Supporting the ACT Solutions ZCU201 USB Z-wave Interface

[Domodude]

Morning all,

Almost there. As Hari wrote, we got a lot closer to a working Z-wave setup. The only problem remaining, I hope, is the transfer of the config from the ZTH200 Homepro primary controller to LinuxMCE.

(I had some trouble getting the ZCS201 recognized by lmce, but I think that it eventually worked again after I got rid of all interfaces, rebooted the core, and then started over. That included attaching the ZCS201, turning on the system, adding the interface in the web setup, update, reload dcerouter. I think that was all it took. I will replay everything once the download problem is out of the way.)

Andrew, I understand you own a ZTH200? Could you tell me if something is wrong here?

• Add units to the ZTH200. I have one plugin dimmer unit on group 1, 3 and 6 each.
• From setup, select transfer partial configuration
• The ZTH200 will tell me Transfer Successful (or something like it)

After this, lmce has only one light as a child device to the zcs201. If I select Transfer FULL Config, the transfer somehow fails, I think it mentions a Data Error.

Any ideas?

Thanks,
Mark

[1audio]

LMCE's ZWave supports the devices. It doesn't know scenes from the controller. In fact in ZWave controller scenes can only be transfered to identical controllers because they all do the UI very differently (and most are really awful).

If you have one device that is all you will see in LMCE. Once its there you can name it and build scenes and scenarios around it.

Did you add the device from the web interface or from the wizard?

I'm really encouraged that we can add a serial ZWave device since the Leviton is serial, and has the feedback from the Leviton switches.

[Domodude]

LMCE's ZWave supports the devices. It doesn't know scenes from the controller. In fact in ZWave controller scenes can only be transfered to identical controllers because they all do the UI very differently (and most are really awful).
If you have one device that is all you will see in LMCE. Once its there you can name it and build scenes and scenarios around it.

At the time I tried it, I had two pluggable dimmers units, which where put in group 1 and group 2 of the controller, respectively. Are you saying I should just add all dimmers to the first group on the Homepro controller, and then do further setup in lmce after the upload of the config?

Did you add the device from the web interface or from the wizard?

I used the web interface; I selected "add device" under "Interfaces". I selected manufacturer Pluto, and just picked the ZWave option after updating the filter. Again, I still need to double-check this. However, the bottom line is that the interface can be recognized (running 0704 here).

Cheers
Mark

[hari]

works for me with the Seluxit viaSENS Homecontroller, a ZTH200 and a ZDP200 plug.
Download configuration works perfect (dongle flashes red). That created a child device that is now fully controllable!

Yippie, ZWave with Linux in Europe

best regards,
Hari

[Domodude]

Yippie, ZWave with Linux in Europe

You beat me to it! 

I will try all three dimmer plugs in the same group on the homepro controller, and then upload the config. How did you do your config transfer to lmce, Hari?

Mark

[hari]

Yippie, ZWave with Linux in Europe

You beat me to it! 

I will try all three dimmer plugs in the same group on the homepro controller, and then upload the config. How did you do your config transfer to lmce, Hari?

Mark

only transfered system configuration as suggested by 1audio. As i have only one plug i don't have multiple groups.

best regards,
Hari

[Domodude]

I now get this in 62_ZWave.log:
...
1   01/18/08 21:44:12   62 (spawning-device)   Starting... 4
1   01/18/08 21:44:12   62 (spawning-device)   Found /usr/pluto/bin/ZWave
05   01/18/08 21:44:17.052      Creating child 63 <0xb78dd6d0>
05   01/18/08 21:44:17.052      Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb78dd6d0>
05   01/18/08 21:44:17.052      Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb78dd6d0>
05   01/18/08 21:44:17.053      Creating child 69 <0xb78dd6d0>
05   01/18/08 21:44:17.053      Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb78dd6d0>
05   01/18/08 21:44:17.053      Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb78dd6d0>
05   01/18/08 21:44:17.053      Creating child 70 <0xb78dd6d0>
05   01/18/08 21:44:17.053      Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb78dd6d0>
05   01/18/08 21:44:17.053      Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb78dd6d0>
...

Those two devices are supposed to be dimmers. I see them, but cannot properly send commands to them. Sending directly to the dimmers gets me an OK response, but nothing happens. The ZWave.log file prints:
05   01/18/08 21:54:35.035      ### Go to timeout queue <0xb68dab90>
05   01/18/08 21:54:35.035      ### skip the next job from timeout queue <0xb68dab90>
05   01/18/08 21:54:58.011      ### Go to timeout queue <0xb68dab90>
05   01/18/08 21:54:58.011      ### skip the next job from timeout queue <0xb68dab90>

 

