Author Topic: New Z-Wave driver  (Read 35236 times)

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2421
    • View Profile
    • ago control
New Z-Wave driver
« on: September 10, 2008, 12:10:50 am »
Hi there,

a 32bit binary of the new Z-Wave driver can be found here: http://vt100.at/files/ZWave-0.0.1-0710-32bit.bz2
Just swap with the existing /usr/pluto/bin/ZWave and quick reload the router.

Feedback appreciated,

best regards,
Hari
rock your home - http://www.agocontrol.com home automation

itspac

  • Veteran
  • ***
  • Posts: 136
    • View Profile
Re: New Z-Wave driver
« Reply #1 on: September 10, 2008, 03:17:13 pm »
ill try it this weekend

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2421
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #2 on: September 10, 2008, 05:35:11 pm »
cool!

br, Hari
rock your home - http://www.agocontrol.com home automation

itspac

  • Veteran
  • ***
  • Posts: 136
    • View Profile
Re: New Z-Wave driver
« Reply #3 on: September 13, 2008, 12:02:00 am »
well, I dont have many devices yet, but it seems to be faster, I'll be added more devices in the near future

Domodude

  • Guest
Re: New Z-Wave driver
« Reply #4 on: September 15, 2008, 10:48:24 pm »
a 32bit binary of the new Z-Wave driver can be found

I _so_ would like to try it, but I am currently running 64-bit. As soon as the merge is done, and there is a source that can compile, that will be the VERY first thing I will change on my system!

Hari, did you get your Merten stick? If not, I could probably lend you mine for  awhile...

LegoGT

  • Regular Poster
  • **
  • Posts: 29
    • View Profile
    • Medium Rare Brain
Re: New Z-Wave driver
« Reply #5 on: October 02, 2008, 12:14:11 am »
I finally got a chance to try out the new driver and it seems to work perfectly... very fast. When I plugged in my ZWave dongle (the USB HA22 from Intermatic) the setup wizard never asked me to copy my devices over (from the HA07). I just had to send the command from the Admin panel, manually. I'm not sure if that's intentional but other than that it works great.

In case you're curious, I'm using a random assortment of Leviton and Intermatic lamp modules and dimmers. All seem to work just fine.

Nice work, Hari!
A brain dump of my neverending projects: http://MediumRareBrain.com

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5501
  • DOES work for LinuxMCE.
    • View Profile
Re: New Z-Wave driver
« Reply #6 on: October 02, 2008, 03:37:47 pm »
I second that, Hari.

You rock the Casbah.

-Thom

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2421
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #7 on: October 02, 2008, 04:51:51 pm »
you're welcome!

The intermatic thermostat will be added soon. I think we have a pretty solid Z-Wave support for now. Of course, the code has still some ugly lines, too. But it is only a bit more than 10% of the old code and much better readable (in my eyes *lol*). Inline documentation will follow, somebody interested in becoming "the second z-wave guy"?

br, Hari
rock your home - http://www.agocontrol.com home automation

yannko

  • Regular Poster
  • **
  • Posts: 22
    • View Profile
Re: New Z-Wave driver
« Reply #8 on: October 31, 2008, 02:21:57 pm »
Hello,

First, thanks for the new version of this driver. I actually have an issue with a Seluxit ViaSens Homecontroller, it's well detected by the system as well as in the pluto admin, but I can't communicate with the device.
Switching ON/OFF/50% a dimmer in the light menu results with no action, it seems that no message is sent through the system.

A lsusb shows up the correct device:

Code: [Select]
Bus 002 Device 009: ID 16c0:06eb

A dmesg brings the following output:

Code: [Select]
[ 7529.677639] usb 2-1: new full speed USB device using uhci_hcd and address 7
[ 7529.852890] usb 2-1: configuration #1 chosen from 1 choice
[ 7529.855858] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/cdc-acm.c: This device cannot do calls on its own. It is no modem.
[ 7529.855869] cdc_acm 2-1:1.0: ttyACM0: USB ACM device

And the ZWave command gives the following:

Code: [Select]
ZWave, v.<=version=>
Visit www.plutohome.com for source code and license information

