Supporting the ACT Solutions ZCU201 USB Z-wave Interface

[coley]

wow! a lot happens in a few days, was away for a bit.
my zwave devices arrived so hopefully should get to play with them in the next few days.

btw does anyone know what the extra connector on the ZCU201 is besides the pwr and USB?

-Coley.

[totallymaxed]

I also noticed that there is a new unit ZCS201 available, which is direct RS232 (I think)  . Does anyone actually own one of these, or did experiments with it?

We have ordered some of those for testing here... will report back once we have them ;-)

Of course, I could not wait on that 
My ZCS201 should come in tomorrow, I'll check it out and report on the results. Supposedly it really does have a serial connector, so we'll see what happens. A previous thread (http://forum.linuxmce.org/index.php?topic=2766.msg13509#msg13509) mentioned the ZCS201, but refers to the USB connector! Hmmm... I am hoping that was a typo! 

Mark

Mark there are two models of the ZCU201.... one USB and one serial. Hope you get the version you want ;-)

[hari]

Mark there are two models of the ZCU201.... one USB and one serial. Hope you get the version you want ;-)

Actually, the models can be told apart by the third letter. I got a ZCS201, not a ZCU201! 

where did you get that beast from? i was searching for ages..

[hari]

news from the Z-Wave front:
after some device tweaking and package installation (mysterious indeed) with domodude we got the ZWave device to run with the ZCS201. As domodude has no primary controller, too, we have to wait until the shippings arrive for further tests.

best regards,
Hari

[totallymaxed]

news from the Z-Wave front:
after some device tweaking and package installation (mysterious indeed) with domodude we got the ZWave device to run with the ZCS201. As domodude has no primary controller, too, we have to wait until the shippings arrive for further tests.

best regards,
Hari

Hey Hari thats great... when you get a chance can you post the steps you needed to do to get the ZCS201 working? I will then test that here and we will try and get it into the 0710

[hari]

Hey Hari thats great... when you get a chance can you post the steps you needed to do to get the ZCS201 working? I will then test that here and we will try and get it into the 0710

we simply did a "ln -s /dev/ttyS0 /dev/ttyS_ZWAVE_0" and "UpdateAvailableSerialPorts.sh" and used that devicefile in the device config, because of some obscure reason the manually added device did not like the "/dev/ttyS0" port..

I'll keep you posted,

best regards,
Hari

[totallymaxed]

Hey Hari thats great... when you get a chance can you post the steps you needed to do to get the ZCS201 working? I will then test that here and we will try and get it into the 0710

we simply did a "ln -s /dev/ttyS0 /dev/ttyS_ZWAVE_0" and "UpdateAvailableSerialPorts.sh" and used that devicefile in the device config, because of some obscure reason the manually added device did not like the "/dev/ttyS0" port..

I'll keep you posted,

best regards,
Hari

We should get that added to the SVN somehow so that it can be easily chosen by users. With the new common SVN coming that should be easily achieved ;-)

[hari]

We should get that added to the SVN somehow so that it can be easily chosen by users. With the new common SVN coming that should be easily achieved ;-)

to become of topic maybe you want to contribute to the foundation thread?

best regards,
Hari

[totallymaxed]

We should get that added to the SVN somehow so that it can be easily chosen by users. With the new common SVN coming that should be easily achieved ;-)

to become of topic maybe you want to contribute to the foundation thread?

best regards,
Hari

;-) will do

[hari]

some progress with Domodude and his ZCS201: we were able to download a device to the ZCS201. More tests to come (some problems with transfer of the full config).

hope to get my ZTH200 tomorrow for further tests with the Seluxit dongle.

best regards,
Hari

[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.

[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

[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

[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: [Select]

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