Any ideas? I think I'd like to thoroughly clean up all children of the ZCS201 and resend the config, would deleting these devices and reloading dcerouter be enough?

Cheers,
Mark

[1audio]

 I'm attaching my log for reference. I have a few devices including one PIR device. I'm not sure if it looks right or not, but its almost all working.

Code:

05 12/30/07 0:00:07.520 Connect() failed, Error Code 111 (Connection refused)) <0xb79166d0>
05 12/30/07 0:00:29.117 Creating child 35 <0xb79166d0>
05 12/30/07 0:00:29.117 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.117 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.117 Creating child 232 <0xb79166d0>
05 12/30/07 0:00:29.117 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.117 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.117 Creating child 233 <0xb79166d0>
05 12/30/07 0:00:29.117 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.117 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 234 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 235 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 236 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 237 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 238 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 239 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 240 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 241 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 242 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 243 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 1813 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 1813 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 244 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 245 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.119 Creating child 246 <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.119 Creating child 247 <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.119 Creating child 248 <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.119 Creating child 252 <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
== ATTEMPT FRESH START ==
1 12/30/07 00:24:37 /usr/pluto/bin/Spawn_Device.sh 34 (spawning-device) 13855 Dev: 34; Already Running list: 15,16,17,18,27,
== FRESH START ==
1 12/30/07 00:24:37 /usr/pluto/bin/Spawn_Device.sh 34 (spawning-device) device: 34 ip: localhost cmd_line: ZWave
0 12/30/07 00:24:37 34 (spawning-device) Entering 34

[ddamron]

1audio,

I get those messages for ALL child devices in all my coding too.
From what I can tell, they can be safely ignored.
38 is Lightswitch Dimmable, 37 is Lightswitch ON/OFF, 1820 and 1813 I'm not sure about..

HTH,

Dan

[totallymaxed]

Morning all,

Almost there. As Hari wrote, we got a lot closer to a working Z-wave setup. The only problem remaining, I hope, is the transfer of the config from the ZTH200 Homepro primary controller to LinuxMCE.

(I had some trouble getting the ZCS201 recognized by lmce, but I think that it eventually worked again after I got rid of all interfaces, rebooted the core, and then started over. That included attaching the ZCS201, turning on the system, adding the interface in the web setup, update, reload dcerouter. I think that was all it took. I will replay everything once the download problem is out of the way.)

Andrew, I understand you own a ZTH200? Could you tell me if something is wrong here?

• Add units to the ZTH200. I have one plugin dimmer unit on group 1, 3 and 6 each.
• From setup, select transfer partial configuration
• The ZTH200 will tell me Transfer Successful (or something like it)

After this, lmce has only one light as a child device to the zcs201. If I select Transfer FULL Config, the transfer somehow fails, I think it mentions a Data Error.

Any ideas?

Thanks,
Mark

Yes we use the ZTH200 Master Controller/remote. We always use 'transfer full config' but we do see a transfer error sometimes. Just resend a few times until you get a good transfer. Are you using the Lighting Wizard to manage the transfer/addition of the lights?

[1audio]

1813 and possibly 1820 are additional controllers on the network or the PIR. I have 3 additional ZWave controllers in the system which should explain that. Or they may be the PIR. I have one light with a device number after a large gap. It gets dumped buy the code and needs to be re-added with almost every router reload if I want to use it.

[Domodude]

Andrew, I understand you own a ZTH200? Could you tell me if something is wrong here?

Are you using the Lighting Wizard to manage the transfer/addition of the lights?

Thanks. I will try to use the full config transfer.

I am not using the lighting wizard, because the RS232 is not plug'n'play. It would be great to use the wizard, but so far I have had no luck. So, it's a matter of manually adding the interface, and then transfering the settings...

Mark

[totallymaxed]

Andrew, I understand you own a ZTH200? Could you tell me if something is wrong here?

Are you using the Lighting Wizard to manage the transfer/addition of the lights?

Thanks. I will try to use the full config transfer.

I am not using the lighting wizard, because the RS232 is not plug'n'play. It would be great to use the wizard, but so far I have had no luck. So, it's a matter of manually adding the interface, and then transfering the settings...

Mark

ok... well under the hood the same code is being called so doing the upload from Web Admin amounts to the same thing.

[Domodude]

Come to think of it....

I have not yet been able to get the floorplan function to work. I added my lights thorugh the "Download Config" route on the web admin site, and added the lights to my map. However, I see no lights on the map on orbiters!

Another thing: reaction to the web interface is sometimes quite slow, or the command does not get processed at all. To any of you experienced Z-wave users: Is that normal?

Thanks,
Mark

[1audio]

The lights won't appear until you rebuild the Orbiter. Have you reset the router and rebuilt the Orbiters?