01 10/31/08 14:14:08.549 ZWaveSerial::Send m_iFrameID 1 type 0x0 command 0x15 didn't get ACK.  wait for rest <0xb694eb90>
01 10/31/08 14:14:09.300 ZWaveSerial::Send m_iFrameID 1 type 0x0 command 0x15 didn't get ACK.  wait for rest <0xb694eb90>
01 10/31/08 14:14:10.050 ZWaveSerial::Send m_iFrameID 1 type 0x0 command 0x15 didn't get ACK.  wait for rest <0xb694eb90>
01 10/31/08 14:14:10.085 ZWaveSerial::ReceiveData Checksum 234 != 0 size 16 offset 0 left 16 framesize 16 <0xb594cb90>
05 10/31/08 14:14:10.135 ZWaveSerial::ReceiveData skipping unknown 0x10 <0xb594cb90>
01 10/31/08 14:14:10.800 ZWaveSerial::Send m_iFrameID 1 type 0x0 command 0x15 expected 2 got ack 0 response 0 request 0 failed to get at time 3799 ack 0 <0xb694eb90>
01 10/31/08 14:14:10.800 ZWJob_GenericSendFrame::Run failed to run job #0 P:1 ZWJob_Initialize:init type 0x0 command 0x15 abort 0 lower priority 0 retries 0 node 0 <0xb694eb90>
01 10/31/08 14:14:11.585 ZWaveSerial::Send m_iFrameID 2 type 0x0 command 0x20 didn't get ACK.  wait for rest <0xb694eb90>
01 10/31/08 14:14:12.335 ZWaveSerial::Send m_iFrameID 2 type 0x0 command 0x20 didn't get ACK.  wait for rest <0xb694eb90>
01 10/31/08 14:14:13.086 ZWaveSerial::Send m_iFrameID 2 type 0x0 command 0x20 didn't get ACK.  wait for rest <0xb694eb90>
01 10/31/08 14:14:13.836 ZWaveSerial::Send m_iFrameID 2 type 0x0 command 0x20 expected 2 got ack 0 response 0 request 0 failed to get at time 6835 ack 0 <0xb694eb90>
01 10/31/08 14:14:13.836 ZWJob_GenericSendFrame::Run failed to run job #0 P:1 ZWJob_Initialize:init type 0x0 command 0x20 abort 0 lower priority 0 retries 0 node 0 <0xb694eb90>

Any help very much appreciated, thanks for reading me!

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2421
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #9 on: October 31, 2008, 09:25:52 pm »
Hi Yannko,

you are not running my driver. This seems to be the stock 0710 driver. Please enable log levels 36, 40 and 41 in /etc/pluto.conf. Quick reload the router, it should start the device automatically. Show me the output of /var/log/pluto/<your_device_id>_ZWave.log, where <your_device_id> is your device id in lmce.

best regards,
Hari
rock your home - http://www.agocontrol.com home automation

superfro

  • Regular Poster
  • **
  • Posts: 24
    • View Profile
Re: New Z-Wave driver
« Reply #10 on: November 06, 2008, 06:44:00 am »
Hari, Are HSM100's supported?

I'm running the driver you have below iwth a intermatic ha22 ... I've followed the instructions for the ACT homepro motion detector... (http://wiki.linuxmce.com/index.php/ACT_Homepro_Motion_Detector) .... And I add items to my HA07 and copy them over, well the HSM100's don't get copied over... they don't show up in the z-wave log or on the admin web... I'm still installing new devices so I know the items are added to my network .... they just don't seem to be copying over...

seeing how there was debug info here http://wiki.linuxmce.com/index.php/ZWave_API#HSM100__.28battery.2C_temperature.2C_motion.2C_light.29  I had assumed these were supported.

Any help is appreciated...

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2421
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #11 on: November 06, 2008, 09:40:17 am »
Hari, Are HSM100's supported?
not yet, but that should be an easy one.

Quote
I'm running the driver you have below iwth a intermatic ha22 ... I've followed the instructions for the ACT homepro motion detector... (http://wiki.linuxmce.com/index.php/ACT_Homepro_Motion_Detector) .... And I add items to my HA07 and copy them over, well the HSM100's don't get copied over... they don't show up in the z-wave log or on the admin web... I'm still installing new devices so I know the items are added to my network .... they just don't seem to be copying over...

seeing how there was debug info here http://wiki.linuxmce.com/index.php/ZWave_API#HSM100__.28battery.2C_temperature.2C_motion.2C_light.29  I had assumed these were supported.

Any help is appreciated...
For a first look i need the logfile of the ZWave device with loglevels 36, 40 and 41 activated.

Can you prepare SSH remote access for me?

best regards,
Hari
rock your home - http://www.agocontrol.com home automation

superfro

  • Regular Poster
  • **
  • Posts: 24
    • View Profile
Re: New Z-Wave driver
« Reply #12 on: November 06, 2008, 05:36:30 pm »
Ahh, now that i enable the loglevels I see them appear in the logs as nodes 5,6,7,8 (i have 4 of them currently)....

Hari I will send you a pm right now with info for you to login remotely to my core... 

Thanks

superfro

  • Regular Poster
  • **
  • Posts: 24
    • View Profile
Re: New Z-Wave driver
« Reply #13 on: November 06, 2008, 06:14:45 pm »
I had to send an email, it said you rejected pm's ....

Let me know if there is anything I can do.

yannko

  • Regular Poster
  • **
  • Posts: 22
    • View Profile
Re: New Z-Wave driver
« Reply #14 on: November 06, 2008, 07:11:49 pm »
Hi Yannko,

you are not running my driver. This seems to be the stock 0710 driver. Please enable log levels 36, 40 and 41 in /etc/pluto.conf. Quick reload the router, it should start the device automatically. Show me the output of /var/log/pluto/<your_device_id>_ZWave.log, where <your_device_id> is your device id in lmce.

best regards,
Hari

Hi Hari,

Thanks a lot for your answer. I finally got the driver running, and the possibility to send commands to the nodes. Here is a snapshot of the log file:

Code: [Select]
05 11/06/08 18:54:02.946 Creating child 210 <0xb798b6c0>
05 11/06/08 18:54:02.946 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb798b6c0>
05 11/06/08 18:54:02.947 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb798b6c0>
05 11/06/08 18:54:02.947 Creating child 211 <0xb798b6c0>
05 11/06/08 18:54:02.947 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb798b6c0>
05 11/06/08 18:54:02.947 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb798b6c0>
05 11/06/08 18:54:02.947 Creating child 212 <0xb798b6c0>
05 11/06/08 18:54:02.947 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb798b6c0>
05 11/06/08 18:54:02.947 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb798b6c0>
05 11/06/08 18:54:02.947 Creating child 215 <0xb798b6c0>
05 11/06/08 18:54:02.947 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0xb798b6c0>
05 11/06/08 18:54:02.947 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0xb798b6c0>
36 11/06/08 18:54:04.535 No callback received: await_callback: 1 timer: 31 <0xb798ab90>
36 11/06/08 18:54:04.535 ERROR: Dropping command, no callback received after three resends <0xb798ab90>
40 11/06/08 18:54:04.635 Sending job 0x80831c0 (cb 0) - 0x1 0x4 0x0 0x41 0x1 0xbb (###A##) <0xb798ab90>
41 11/06/08 18:54:04.638 ACK RECEIVED <0xb798ab90>
41 11/06/08 18:54:04.641 0x1 0x9 0x1 0x41 0xd2 0x6 0x0 0x2 0x2 0x1 0x63 (###A######c) <0xb798ab90>
36 11/06/08 18:54:04.641 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb798ab90>
36 11/06/08 18:54:04.641 ***FOUND NODE: 1 <0xb798ab90>
36 11/06/08 18:54:04.641 listening node <0xb798ab90>
36 11/06/08 18:54:04.641 optional functionality <0xb798ab90>
36 11/06/08 18:54:04.641 BASIC TYPE: Static Controller <0xb798ab90>
36 11/06/08 18:54:04.641 GENERIC TYPE: Static Controller <0xb798ab90>
36 11/06/08 18:54:04.641 SPECIFIC TYPE: 1 <0xb798ab90>
40 11/06/08 18:54:04.740 Sending job 0x80833e0 (cb 0) - 0x1 0x4 0x0 0x41 0x2 0xb8 (###A##) <0xb798ab90>
41 11/06/08 18:54:04.741 ACK RECEIVED <0xb798ab90>
41 11/06/08 18:54:04.745 0x1 0x9 0x1 0x41 0xc9 0xc 0x0 0x4 0x11 0x1 0x67 (###A######g) <0xb798ab90>
36 11/06/08 18:54:04.745 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb798ab90>
36 11/06/08 18:54:04.745 ***FOUND NODE: 2 <0xb798ab90>
36 11/06/08 18:54:04.745 listening node <0xb798ab90>
36 11/06/08 18:54:04.745 optional functionality <0xb798ab90>
36 11/06/08 18:54:04.745 BASIC TYPE: Routing Slave <0xb798ab90>
36 11/06/08 18:54:04.745 GENERIC TYPE: Multilevel Switch <0xb798ab90>
36 11/06/08 18:54:04.745 SPECIFIC TYPE: 1 <0xb798ab90>

My question is now the following one: the messages from the USB controller to the devices are well interpreted by the orbiter (the lights icons are changing), but in the other direction it's not true (if I manually switch off a light which was on, it will still display that it's on). It's just showing what was the last light action from the USB control device. Is there a possibility to intercept messages in both directions, and to have them interpreted accordingly in Orbiter?

Thanks a lot for your help!