LinuxMCE Forums

General => Users => Topic started by: hari on September 10, 2008, 12:10:50 am

Title: New Z-Wave driver
Post by: hari 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
Title: Re: New Z-Wave driver
Post by: itspac on September 10, 2008, 03:17:13 pm
ill try it this weekend
Title: Re: New Z-Wave driver
Post by: hari on September 10, 2008, 05:35:11 pm
cool!

br, Hari
Title: Re: New Z-Wave driver
Post by: itspac 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
Title: Re: New Z-Wave driver
Post by: LegoGT 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!
Title: Re: New Z-Wave driver
Post by: tschak909 on October 02, 2008, 03:37:47 pm
I second that, Hari.

You rock the Casbah.

-Thom
Title: Re: New Z-Wave driver
Post by: hari 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
Title: Re: New Z-Wave driver
Post by: yannko 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!
Title: Re: New Z-Wave driver
Post by: hari 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
Title: Re: New Z-Wave driver
Post by: superfro 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...
Title: Re: New Z-Wave driver
Post by: hari 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
Title: Re: New Z-Wave driver
Post by: superfro 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
Title: Re: New Z-Wave driver
Post by: superfro 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.
Title: Re: New Z-Wave driver
Post by: yannko 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!
Title: Re: New Z-Wave driver
Post by: hari on November 06, 2008, 07:24:59 pm
what kind of light switches are you using?
Title: Re: New Z-Wave driver
Post by: yannko on November 06, 2008, 07:30:28 pm
what kind of light switches are you using?

So far I connected, from Merten, 1 dimmer (ref. 577x with some office lamp) and 1 relay (ref. 576x, simply an ON/OFF switch with a halogen lamp). Everything works well, manually and remotely, except this "update" of nodes in the orbiter.
Thanks for your help, it's greatly appreciated!
Title: Re: New Z-Wave driver
Post by: hari on November 06, 2008, 09:58:00 pm
assign the dongle to group 1 of the merten stuff.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: yannko on November 07, 2008, 01:02:20 pm
assign the dongle to group 1 of the merten stuff.

best regards,
Hari

Thanks for your answer. I added, in the Seluxit software (WinXP), a group consisting of the dongle and the Merten devices, but it didn't help to solve my problem. Should I do it in LinuxMCE as well on the Admin Website (add a device group)?
Title: Re: New Z-Wave driver
Post by: hari on November 07, 2008, 02:27:44 pm
never used the seluxit software.

Maybe you did it the wrong way round.  The dongle has to go into group1 of the switch, not the other way round.

You can use the SetAssociation DCE command, first parameter is the node id of the switch, second the group (1), third the node id of the dongle (can be seen as "our node id" in the logs.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: yannko on November 07, 2008, 04:59:06 pm
Just tried the Set Association command, and a few manipulations to see what happens. It didn't solve my issue still, but at least I progressed a bit in the assimilation of the system.
When I create the group association in LinuxMCE, and after I check it in the Seluxit software, it's well updated, but only the dongle appears in the group, the switch doesn't belong to any group. I tried also to set the group directly in the Seluxit software, both devices belong to the same group, but back to lmce, I don't have positive results so far.
I was just wondering, is it possible to associate lights directly in lmce without having to use the Seluxit software? I still couldn't find how to do it (after few trials, unfortunately the lack of documentation for the devices I'm handling is very problematic). If yes, I would try to configure everything from lmce.
Thanks for your support Hari, I hope it will get solved somehow  :)!
Title: Re: New Z-Wave driver
Post by: hari on November 07, 2008, 05:56:18 pm
yes. On the long run I'll try to make all devices plug and play. Let me verify some code, could be I've missed to check that in. For now it would help if you could enable log levels 36, 40 and 41 in /etc/pluto.conf and show me the output of the z-wave device log (/var/log/pluto) when pressing the switch.

I have a merten dimmer installed at the moment (thanks possy :-) ), I'm sure I can work that out this weekend.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: hari on November 08, 2008, 06:02:21 pm
have not yet received the stick..

should arrive these days..

br, Hari
Title: Re: New Z-Wave driver
Post by: yannko on November 10, 2008, 06:12:46 pm
yes. On the long run I'll try to make all devices plug and play. Let me verify some code, could be I've missed to check that in. For now it would help if you could enable log levels 36, 40 and 41 in /etc/pluto.conf and show me the output of the z-wave device log (/var/log/pluto) when pressing the switch.

I have a merten dimmer installed at the moment (thanks possy :-) ), I'm sure I can work that out this weekend.

best regards,
Hari

It will be great to have the device detected as plug and play  :D!
Here are the log files from the Z-Wave device, at first the relay switch when pushed on:

Code: [Select]
41 11/10/08 18:05:38.314 0x1 0x9 0x0 0x4 0x0 0x3 0x3 0x20 0x1 0xff 0x2c (####### ##,) <0xb790db90>
36 11/10/08 18:05:38.314 FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb790db90>
36 11/10/08 18:05:38.314 COMMAND_CLASS_BASIC -  <0xb790db90>
36 11/10/08 18:05:38.314 Got COMMAND_CLASS_BASIC:BASIC_SET, level 255 <0xb790db90>

Same switch pushed off:

Code: [Select]
41 11/10/08 18:07:54.968 0x1 0x9 0x0 0x4 0x0 0x3 0x3 0x20 0x1 0x0 0xd3 (####### ###) <0xb790db90>
36 11/10/08 18:07:54.968 FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb790db90>
36 11/10/08 18:07:54.968 COMMAND_CLASS_BASIC -  <0xb790db90>
36 11/10/08 18:07:54.968 Got COMMAND_CLASS_BASIC:BASIC_SET, level 0 <0xb790db90>

Then the dimmer pushed on:

Code: [Select]
41 11/10/08 18:08:24.139 0x1 0x9 0x0 0x4 0x0 0x2 0x3 0x26 0x1 0xff 0x2b (#######&##+) <0xb790db90>
36 11/10/08 18:08:24.139 FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb790db90>
36 11/10/08 18:08:24.139 COMMAND_CLASS_SWITCH_MULTILEVEL -  <0xb790db90>

And finally, the dimmer pushed off:

Code: [Select]
41 11/10/08 18:09:11.512 0x1 0x9 0x0 0x4 0x0 0x2 0x3 0x26 0x1 0x0 0xd4 (#######&###) <0xb790db90>
36 11/10/08 18:09:11.512 FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb790db90>
36 11/10/08 18:09:11.512 COMMAND_CLASS_SWITCH_MULTILEVEL -  <0xb790db90>

If I can help by sending or doing anything more, just let me know.
Title: Re: New Z-Wave driver
Post by: hari on November 10, 2008, 06:30:14 pm
yeah, I missed some code for that, it is now checked into the 0810 branch on svn. I will release a new binary version for 0710 these days after some polishing and when I've added multiple instances support for that HSM100 beast.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: yannko on November 10, 2008, 06:34:13 pm
yeah, I missed some code for that, it is now checked into the 0810 branch on svn. I will release a new binary version for 0710 these days after some polishing and when I've added multiple instances support for that HSM100 beast.

best regards,
Hari

Thanks a lot for your help and your reactivity Hari, that's really great! I'm looking forward to test it  :)!

Best regards!
Title: Re: New Z-Wave driver
Post by: totallymaxed on November 10, 2008, 06:39:05 pm
Hari,

We're ordering some Danfoss RA Plus-w's for testing here... from memory I think you have got those working. Is that correct?

All the best

Andrew
Title: Re: New Z-Wave driver
Post by: hari on November 10, 2008, 10:36:58 pm
Hari,

We're ordering some Danfoss RA Plus-w's for testing here... from memory I think you have got those working. Is that correct?

yes, they are automatically configured when included in SIS mode (they require SIS). It supports multiple setpoints for every weekday and requests a schedule, for now i just reply with an empty one as we have no way in lmce to define one.

It honors on and off (normal/setback operation). The wake up interval is a bit short at the moment, wanted to do some tests this heating period to find the optimum compromise between latency and battery drain.

When you've got yours we can do some fine tuning..

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: hari on November 11, 2008, 12:33:21 pm
yeah, I missed some code for that, it is now checked into the 0810 branch on svn. I will release a new binary version for 0710 these days after some polishing and when I've added multiple instances support for that HSM100 beast.
Thanks a lot for your help and your reactivity Hari, that's really great! I'm looking forward to test it  :)!
no multi instance yet but I wanted to provide you a test version with the fix for the merten dimmer floorplan updates, just tested, works fine:

http://vt100.at/files/ZWave-0.0.2-0710-32bit.bz2

I'd assume the same is needed for the binary switch, I don't have one yet. Do you have one?

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: totallymaxed on November 11, 2008, 01:15:45 pm
Hari,

We're ordering some Danfoss RA Plus-w's for testing here... from memory I think you have got those working. Is that correct?

yes, they are automatically configured when included in SIS mode (they require SIS). It supports multiple setpoints for every weekday and requests a schedule, for now i just reply with an empty one as we have no way in lmce to define one.

It honors on and off (normal/setback operation). The wake up interval is a bit short at the moment, wanted to do some tests this heating period to find the optimum compromise between latency and battery drain.

When you've got yours we can do some fine tuning..

best regards,
Hari

Hari,

Great sounds good. We should have our units by next week I imagine.

All the best

Andrew
Title: Re: New Z-Wave driver
Post by: yannko on November 11, 2008, 04:33:54 pm
yeah, I missed some code for that, it is now checked into the 0810 branch on svn. I will release a new binary version for 0710 these days after some polishing and when I've added multiple instances support for that HSM100 beast.
Thanks a lot for your help and your reactivity Hari, that's really great! I'm looking forward to test it  :)!
no multi instance yet but I wanted to provide you a test version with the fix for the merten dimmer floorplan updates, just tested, works fine:

http://vt100.at/files/ZWave-0.0.2-0710-32bit.bz2

I'd assume the same is needed for the binary switch, I don't have one yet. Do you have one?

best regards,
Hari

Hi Hari,

Many thanks for this release, it's working pretty nicely now  :P! I tested the dimmer and the binary switch, and both are sending the correct infos in the orbiter. Great job  :)! If you need some logs from the binary switch just tell me.
Title: Re: New Z-Wave driver
Post by: hari on November 11, 2008, 05:11:39 pm
Many thanks for this release, it's working pretty nicely now  :P!
nice to hear, you are welcome :-)

Quote
I tested the dimmer and the binary switch, and both are sending the correct infos in the orbiter. Great job  :)! If you need some logs from the binary switch just tell me.
perfect, I was not sure about the binary. Yes, a few log lines for final QA would be nice.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: yannko on November 13, 2008, 02:20:01 pm
Here are the logs for the binary switch:

When turned on:
Code: [Select]
41 11/13/08 14:16:23.799 0x1 0x9 0x0 0x4 0x0 0x3 0x3 0x20 0x1 0xff 0x2c (####### ##,) <0xb7995b90>
36 11/13/08 14:16:23.800 FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb7995b90>
36 11/13/08 14:16:23.800 COMMAND_CLASS_BASIC -  <0xb7995b90>
36 11/13/08 14:16:23.800 Got BASIC_SET from node 3, value 255 <0xb7995b90>
36 11/13/08 14:16:23.800 State changed, send light changed event <0xb7995b90>
36 11/13/08 14:16:23.800 ZWave::SendLightChangedEvents sending commands/events <0xb7995b90>
36 11/13/08 14:16:23.800 Sending EVENT_State_Changed_CONST event from node 3, level 255 <0xb7995b90>


And when turned off:
Code: [Select]
41 11/13/08 14:15:04.686 0x1 0x9 0x0 0x4 0x0 0x3 0x3 0x20 0x1 0x0 0xd3 (####### ###) <0xb7995b90>
36 11/13/08 14:15:04.686 FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb7995b90>
36 11/13/08 14:15:04.686 COMMAND_CLASS_BASIC -  <0xb7995b90>
36 11/13/08 14:15:04.686 Got BASIC_SET from node 3, value 0 <0xb7995b90>
36 11/13/08 14:15:04.686 State changed, send light changed event <0xb7995b90>
36 11/13/08 14:15:04.686 ZWave::SendLightChangedEvents sending commands/events <0xb7995b90>
36 11/13/08 14:15:04.686 Sending EVENT_State_Changed_CONST event from node 3, level 0 <0xb7995b90>

That works smoothly for now  :), many thanks!
Title: Re: New Z-Wave driver
Post by: hari on November 13, 2008, 03:07:43 pm
cool, exactly as I've expected.

br, Hari
Title: Re: New Z-Wave driver
Post by: hari on November 14, 2008, 07:41:56 pm
I have a merten dimmer installed at the moment (thanks possy :-) ), I'm sure I can work that out this weekend.

Hari, any progress on the Merten stick? (Hopefully I did not miss an announcement!)
If you still need one, I could lend you mine for a while.

Cheers
Mark
I've received the dongle this week.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: habazot on November 23, 2008, 11:14:16 pm
Hi, do you have a 64bit version of the new ZWave binary as well..?.
On a general note: is using 64bit LMCE going to cause me more pain than gain..?..
Title: Re: New Z-Wave driver
Post by: hari on November 23, 2008, 11:23:49 pm
Hi, do you have a 64bit version of the new ZWave binary as well..?.
no.

Quote
On a general note: is using 64bit LMCE going to cause me more pain than gain..?..
if you ask me, yes.

br, Hari
Title: Re: New Z-Wave driver
Post by: hari on November 30, 2008, 11:21:42 pm
good news, the creation of the open Z-Wave driver package is now included in the build process. 0810alpha has Z-Wave :-)

br, Hari
Title: Re: New Z-Wave driver
Post by: hari on January 02, 2009, 09:04:59 pm
you should see speed improvements. E.g. the fiire chief with multiple lamps in the same room now works much better.

br, Hari
Title: Re: New Z-Wave driver
Post by: johanr on January 25, 2009, 10:11:40 pm
Hi, do you have a 64bit version of the new ZWave binary as well..?.
no.

Quote
On a general note: is using 64bit LMCE going to cause me more pain than gain..?..
if you ask me, yes.

br, Hari

Can you please explain why you think 64 bit is not as good as 32.
I will most probarbly do a reinstall shortly(system cannot find device-logfiles etc from webadmin so I have destroyed something) and are using "64 bit hw" and 64 lmce now so any input is interesting to know.

Also I wonder if I want to convert the 32bit driver you have done to suit 64 bit hardware. What process should I google? (compile?)

Still Very thankful(glad) for the help I got with the Connect hw selection.(it works!) but config is sometimes lost..
Best Regards
johan
Title: Re: New Z-Wave driver
Post by: hari on January 25, 2009, 11:54:17 pm
to stay on topic: they should _not_ forget the config. Go and have them replaced.

the 32/64bit thing does not belong here.. there are other threads where the topic is discussed.

br, Hari
Title: Re: New Z-Wave driver
Post by: johanr on January 26, 2009, 09:51:15 am
Ok, I will let the system run for a few days and evaluate. Could also just being me doing something wrongly maybe..
Sorry for the OT. was not sure how to treat it since it was related to the driver, will start another thread about that.  :)

edit. will not start another thread since I did more thourough searches on the matter and are now convinced to install the 32bit instead.

-johan
Title: Re: New Z-Wave driver
Post by: KingCrab on January 30, 2009, 09:57:37 am
Hi,

I've just started rebuilding my Linuxmce system and I'm thinking to include a new set of zwave devices to it.

As Merten inwall devices seem to be the best choice for me, I want to ask if there is any progress on the Merten Usb stick right now?
Alternatively, is it possible to start only with two inwall devices and the Tricklestar combi (stick + remote) or do I need an additional static controller?

I'm an absolutely newbie with the whole zwave thing, please be kind  ;)

Thanks in advance
Title: Re: New Z-Wave driver
Post by: hari on January 30, 2009, 12:53:12 pm
the tricklestar is no "combi" thing, you mix that with the MCV stick.

I usually recommend SIS mode, read a recent remote (like the tricklestar) and a static controller. If you don't want to use a remote get the MCV stick, it has an include button.

The merten usb chip is not supported by the linux kernel, so I have no way to access the zensys chip. Better get another dongle.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: johanr on February 01, 2009, 12:12:27 am
Hi!

reinstalled and I am now running 32bit. Lmce found my previously added zwave devices and I added them back. Then after functioncheck I changed to the updated driver.
For some reason the Seluxit wont respond. Made a restart of the system(after a few quick reloads) but it did not help.
Rolled back the driver and after restart everything was fine again =/ hmm.
Got a thought that maybe I need to add the devices with the new driver. So all devices has been excluded but I just cannot get them back by including.
 Nor do the Seluxit give a response "OK" on the download config.
Maybe like some other guy here that had problem and it was related to a group id. However I cannot figure out the node id and the rest so..
Here's a print from when I sent "download config" from LMCE Admin and never got a respons back and onwards since it seem to have made a restart.

Hope you or someone that hopefully understand the output can help me get it working.

Code: [Select]
41   01/31/09 23:59:09.810              ACK RECEIVED <0xb78bcb90>
41   01/31/09 23:59:09.812              0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0xb78bcb90>
36   01/31/09 23:59:09.812              ZW_SEND delivered to Z-Wave stack <0xb78bcb90>
41   01/31/09 23:59:09.833              0x1 0x5 0x0 0x13 0x5 0x0 0xec (#######) <0xb78bcb90>
36   01/31/09 23:59:09.833              ZW_SEND Response with callback 5 received <0xb78bcb90>
36   01/31/09 23:59:09.833              ZW_SEND was successful, removing job <0xb78bcb90>
36   01/31/09 23:59:10.162              Received command #757 - Download Configuration <0xb68bab90>
36   01/31/09 23:59:10.162              Download configuration start <0xb68bab90>
36   01/31/09 23:59:10.162              Replicate controller start <0xb68bab90>
40   01/31/09 23:59:10.233              Sending job 0x80a0700 (cb 0) - 0x1 0x4 0x0 0x50 0x1 0xaa (###P##) <0xb78bcb90>
41   01/31/09 23:59:10.234              ACK RECEIVED <0xb78bcb90>
36   01/31/09 23:59:40.453              We have been idle for 30 seconds, polling device states <0xb78bcb90>
40   01/31/09 23:59:40.553              Sending job 0x80a0920 (cb 6) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x6 0x39 (###### ###9) <0xb78bcb90>
41   01/31/09 23:59:40.554              ACK RECEIVED <0xb78bcb90>
41   01/31/09 23:59:40.556              0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0xb78bcb90>
36   01/31/09 23:59:40.556              ZW_SEND delivered to Z-Wave stack <0xb78bcb90>
41   01/31/09 23:59:40.577              0x1 0x5 0x0 0x13 0x6 0x0 0xef (#######) <0xb78bcb90>
36   01/31/09 23:59:40.577              ZW_SEND Response with callback 6 received <0xb78bcb90>
36   01/31/09 23:59:40.577              ZW_SEND was successful, removing job <0xb78bcb90>
36   02/01/09 0:00:10.162               Download configuration end <0xb68bab90>
36   02/01/09 0:00:10.162               Replicate controller end <0xb68bab90>
36   02/01/09 0:00:10.162               Get new init data after replication <0xb68bab90>
05   02/01/09 0:00:10.163               Socket::ReceiveData 0x807a2c0 failed, bytes left 0 start: 10000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 7 Command_Impl1 Dev #31 <0xb68bab90>
05   02/01/09 0:00:10.164               Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Command_Impl1 Dev #31 <0xb68bab90>
01   02/01/09 0:00:10.164               Receive string failed in HandleRequestSocket 18:ReceiveData failed Command_Impl1 Dev #31 <0xb68bab90>
05   02/01/09 0:00:10.164               Dumping 1 locks <0xb68bab90>
05   02/01/09 0:00:10.164               finished check for exceptions <0xb68bab90>
05   02/01/09 0:00:10.164               OL: (0x807a40c) (>104) MessageQueue Command_Impl.cpp l:822 time: 1:00:00a (1233442810 s) thread: 3070999440 Rel: Y Got: Y <0xb68bab90>
Return code: 2
2 02/01/09 00:00:10     31 (spawning-device)    Device requests restart... count=3/50 dev=31
Sun Feb  1 00:00:10 CET 2009 Restart
========== NEW LOG SECTION ==========
1 02/01/09 00:00:18     31 (spawning-device)    Starting... 3
1 02/01/09 00:00:18     31 (spawning-device)    Found /usr/pluto/bin/ZWave
36   02/01/09 0:00:18.493               Initialization... <0xb79976c0>
36   02/01/09 0:00:18.493               Open serial port /dev/ttyACM0 <0xb79976c0>
36   02/01/09 0:00:18.496               receiveFunction started <0xb7996b90>
36   02/01/09 0:00:18.496               Get version <0xb79976c0>
36   02/01/09 0:00:18.496               Get home/node id <0xb79976c0>
36   02/01/09 0:00:18.496               Get capabilities <0xb79976c0>
36   02/01/09 0:00:18.496               Get SUC node id <0xb79976c0>
36   02/01/09 0:00:18.496               Get init data <0xb79976c0>
36   02/01/09 0:00:21.621               No callback received: await_callback: 134720552 timer: 31 <0xb7996b90>
40   02/01/09 0:00:21.721               Sending job 0x80825f8 (cb 0) - 0x1 0x3 0x0 0x15 0xe9 (#####) <0xb7996b90>
41   02/01/09 0:00:21.722               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:21.723               0x1 0x10 0x1 0x15 0x5a 0x2d 0x57 0x61 0x76 0x65 0x20 0x32 0x2e 0x34 0x30 0x0 0x1 0x90 (####Z-Wave 2.40###) <0xb7996b90>
36   02/01/09 0:00:21.724               TODO: handle response for 0x15  <0xb7996b90>
40   02/01/09 0:00:21.821               Sending job 0x8082818 (cb 0) - 0x1 0x3 0x0 0x20 0xdc (### #) <0xb7996b90>
41   02/01/09 0:00:21.822               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:21.823               0x1 0x8 0x1 0x20 0x0 0x5b 0x93 0x75 0x1 0x6a (### #[#u#j) <0xb7996b90>
36   02/01/09 0:00:21.824               Got reply to ZW_MEMORY_GET_ID, Home id: 0x005b9375, our node id: 1 <0xb7996b90>
40   02/01/09 0:00:21.921               Sending job 0x8082a38 (cb 0) - 0x1 0x3 0x0 0x7 0xfb (#####) <0xb7996b90>
41   02/01/09 0:00:21.922               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:21.954               0x1 0x2b 0x1 0x7 0x2 0x4c 0x0 0x0 0x0 0x1 0x0 0x1 0xfe 0x80 0xfe 0x88 0xf 0x0 0x0 0x0 0xfb 0x9f 0x7f 0x80 0x7 0x0 0x0 0x0 0x0 0x80 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x87 (#+###L#######################################) <0xb7996b90>
36   02/01/09 0:00:21.954               TODO: handle response for 0x7  <0xb7996b90>
40   02/01/09 0:00:22.053               Sending job 0x8082c58 (cb 0) - 0x1 0x3 0x0 0x56 0xaa (###V#) <0xb7996b90>
41   02/01/09 0:00:22.054               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.055               0x1 0x4 0x1 0x56 0x1 0xad (###V##) <0xb7996b90>
36   02/01/09 0:00:22.055               Got reply to GET_SUC_NODE_ID, node: 1 <0xb7996b90>
40   02/01/09 0:00:22.153               Sending job 0x8082e78 (cb 0) - 0x1 0x3 0x0 0x2 0xfe (#####) <0xb7996b90>
41   02/01/09 0:00:22.154               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.201               0x1 0x25 0x1 0x2 0x4 0x8 0x1d 0x1 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x2 0x1 0xca (#%#) <0xb7996b90>
36   02/01/09 0:00:22.202               Got reply to FUNC_ID_SERIAL_API_GET_INIT_DATA: <0xb7996b90>
36   02/01/09 0:00:22.202               found node 1 <0xb7996b90>
36   02/01/09 0:00:22.202               found node 2 <0xb7996b90>
36   02/01/09 0:00:22.202               found node 3 <0xb7996b90>
36   02/01/09 0:00:22.202               found node 4 <0xb7996b90>
36   02/01/09 0:00:22.202               found node 5 <0xb7996b90>
36   02/01/09 0:00:22.202               found node 6 <0xb7996b90>
36   02/01/09 0:00:22.202               found node 7 <0xb7996b90>
36   02/01/09 0:00:22.202               found node 8 <0xb7996b90>
40   02/01/09 0:00:22.301               Sending job 0x8083098 (cb 0) - 0x1 0x4 0x0 0x41 0x1 0xbb (###A##) <0xb7996b90>
41   02/01/09 0:00:22.302               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.303               0x1 0x9 0x1 0x41 0xd2 0x6 0x0 0x2 0x2 0x1 0x63 (###A######c) <0xb7996b90>
36   02/01/09 0:00:22.304               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:22.304               ***FOUND NODE: 1 <0xb7996b90>
36   02/01/09 0:00:22.304               listening node <0xb7996b90>
36   02/01/09 0:00:22.304               optional functionality <0xb7996b90>
36   02/01/09 0:00:22.304               BASIC TYPE: Static Controller <0xb7996b90>
36   02/01/09 0:00:22.304               GENERIC TYPE: Static Controller <0xb7996b90>
36   02/01/09 0:00:22.304               SPECIFIC TYPE: 1 <0xb7996b90>
40   02/01/09 0:00:22.401               Sending job 0x80832b8 (cb 0) - 0x1 0x4 0x0 0x41 0x2 0xb8 (###A##) <0xb7996b90>
41   02/01/09 0:00:22.402               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.403               0x1 0x9 0x1 0x41 0x0 0x0 0x0 0x3 0x0 0x0 0xb5 (###A#######) <0xb7996b90>
36   02/01/09 0:00:22.404               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:22.404               Invalid generic class (0), ignoring device <0xb7996b90>
40   02/01/09 0:00:22.501               Sending job 0x80834d8 (cb 0) - 0x1 0x4 0x0 0x41 0x3 0xb9 (###A##) <0xb7996b90>
41   02/01/09 0:00:22.502               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.503               0x1 0x9 0x1 0x41 0x0 0x0 0x0 0x3 0x0 0x0 0xb5 (###A#######) <0xb7996b90>
36   02/01/09 0:00:22.503               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:22.504               Invalid generic class (0), ignoring device <0xb7996b90>
40   02/01/09 0:00:22.601               Sending job 0x80836f8 (cb 0) - 0x1 0x4 0x0 0x41 0x4 0xbe (###A##) <0xb7996b90>
41   02/01/09 0:00:22.602               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.603               0x1 0x9 0x1 0x41 0x0 0x0 0x0 0x3 0x0 0x0 0xb5 (###A#######) <0xb7996b90>
36   02/01/09 0:00:22.603               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:22.604               Invalid generic class (0), ignoring device <0xb7996b90>
40   02/01/09 0:00:22.701               Sending job 0x8083918 (cb 0) - 0x1 0x4 0x0 0x41 0x5 0xbf (###A##) <0xb7996b90>
41   02/01/09 0:00:22.702               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.703               0x1 0x9 0x1 0x41 0x0 0x0 0x0 0x3 0x0 0x0 0xb5 (###A#######) <0xb7996b90>
36   02/01/09 0:00:22.703               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:22.704               Invalid generic class (0), ignoring device <0xb7996b90>
40   02/01/09 0:00:22.801               Sending job 0x809afc0 (cb 0) - 0x1 0x4 0x0 0x41 0x6 0xbc (###A##) <0xb7996b90>
41   02/01/09 0:00:22.802               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.803               0x1 0x9 0x1 0x41 0x0 0x0 0x0 0x3 0x0 0x0 0xb5 (###A#######) <0xb7996b90>
36   02/01/09 0:00:22.803               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:22.804               Invalid generic class (0), ignoring device <0xb7996b90>
40   02/01/09 0:00:22.901               Sending job 0x809b1e0 (cb 0) - 0x1 0x4 0x0 0x41 0x7 0xbd (###A##) <0xb7996b90>
41   02/01/09 0:00:22.902               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.903               0x1 0x9 0x1 0x41 0x0 0x0 0x0 0x3 0x0 0x0 0xb5 (###A#######) <0xb7996b90>
36   02/01/09 0:00:22.903               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:22.904               Invalid generic class (0), ignoring device <0xb7996b90>
40   02/01/09 0:00:23.001               Sending job 0x809b400 (cb 0) - 0x1 0x4 0x0 0x41 0x8 0xb2 (###A##) <0xb7996b90>
41   02/01/09 0:00:23.002               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:23.003               0x1 0x9 0x1 0x41 0x0 0x0 0x0 0x3 0x0 0x0 0xb5 (###A#######) <0xb7996b90>
36   02/01/09 0:00:23.003               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:23.003               Invalid generic class (0), ignoring device <0xb7996b90>
36   02/01/09 0:00:23.004               Finished building node list: <0xb7996b90>
36   02/01/09 0:00:23.004               Node: 1 basic: 2 generic: 2 specific: 1 pluto: 0 <0xb7996b90>
36   02/01/09 0:00:23.004               Received command #756 - Report Child Devices <0xb7996b90>
36   02/01/09 0:00:23.004               Reporting child devices <0xb7996b90>
05   02/01/09 0:00:30.498               Creating child 32 <0xb79976c0>
05   02/01/09 0:00:30.498               Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb79976c0>
05   02/01/09 0:00:30.498               Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb79976c0>
05   02/01/09 0:00:30.498               Creating child 33 <0xb79976c0>
05   02/01/09 0:00:30.498               Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb79976c0>
05   02/01/09 0:00:30.498               Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb79976c0>
36   02/01/09 0:00:53.185               We have been idle for 30 seconds, polling device states <0xb7996b90>
40   02/01/09 0:00:53.285               Sending job 0x809fa60 (cb 1) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x1 0x3e (###### ###>) <0xb7996b90>
41   02/01/09 0:00:53.286               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:53.288               0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0xb7996b90>
36   02/01/09 0:00:53.288               ZW_SEND delivered to Z-Wave stack <0xb7996b90>
41   02/01/09 0:00:53.309               0x1 0x5 0x0 0x13 0x1 0x0 0xe8 (#######) <0xb7996b90>
36   02/01/09 0:00:53.309               ZW_SEND Response with callback 1 received <0xb7996b90>
36   02/01/09 0:00:53.309               ZW_SEND was successful, removing job <0xb7996b90>

linuxmce@dcerouter:/var/log/pluto$
-johan
Title: Re: New Z-Wave driver
Post by: hari on February 01, 2009, 10:27:07 am
Quote
05   02/01/09 0:00:10.163               Socket::ReceiveData 0x807a2c0 failed, bytes left 0 start: 10000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 7 Command_Impl1 Dev #31 <0xb68bab90>
05   02/01/09 0:00:10.164               Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Command_Impl1 Dev #31 <0xb68bab90>
01   02/01/09 0:00:10.164               Receive string failed in HandleRequestSocket 18:ReceiveData failed Command_Impl1 Dev #31 <0xb68bab90>

that error looks strange... the DCErouter sends us crap. This is a fresh 0710?

br, Hari
Title: Re: New Z-Wave driver
Post by: johanr on February 01, 2009, 05:02:32 pm
Aha! amazing.. and that you could see on the message that was being sent  :o

no, having issues with my ISP connection so I couldn't download a fresh one(actually did not know it was being updated regularly)
Ok, so I download a fresh one then. Thanks!
 :)


-johan

Title: Re: New Z-Wave driver
Post by: hari on February 01, 2009, 06:01:41 pm
aeh no. I meant "fresh installation" not "fresh media".

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: johanr on February 01, 2009, 11:33:26 pm
ok, need to specify more I think. The install is what I call "clean install" meaning that the disk is wiped during install(also used another hdd than the 64bit installed one since I have all media still on that one)
The driver is however the latest downloaded(wget) from your site (sorry for the Su-31 btw it's a nice plane)

Funny thing is that now when I rolled the driver back again just to get it working for the week.  I can still not add any devices using the tricklestar. It turns red really fast, as it was reading the info sent and denied it. But the Seluxit is responding again :)

-johan
Title: Re: New Z-Wave driver
Post by: hari on February 02, 2009, 12:02:24 am
reset the dongle with the web gui and the remote with the procedure from the manual. Then do the download configuration procedure. After that add your devices with the remote. Do all that with the new driver. I've had an issue once where the remote did not allow to add new devices until a reset, just flashing red.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: johanr on February 03, 2009, 03:54:53 pm
ok, Thanks. Will try that as soon as I get back home(later this week) just found the manual for the tricklestar.

-johan
Title: Re: New Z-Wave driver
Post by: yannko on February 16, 2009, 03:57:31 pm
Hello  :),

back to some questions about Z-Wave (Seluxit controller and Merten range of products).

I have both Merten push buttons with 2 and 4 ways (respectively 5071xx and 5072xx), which I can use as controller / administrator of the system. My issue is that when I use, for example, the 2 ways button with 2 dimmed-lamps (both are switched and dimmed on and off at the same time by the push button), the info is not sent in linuxmce (for example the floorplan is not updated). If I switch separately each of the lamp in the floorplan, the correct info is then displayed. How could the push button function sends correct status of the devices, or communicate correctly with the Seluxit controller? I run the latest driver that you posted in this topic Hari for 7.10.

My second question is, how to associate the specifics pushing actions of the button (left up, right down, etc...) with a given device (example, left down switches dimmer A on/off, right up switches relay B on/off)?

Last question, do I need absolutely to run Seluxit configuration software in Windows at first, or can I perform all these steps directly in linuxmce, and if yes how (just few hints to understand the principles)?

Thanks a lot for any help, it will be greatly appreciated  ;)!
Title: Re: New Z-Wave driver
Post by: eNoodle on February 16, 2009, 04:49:57 pm
Hey yannko,

I do not own a merten stick, but I also use the Seluxit controller. There was no need to use the Windows software with the Seluxit. However, for association the offered beta software from Seluxit is absolutely ok. You can connect the Seluxit controller to a Windows machine, configure the associations to your needs and then reconnect it to your core (or MD) again. (I powered my core off before I unplugged the device and reconnected it).

I used the Seluxit software to assign all commands to the Seluxit controller, now I get the status submitted to linuxmce correctly.

I do not own any merten switches, but I have some ACT Homepro, they support up to four groups (commands). I either assign them via my ZTH200 (Zwave Remote) or I use the software. I guess you can do the same with your push actions.

eNoodle
Title: Re: New Z-Wave driver
Post by: yannko on February 17, 2009, 02:32:02 pm
Hi eNoodle,

Thanks a lot for your help. I also don't use the merten stick, because it's not supported by linux kernel as wrote Hari.
I tried the solution that your proposed me, but I still can't associate my 4 way switch to make different actions.

If you use the seluxit software, do you configure the devices with the "Start Learn Mode" at first?

How do you make it directly in LinuxMCE without using at all the seluxit software?

Thanks by advance for your help!
Title: Re: New Z-Wave driver
Post by: eNoodle on February 18, 2009, 04:33:41 pm
Hi Yannko,

it should work from within LMCE. Choose your Zwave Interface, Send Comand -> Set Association. Here you have to specify the Sender, the Group and the Transmitter. However, I didn't get it to work within the Webadmin, so I now use the Remote to associate devices.

Using the Seluxit Software is also possible. If you plug in your controller and start the software, you should see all your devices. You can then choose the device of matter, right click on it and choose "Set Association" (could be named something else, I'm not in front of my core right now, so I don't know the correct wording). You can then also choose the group (which represents your four functions). I guess you couls also set the association from within the property box on the right hand side, but haven't tested this.

eNoodle
Title: Re: New Z-Wave driver
Post by: yannko on February 18, 2009, 07:08:24 pm
eNoodle,

Thanks again for your answer. Well, it's really tricky: if I use lmce to send the association groups, I have one light which is correctly associated, and the second not, when I check after in the Seluxit software. And I have no way at all to set the group association in Seluxit software, I can't control the group association. I have just the "Associate to node" action from the right click menu, when done on a given node (one dimmer or relay for example), but no group association.

I would like to do the following setup, consisting of a Seluxit USB controller, a Merten 4 way switch (5072xx), and 2 Merten relays.

Association group 1 of the 4 way switch (left top) to switch on the first relay. Parameter number 0 (?).
Association group 2 (left bottom) to switch off the first relay. Parameter number 1
Association group 3 (right top) to switch on the second relay. Parameter number 2
Association group 4 (right bottom) to switch off the second relay. Parameter number 3

Is there something to do with the "parameter number" for each of these groups? What does it exactly represents?

Also the main thing would be to have these infos correctly updated on the orbiter's floorplan.

Which version of lmce are you running? Do you have your floorplan correctly updated when using your 4 way switch?

Many thanks!
Title: Re: New Z-Wave driver
Post by: hari on February 18, 2009, 07:20:10 pm
the n-way things are a bit tricky. Z-Wave is not a "bus", so only the addressed devices see commands. The code usually adds an association for the regular switches and dimmers. So when they are operated locally, like the merten ones, they also send a command to the core, as we are in group 1. When they are operated remotely, they don't send a command to their group 1 associated peers.

Solution: Read out the association of the remote switch and store them in the DB (the new code already manages the child devices on its own and stores e.g. capabilities for each device, learned from the node info frame at association). We then put the dongle of the core into all groups of the remote switch. So every button press sends a command to the core, too. We then have to traverse the association list and send commands to request the actual levels from the devices. This was already implemented as proof of concept for the ACT remote switches, but abandoned as it forced me to read all associations at every startup in the past. You cannot do that for battery powered remote switches. There is also a new remote switch device template in 0810, so this will work on the long term. For now, the network is polled after 30 seconds of no activity, so you still have the correct floorplan status when you use the orbiter to check if you left the lights on in a room for example.. and you seldom toggle a light and then instantly jump to the orbiter to see if the status is correct (except for testing :-) )

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: yannko on March 03, 2009, 02:58:24 pm
Hari, many thanks for this very complete and technical answer. I finally managed to do everything I wanted using the Merten software, and then passing the configuration to LinuxMCE on the Seluxit controller.
This main issue I had with Merten binary switches (battery powered) could be solved like that, and the polling every 30s effectively updates the floorplan in the Orbiter.
It's nice to see the progresses of the Z-Wave development, thanks a lot for all the support!  :)
Title: Re: New Z-Wave driver
Post by: hari on March 03, 2009, 06:49:10 pm
You are welcome. Reminds me that I need to code an improved job handler.

br, Hari
Title: Re: New Z-Wave driver
Post by: hari on April 14, 2009, 06:03:38 pm
the 0810 z-wave package from yesterday has regular thermostat support. Would be cool if somebody could test it, I have none here..

br, Hari
Title: Re: New Z-Wave driver
Post by: pga57 on April 15, 2009, 09:03:04 pm
Hello Hari,

Yesterday we discuss (on irc) a problem I had with my zwave setup.
After correction of my setup, the network worked again.
But this evening I does not work anymore, without changing anything :-(.
I've just configurate last evening some timed events to open and close my 3 electric stores.
I've post my zwave log at http://pastebin.com/m192ed64a

Can you look at it and explain me what's append ?
The error begin at 08:37:48.

Thank's,
Philippe
Title: Re: New Z-Wave driver
Post by: hari on April 15, 2009, 09:18:37 pm
what devices do you use? Did all stop working?  I'd need a device list and the output of the z-wave log at startup. From the logs it looks like the devices are not reachable (the ZW SEND gets delivered to the stack, but we never receive the acknowledge that the frame has been sent.

br, Hari
Title: Re: New Z-Wave driver
Post by: pga57 on April 15, 2009, 09:30:05 pm
I use:
3 x Merten Blind control (580699) + Radio shutter push-button (504519)
2 x HomePro ZRP230 (plug-in appliance)
2 x HomePro ZDP230 (plug-in lamp module)

They all stop working.
It is like the zwave stick does not work anymore.

I had the same problem and re-installed all (driver etc..) after a delete but prefer now search the cause of the problem.

Philippe
Title: Re: New Z-Wave driver
Post by: hari on April 15, 2009, 10:50:58 pm
what do you use as remote controller? How did you learn the units into the system?

From a driver perspective, there is nothing more one can do than to issue the ZW_SEND command. If it fails, the driver retries 2 times. I'd assume your mesh is not working properly or your stick has a defect.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: pga57 on April 16, 2009, 06:59:02 am
My remote controleur is a Tricklestar 200ZW-EU-W and the stick is a Tricklestar 300ZW-EU-W.
I use the SIS mode I've find in the Zwave wiki.
It worked for about 1 month (with 1 shutter only) without problem.

I think like you that the stick has a defect.
I've order another one (Seluxit now) to verify

Best regards,
Philippe

Title: Re: New Z-Wave driver
Post by: hari on April 16, 2009, 12:28:08 pm
strange, i'm seeing the exact same thing here since yesterday night. The tricklestar dongle worked for months now without issues. Rumor says the 5.x firmware is way bad as zensys did massive changes to support encyption. They even forked a 4.x firmware for that reason.

I'll switch back to the Seluxit this evening..

br, Hari
Title: Re: New Z-Wave driver
Post by: hari on April 16, 2009, 08:47:20 pm
just as a note, the issues are not yet fully investigated:

* The recent 5.x firmwares can be problematic (MCV, tricklestar dongle). We've seen two occurences of the Tricklestar stick to suddenly suspend operation. For a rock solid install use either the seluxit (EU) or the intermatic (US) dongle. The problems are big enough that zensys even forked the 4.x version for the latest chips..

* The Tricklestar remote has issues in SIS mode. The add node procedure stops working after a few inclusions (no clear pattern yet). 0710 has no direct workaround, 0810 allows to do a "remove node" and "add node" to re-include it as inclusion controller (exclude, factory reset, include again). 0710 users can do the same with a "z-wave tool".

* The merten battery powered remote switches can get permanently "disabled" by doing the following:

- add to the network (only tested with sis)
- do a reset unit (e.g. from the ZTH200)

There might be other scenarios to "kill them". Not even the low level merten tool to unlock "active protection" can access them any more

I'll provide updates when I have more information.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: hari on April 16, 2009, 10:12:09 pm
I would think that especially with these units, it's essential then to first remove from the network before doing _anything_ else... Of course, we all do that anyway  ;D
*evil grin*

yes, absolutely, that is a very important point. Dunno about the age of the parts..

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: pga57 on April 17, 2009, 08:43:44 am
Strange...this morning my shutters were reopened without changing my config and I can control my lights again.
It appears that the system work after a while.
The Zwave log seems ok.

Philippe

Title: Remote also broken ?
Post by: Viking on April 26, 2009, 04:56:32 pm
Hi,

My remote is probably also broken :(

I am just now working on including some devices in my zwave network using SIS mode. I did some testing up til now with two ACT light switches (one dimmer an one switch). And added and removed the same devices a couple of times. Yesterday I removed both of them an started adding the first one again (the swithch) and that did work and does still work. The USB dongle is OK.

Now I wanted to add the second one (and some more devices) but including was not 100% successfull as I could not switch the dimmer. So i removed the dimmer again - the first time did not work, so I tried a second time and that worked.

After that the 200ZW-EU-W remote does not show any lights when pressing the buttons :(

What can I do now ? I am using 0710.

Should I try resetting the remote ?

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: Viking on April 26, 2009, 05:26:17 pm
Hi again,

what I forgot. The remote does also not charge when attached to an USB port.

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: Viking on April 27, 2009, 09:20:07 am
Hi Hari,

* The recent 5.x firmwares can be problematic (MCV, tricklestar dongle). We've seen two occurences of the Tricklestar stick to suddenly suspend operation. For a rock solid install use either the seluxit (EU) or the intermatic (US) dongle. The problems are big enough that zensys even forked the 4.x version for the latest chips..

How do I check what firmware I have ? And where can we find a 4.x for the Tricklestar 300ZW-EU-W ? (google and tricklestar homepage did not give me any hints)

Quote
* The Tricklestar remote has issues in SIS mode. The add node procedure stops working after a few inclusions (no clear pattern yet). 0710 has no direct workaround, 0810 allows to do a "remove node" and "add node" to re-include it as inclusion controller (exclude, factory reset, include again). 0710 users can do the same with a "z-wave tool".

Will that also help if the remote does not do anything anymore. Meaning no lights when pressing the button ?

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: hari on April 28, 2009, 05:09:44 pm
Will that also help if the remote does not do anything anymore. Meaning no lights when pressing the button ?

in config mode? that sounds way broken. When my remote locks up it behaves as intended, just does not include stuff (blinks red instead of green).
Title: Re: New Z-Wave driver
Post by: hari on April 28, 2009, 05:13:23 pm
just as a note, the issues are not yet fully investigated:
* The recent 5.x firmwares can be problematic (MCV, tricklestar dongle).
Hi,
Just received a tricklestar dongle. I used to have lots of issues with my MCV dongle, mainly zwave functionality suddenly disappearing. I had someone suggest the tricklestar, but some strange things happen with it. If you have a minute, look at this:

oh, you are the first one reporting problems with the MCV dongle. It has the same library version as the Tricklestar (5.02 iirc). I'll look at the network HAIL command, maybe it helps in that regard. The author of the MCV z-wave stack told me that he had similiar problems recently, I'll try to find out how they worked around (I assume "HAIL" but I have to look more closely after my hollidays).

br, Hari
Title: Re: New Z-Wave driver
Post by: totallymaxed on May 03, 2009, 05:22:00 pm
Just received a tricklestar dongle. I used to have lots of issues with my MCV dongle, mainly zwave functionality suddenly disappearing.
oh, you are the first one reporting problems with the MCV dongle. It has the same library version as the Tricklestar (5.02 iirc). I'll look at the network HAIL command, maybe it helps in that regard. The author of the MCV z-wave stack told me that he had similiar problems recently, I'll try to find out how they worked around (I assume "HAIL" but I have to look more closely after my hollidays).

Well,  I do agree it is probably related to the stack/library combo, as I now have totally similar behaviour from the Tricklestar, like this:
Code: [Select]
41      04/29/09 19:22:35.429           ACK RECEIVED <0xb791cb90>
41      04/29/09 19:22:35.429           0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb791cb90>
36      04/29/09 19:22:35.429           ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb791cb90>
36      04/29/09 19:22:38.545           No callback received: await_callback: 212 timer: 31 <0xb791cb90>
40      04/29/09 19:22:38.645           Sending job 0x81db210 (cb 212) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0xd4 0xeb (###### ####) <0xb791cb90>
41      04/29/09 19:22:38.649           ACK RECEIVED <0xb791cb90>
41      04/29/09 19:22:38.649           0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb791cb90>
36      04/29/09 19:22:38.649           ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb791cb90>
36      04/29/09 19:22:41.773           No callback received: await_callback: 212 timer: 31 <0xb791cb90>
40      04/29/09 19:22:41.873           Sending job 0x81db210 (cb 212) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0xd4 0xeb (###### ####) <0xb791cb90>
41      04/29/09 19:22:41.877           ACK RECEIVED <0xb791cb90>
41      04/29/09 19:22:41.877           0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb791cb90>
36      04/29/09 19:22:41.877           ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb791cb90>
36      04/29/09 19:22:45.005           No callback received: await_callback: 212 timer: 31 <0xb791cb90>
36      04/29/09 19:22:45.005           ERROR: Dropping command, no callback received after three resends <0xb791cb90>

Since it only happens after a while, and the zwave stack returns "Error: ZW_SEND failed, retrying <0xb793fb90>" many times before these delivery errors, could it be that the zwave driver be "flooded" with stacked commands?

I will check out the MCV forum, too. Have a nice holiday!


EDIT:  Aaron B let me know that MCV Vera checks if the USB dongle fails to connect to all nodes, and if such is the case, it sends a ZW_Softreset to the dongle. That gets things working again.
I tried to do this (perhaps I made a mistake), but I got a "not implemented" result. Not sure, really, if a ZW_softreset should be the final solution but it is a viable workaround until something better comes up. We can think about the trigger, because if you have 20+ nodes and a polling interval of 30s it would take 10 minutes to discover that the USB stick is messed up...



We've never seen this... so I wonder why that would be?

Andrew
Title: Re: New Z-Wave driver
Post by: hari on May 05, 2009, 06:33:46 pm
the new driver supports the deactivation of polling, but the DCE command is only in 0810 (SetPollingState iirc).

But it's easy to patch that in. But to solve the problem, I'm thinking about an error counter, giving more weight to errors if multiple devices are "failing", with a soft reset if the overall error counter gets too high. I'll play a bit with that this weekend.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: Viking on May 07, 2009, 10:24:34 am
Hi Hari,
just as a note, the issues are not yet fully investigated:

* The recent 5.x firmwares can be problematic (MCV, tricklestar dongle). We've seen two occurences of the Tricklestar stick to suddenly suspend operation. For a rock solid install use either the seluxit (EU) or the intermatic (US) dongle. The problems are big enough that zensys even forked the 4.x version for the latest chips..

I am going to go crazy ... It seem I have really bad luck with my LinuxMCE hardware :(

This now also happened to me. The trickelstar 300ZW-EU-W stopped working a couple of days ago :( It worked for a couple of days and then stopped doing anything :(

Can I somehow find out what firmware I have and mayby downgrade it ?


Here is a log part from now trying to turn a light on.

Code: [Select]
2       05/07/09 10:07:03       35 (spawning-device)    Device requests restart... count=1/50 dev=35
Thu May  7 10:07:03 CEST 2009 Restart
========== NEW LOG SECTION ==========
1       05/07/09 10:07:11       35 (spawning-device)    Starting... 1
1       05/07/09 10:07:11       35 (spawning-device)    Found /usr/pluto/bin/ZWave
36      05/07/09 10:07:25.477           Initialization... <0xb797a6c0>
36      05/07/09 10:07:25.477           Open serial port /dev/ttyUSB0 <0xb797a6c0>
36      05/07/09 10:07:25.514           Get version <0xb797a6c0>
36      05/07/09 10:07:25.514           Get home/node id <0xb797a6c0>
36      05/07/09 10:07:25.514           Get capabilities <0xb797a6c0>
36      05/07/09 10:07:25.514           Get SUC node id <0xb797a6c0>
36      05/07/09 10:07:25.514           Get init data <0xb797a6c0>
36      05/07/09 10:07:25.514           receiveFunction started <0xb7979b90>
36      05/07/09 10:07:28.686           No callback received: await_callback: 134718256 timer: 31 <0xb7979b90>
40      05/07/09 10:07:28.786           Sending job 0x8082b00 (cb 0) - 0x1 0x3 0x0 0x15 0xe9 (#####) <0xb7979b90>
05      05/07/09 10:07:37.524           Creating child 36 <0xb797a6c0>
05      05/07/09 10:07:37.524           Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb797a6c0>
05      05/07/09 10:07:37.524           Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb797a6c0>
05      05/07/09 10:07:37.524           Creating child 37 <0xb797a6c0>
05      05/07/09 10:07:37.524           Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb797a6c0>
05      05/07/09 10:07:37.524           Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb797a6c0>
05      05/07/09 10:07:37.524           Creating child 99 <0xb797a6c0>
05      05/07/09 10:07:37.524           Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0xb797a6c0>
05      05/07/09 10:07:37.524           Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0xb797a6c0>

36      05/07/09 10:08:22.747           Received command for child <0xb6977b90>
36      05/07/09 10:08:22.747           SET LEVEL RECEIVED FOR CHILD 8, level: 100 <0xb6977b90>
That's all there came.

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: Viking on May 07, 2009, 11:01:06 am
HI again,

I unplugged the Tricklestar and inserted it again (and confirmed that it is a zwave device on orbiter). Now it works again.

Still I would like to know how to downgrade firmware and find out what version I have :)

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: Viking on May 12, 2009, 10:16:32 am
Hi again,

yesterday the stick stopped working again :
Code: [Select]
36 05/11/09 16:59:01.390  We have been idle for 30 seconds, polling device states <0xb78bab90>
40 05/11/09 16:59:01.490  Sending job 0x8336fe8 (cb 19) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x13 0x2c (###### ###,) <0xb78bab90>
41 05/11/09 16:59:01.498  ACK RECEIVED <0xb78bab90>
41 05/11/09 16:59:01.498  0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0xb78bab90>
36 05/11/09 16:59:01.498  ZW_SEND delivered to Z-Wave stack <0xb78bab90>
41 05/11/09 16:59:01.518  0x1 0x5 0x0 0x13 0x13 0x0 0xfa (#######) <0xb78bab90>
36 05/11/09 16:59:01.518  ZW_SEND Response with callback 19 received <0xb78bab90>
36 05/11/09 16:59:01.518  ZW_SEND was successful, removing job <0xb78bab90>
41 05/11/09 16:59:01.586  0x1 0x9 0x0 0x4 0x0 0xa 0x3 0x20 0x3 0x0 0xd8 (#####\n# ###) <0xb78bab90>
36 05/11/09 16:59:01.586  FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78bab90>
36 05/11/09 16:59:01.586  COMMAND_CLASS_BASIC -  <0xb78bab90>
36 05/11/09 16:59:01.586  Got basic report from node 10, value: 0 <0xb78bab90>
36 05/11/09 16:59:32.051  We have been idle for 30 seconds, polling device states <0xb78bab90>
40 05/11/09 16:59:32.151  Sending job 0x8337208 (cb 20) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x14 0x2b (###### ###+) <0xb78bab90>
41 05/11/09 16:59:32.155  ACK RECEIVED <0xb78bab90>
41 05/11/09 16:59:32.155  0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0xb78bab90>
36 05/11/09 16:59:32.155  ZW_SEND delivered to Z-Wave stack <0xb78bab90>
41 05/11/09 16:59:32.183  0x1 0x5 0x0 0x13 0x14 0x0 0xfd (#######) <0xb78bab90>
36 05/11/09 16:59:32.184  ZW_SEND Response with callback 20 received <0xb78bab90>
36 05/11/09 16:59:32.184  ZW_SEND was successful, removing job <0xb78bab90>
41 05/11/09 16:59:32.207  0x1 0x9 0x0 0x4 0x0 0x2 0x3 0x20 0x3 0x0 0xd0 (####### ###) <0xb78bab90>
36 05/11/09 16:59:32.208  FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78bab90>
36 05/11/09 16:59:32.208  COMMAND_CLASS_BASIC -  <0xb78bab90>
36 05/11/09 16:59:32.208  Got basic report from node 2, value: 0 <0xb78bab90>
41 05/11/09 16:59:32.331  0x1 0x9 0x0 0x4 0x0 0xa 0x3 0x20 0x3 0x0 0xd8 (#####\n# ###) <0xb78bab90>
36 05/11/09 16:59:32.332  FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78bab90>
36 05/11/09 16:59:32.332  COMMAND_CLASS_BASIC -  <0xb78bab90>
36 05/11/09 16:59:32.332  Got basic report from node 10, value: 0 <0xb78bab90>
05 05/11/09 17:00:01.818  void ClientSocket::Disconnect() on this socket: 0x807a1c0 (m_Socket: 7) <0xb78bb6c0>
Return code: 0
2 05/11/09 17:00:01 35 (spawning-device) Shutting down... count=2/50 dev=35
Mon May 11 17:00:01 CEST 2009 Shutdown

Did not use Linuxmce at all yesterday. And today I was told to reload router - and after that the ZWave stick was detected again and I was asked if it is an Serial or ZWave device.

The restart I have posted here. It seems to work after the quick reload, but it is very anoying.

Posted the log of the restart here :
http://pastebin.com/f6b61b6e7

I don't understand why it found 16 nodes !?  I had some trouble getting the new Inclusion stick working so I added some of the devces and removed them afain a couple of times. But the highest number of my three devices I have added until now is 10 !?
Maybe someone can enlighten me !?

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: Viking on May 14, 2009, 01:26:39 pm
Hi,

sometime the commands does not work, like this. Node 2 and node 10 (outside lights) are turned on af sunset and node 10 is turned off again at sunrise. (Node 2 is turned off at midnight and that worked, but just to be sure also at sunrise)

The command off is sent, but it is not turned off. As you can see in the last line where it delivers a value of 255.

Any ideas ?

Node 10 is an Merten 507001
Node 2 is an ACT ZRP-200

I am using the ZWave-0.0.2-0710-32bit.bz2 version.
Should I try a newer version of the ZWave programm ? I could setup a developement system on VMware and compile it. But will it work ? And whet version ? Newest or some trunk ?

Code: [Select]
36      05/14/09 5:09:01.160            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/14/09 5:09:01.160            Got basic report from node 10, value: 255 <0xb78d9b90>
36      05/14/09 5:09:01.579            Received command for child <0xb68d7b90>
36      05/14/09 5:09:01.579            OFF RECEIVED FOR CHILD 2 <0xb68d7b90>
36      05/14/09 5:09:01.590            Received command for child <0xb68d7b90>
36      05/14/09 5:09:01.590            OFF RECEIVED FOR CHILD 10 <0xb68d7b90>
40      05/14/09 5:09:01.659            Sending job 0x81503b0 (cb 179) - 0x1 0xa 0x0 0x13 0x2 0x3 0x20 0x1 0x0 0x5 0xb3 0x70 (ESC[31;1m#\n#### ####pESC[0m) <0xb78d9b90>
41      05/14/09 5:09:01.663            ACK RECEIVED <0xb78d9b90>
41      05/14/09 5:09:01.671            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.672            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/14/09 5:09:01.716            0x1 0x5 0x0 0x13 0xb3 0x0 0x5a (ESC[33;1m######ZESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.716            ZW_SEND Response with callback 179 received <0xb78d9b90>
36      05/14/09 5:09:01.716            ZW_SEND was successful, removing job <0xb78d9b90>
40      05/14/09 5:09:01.816            Sending job 0x81505d0 (cb 180) - 0x1 0xa 0x0 0x13 0xa 0x3 0x20 0x1 0x0 0x5 0xb4 0x7f (ESC[31;1m#\n##\n# #####ESC[0m) <0xb78d9b90>
41      05/14/09 5:09:01.824            ACK RECEIVED <0xb78d9b90>
41      05/14/09 5:09:01.824            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.824            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/14/09 5:09:01.988            0x1 0x5 0x0 0x13 0xb4 0x0 0x5d (ESC[33;1m######]ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.988            ZW_SEND Response with callback 180 received <0xb78d9b90>
36      05/14/09 5:09:01.988            ZW_SEND was successful, removing job <0xb78d9b90>
36      05/14/09 5:09:32.809            We have been idle for 30 seconds, polling device states <0xb78d9b90>
40      05/14/09 5:09:32.913            Sending job 0x81507f0 (cb 181) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0xb5 0x8a (ESC[31;1m###### ####ESC[0m) <0xb78d9b90>
41      05/14/09 5:09:32.921            ACK RECEIVED <0xb78d9b90>
41      05/14/09 5:09:32.921            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:32.921            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/14/09 5:09:32.945            0x1 0x5 0x0 0x13 0xb5 0x0 0x5c (ESC[33;1m######\ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:32.945            ZW_SEND Response with callback 181 received <0xb78d9b90>
36      05/14/09 5:09:32.945            ZW_SEND was successful, removing job <0xb78d9b90>
41      05/14/09 5:09:32.965            0x1 0x9 0x0 0x4 0x0 0x2 0x3 0x20 0x3 0x0 0xd0 (ESC[33;1m####### ###ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:32.965            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/14/09 5:09:32.965            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/14/09 5:09:32.965            Got basic report from node 2, value: 0 <0xb78d9b90>
41      05/14/09 5:09:33.209            0x1 0x9 0x0 0x4 0x0 0xa 0x3 0x20 0x3 0xff 0x27 (ESC[33;1m#####\n# ##'ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:33.209            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/14/09 5:09:33.209            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/14/09 5:09:33.209            Got basic report from node 10, value: 255 <0xb78d9b90>

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: hari on May 14, 2009, 01:33:49 pm
the merten got switched off, but not the ACT. I don't see any errors in the logs. I'd suggest to replace the ZRP. I also have one going havoc here sometimes..

br, Hari
Title: Re: New Z-Wave driver
Post by: Viking on May 18, 2009, 04:35:30 pm
the merten got switched off, but not the ACT. I don't see any errors in the logs. I'd suggest to replace the ZRP. I also have one going havoc here sometimes..

Well, I now have ordered an Innovus - I really hope thats better ...

Thanks for your efforts on this :)

BTW. would it make sence to compile a newer version of your ZWave program and test that ?

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: hari on May 18, 2009, 05:51:16 pm
the latest driver has some improvements and bugfixes.. so it is always worth compiling if you ask me :-) Look at the changelog in trac for specific changes.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: Viking on May 21, 2009, 12:09:49 am
Hi Hari,

what do I do to get the new Innovus running. Can I resuse the config in the SIS inclusion remote or do I have to
1. exclude all devices again
2. reset the SIS remote ?
3. remove the old ZWave controller
4. add the new ZWave controller
5. and then folow the SIS "manual" instructions from the wiki.

I tried just unplugging the old Zwave controller and plugging the inovus in. But the SIS remote did not want to enter configuration mode (hold up key and then press up short). It always gave me a red light.

Thanks
Viking
Title: Re: New Z-Wave driver
Post by: Viking on May 28, 2009, 09:35:33 am
Hi,

this problem is not fixed using the Innovus controller.

Hi,

sometime the commands does not work, like this. Node 2 and node 10 (outside lights) are turned on af sunset and node 10 is turned off again at sunrise. (Node 2 is turned off at midnight and that worked, but just to be sure also at sunrise)

The command off is sent, but it is not turned off. As you can see in the last line where it delivers a value of 255.

Any ideas ?

Node 10 is an Merten 507001
Node 2 is an ACT ZRP-200

I am using the ZWave-0.0.2-0710-32bit.bz2 version.
Should I try a newer version of the ZWave programm ? I could setup a developement system on VMware and compile it. But will it work ? And whet version ? Newest or some trunk ?

Code: [Select]
36      05/14/09 5:09:01.160            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/14/09 5:09:01.160            Got basic report from node 10, value: 255 <0xb78d9b90>
36      05/14/09 5:09:01.579            Received command for child <0xb68d7b90>
36      05/14/09 5:09:01.579            OFF RECEIVED FOR CHILD 2 <0xb68d7b90>
36      05/14/09 5:09:01.590            Received command for child <0xb68d7b90>
36      05/14/09 5:09:01.590            OFF RECEIVED FOR CHILD 10 <0xb68d7b90>
40      05/14/09 5:09:01.659            Sending job 0x81503b0 (cb 179) - 0x1 0xa 0x0 0x13 0x2 0x3 0x20 0x1 0x0 0x5 0xb3 0x70 (ESC[31;1m#\n#### ####pESC[0m) <0xb78d9b90>
41      05/14/09 5:09:01.663            ACK RECEIVED <0xb78d9b90>
41      05/14/09 5:09:01.671            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.672            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/14/09 5:09:01.716            0x1 0x5 0x0 0x13 0xb3 0x0 0x5a (ESC[33;1m######ZESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.716            ZW_SEND Response with callback 179 received <0xb78d9b90>
36      05/14/09 5:09:01.716            ZW_SEND was successful, removing job <0xb78d9b90>
40      05/14/09 5:09:01.816            Sending job 0x81505d0 (cb 180) - 0x1 0xa 0x0 0x13 0xa 0x3 0x20 0x1 0x0 0x5 0xb4 0x7f (ESC[31;1m#\n##\n# #####ESC[0m) <0xb78d9b90>
41      05/14/09 5:09:01.824            ACK RECEIVED <0xb78d9b90>
41      05/14/09 5:09:01.824            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.824            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/14/09 5:09:01.988            0x1 0x5 0x0 0x13 0xb4 0x0 0x5d (ESC[33;1m######]ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.988            ZW_SEND Response with callback 180 received <0xb78d9b90>
36      05/14/09 5:09:01.988            ZW_SEND was successful, removing job <0xb78d9b90>
36      05/14/09 5:09:32.809            We have been idle for 30 seconds, polling device states <0xb78d9b90>
40      05/14/09 5:09:32.913            Sending job 0x81507f0 (cb 181) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0xb5 0x8a (ESC[31;1m###### ####ESC[0m) <0xb78d9b90>
41      05/14/09 5:09:32.921            ACK RECEIVED <0xb78d9b90>
41      05/14/09 5:09:32.921            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:32.921            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/14/09 5:09:32.945            0x1 0x5 0x0 0x13 0xb5 0x0 0x5c (ESC[33;1m######\ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:32.945            ZW_SEND Response with callback 181 received <0xb78d9b90>
36      05/14/09 5:09:32.945            ZW_SEND was successful, removing job <0xb78d9b90>
41      05/14/09 5:09:32.965            0x1 0x9 0x0 0x4 0x0 0x2 0x3 0x20 0x3 0x0 0xd0 (ESC[33;1m####### ###ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:32.965            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/14/09 5:09:32.965            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/14/09 5:09:32.965            Got basic report from node 2, value: 0 <0xb78d9b90>
41      05/14/09 5:09:33.209            0x1 0x9 0x0 0x4 0x0 0xa 0x3 0x20 0x3 0xff 0x27 (ESC[33;1m#####\n# ##'ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:33.209            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/14/09 5:09:33.209            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/14/09 5:09:33.209            Got basic report from node 10, value: 255 <0xb78d9b90>

Greetings
Viking

I am now using the Innovus instead of the Tricklestar controller. But unfortunately it also does not wok stable :(

On the Orbiter I got the message "changes happend, I need to reload" - could it be the reason that it did not work ? What could be the reason for this ? Can I somewhere find out what happened that made LinuxMCE want to do a quick reload ?
I did not change anything myself.

Now :
Node 4 is the Merten 507001
Node 3 is the ACT ZRP-200

Node 3 was turned off at midnight (but to be sure it is also turned off at sunrise). And Node 4 should turn off at sunrise - what it not did :(

here are the logs
Code: [Select]
36      05/28/09 4:46:50.165            We have been idle for 30 seconds, polling device states <0xb78d9b90>
40      05/28/09 4:46:50.265            Sending job 0x8479ac8 (cb 183) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0xb7 0x88 (ESC[31;1m###### ####ESC[0m
) <0xb78d9b90>
41      05/28/09 4:46:50.266            ACK RECEIVED <0xb78d9b90>
41      05/28/09 4:46:50.268            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/28/09 4:46:50.268            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/28/09 4:46:50.290            0x1 0x5 0x0 0x13 0xb7 0x0 0x5e (ESC[33;1m######^ESC[0m) <0xb78d9b90>
36      05/28/09 4:46:50.290            ZW_SEND Response with callback 183 received <0xb78d9b90>
36      05/28/09 4:46:50.290            ZW_SEND was successful, removing job <0xb78d9b90>
41      05/28/09 4:46:50.314            0x1 0x9 0x0 0x4 0x0 0x3 0x3 0x20 0x3 0x0 0xd1 (ESC[33;1m####### ###ESC[0m) <0xb78d9b90>
36      05/28/09 4:46:50.314            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/28/09 4:46:50.314            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/28/09 4:46:50.314            Got basic report from node 3, value: 0 <0xb78d9b90>
41      05/28/09 4:46:50.395            0x1 0x9 0x0 0x4 0x0 0x4 0x3 0x20 0x3 0xff 0x29 (ESC[33;1m####### ##)ESC[0m) <0xb78d9b90>
36      05/28/09 4:46:50.396            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/28/09 4:46:50.396            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/28/09 4:46:50.396            Got basic report from node 4, value: 255 <0xb78d9b90>
36      05/28/09 4:47:20.930            We have been idle for 30 seconds, polling device states <0xb78d9b90>
40      05/28/09 4:47:21.030            Sending job 0x8479ce8 (cb 184) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0xb8 0x87 (ESC[31;1m###### ####ESC[0m
) <0xb78d9b90>
41      05/28/09 4:47:21.032            ACK RECEIVED <0xb78d9b90>
41      05/28/09 4:47:21.034            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:21.034            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/28/09 4:47:21.054            0x1 0x5 0x0 0x13 0xb8 0x0 0x51 (ESC[33;1m######QESC[0m) <0xb78d9b90>
36      05/28/09 4:47:21.055            ZW_SEND Response with callback 184 received <0xb78d9b90>
36      05/28/09 4:47:21.055            ZW_SEND was successful, removing job <0xb78d9b90>
41      05/28/09 4:47:21.079            0x1 0x9 0x0 0x4 0x0 0x3 0x3 0x20 0x3 0x0 0xd1 (ESC[33;1m####### ###ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:21.079            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/28/09 4:47:21.079            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/28/09 4:47:21.079            Got basic report from node 3, value: 0 <0xb78d9b90>
41      05/28/09 4:47:21.161            0x1 0x9 0x0 0x4 0x0 0x4 0x3 0x20 0x3 0xff 0x29 (ESC[33;1m####### ##)ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:21.161            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/28/09 4:47:21.161            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/28/09 4:47:21.161            Got basic report from node 4, value: 255 <0xb78d9b90>
36      05/28/09 4:47:22.283            Received command for child <0xb68d7b90>
36      05/28/09 4:47:22.284            OFF RECEIVED FOR CHILD 4 <0xb68d7b90>
36      05/28/09 4:47:22.285            Received command for child <0xb68d7b90>
36      05/28/09 4:47:22.285            OFF RECEIVED FOR CHILD 3 <0xb68d7b90>
40      05/28/09 4:47:22.286            Sending job 0x8479f08 (cb 185) - 0x1 0xa 0x0 0x13 0x4 0x3 0x20 0x1 0x0 0x5 0xb9 0x7c (ESC[31;1m#\n#### ####|ESC[0m) <0xb78d9b90>
41      05/28/09 4:47:22.288            ACK RECEIVED <0xb78d9b90>
41      05/28/09 4:47:22.291            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:22.291            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/28/09 4:47:22.334            0x1 0x5 0x0 0x13 0xb9 0x0 0x50 (ESC[33;1m######PESC[0m) <0xb78d9b90>
36      05/28/09 4:47:22.334            ZW_SEND Response with callback 185 received <0xb78d9b90>
36      05/28/09 4:47:22.334            ZW_SEND was successful, removing job <0xb78d9b90>
40      05/28/09 4:47:22.439            Sending job 0x847a128 (cb 186) - 0x1 0xa 0x0 0x13 0x3 0x3 0x20 0x1 0x0 0x5 0xba 0x78 (ESC[31;1m#\n#### ####xESC[0m) <0xb78d9b90>
41      05/28/09 4:47:22.442            ACK RECEIVED <0xb78d9b90>
41      05/28/09 4:47:22.444            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:22.444            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/28/09 4:47:22.487            0x1 0x5 0x0 0x13 0xba 0x0 0x53 (ESC[33;1m######SESC[0m) <0xb78d9b90>
36      05/28/09 4:47:22.487            ZW_SEND Response with callback 186 received <0xb78d9b90>
36      05/28/09 4:47:22.487            ZW_SEND was successful, removing job <0xb78d9b90>
36      05/28/09 4:47:52.927            We have been idle for 30 seconds, polling device states <0xb78d9b90>
40      05/28/09 4:47:53.028            Sending job 0x847a348 (cb 187) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0xbb 0x84 (ESC[31;1m###### ####ESC[0m) <0xb78d9b90>
41      05/28/09 4:47:53.029            ACK RECEIVED <0xb78d9b90>
41      05/28/09 4:47:53.031            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:53.031            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/28/09 4:47:53.052            0x1 0x5 0x0 0x13 0xbb 0x0 0x52 (ESC[33;1m######RESC[0m) <0xb78d9b90>
36      05/28/09 4:47:53.052            ZW_SEND Response with callback 187 received <0xb78d9b90>
36      05/28/09 4:47:53.052            ZW_SEND was successful, removing job <0xb78d9b90>
41      05/28/09 4:47:53.076            0x1 0x9 0x0 0x4 0x0 0x3 0x3 0x20 0x3 0x0 0xd1 (ESC[33;1m####### ###ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:53.076            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/28/09 4:47:53.076            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/28/09 4:47:53.076            Got basic report from node 3, value: 0 <0xb78d9b90>
41      05/28/09 4:47:53.234            0x1 0x9 0x0 0x4 0x0 0x4 0x3 0x20 0x3 0xff 0x29 (ESC[33;1m####### ##)ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:53.234            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/28/09 4:47:53.234            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/28/09 4:47:53.234            Got basic report from node 4, value: 255 <0xb78d9b90>

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: hari on May 28, 2009, 09:41:45 am
i don't see any received DCE commands in that log. Please provide the complete log and tell me the exact timestamps when things did not work. Please have the ACT unit replaced. I really suspect it is flaky.

Btw, what do you mean with innovus controller? A portable controller used as inclusion remote?

br, Hari
Title: Re: New Z-Wave driver
Post by: Viking on May 28, 2009, 10:31:35 am
Hallo Hari,

the ACT works like it should ;), but the Merten is the one that does not always work (ans also did not work the last time). After quick reloading this morning I switched it off using the orbiter and that worked. Unfortunately I did not think about trying to switch it off using the webinterface - maybe that would not work. I will have to try that the next time.

What exactly do you need ? I added the loglevel 36,40 and 41. in /etc/pluto.conf - is that not enough ?

Logfile is attached.

With "Innovus controller" I mean the Innovus Viasens 100 USB.

I am still using the Tricklestar ZW200-EU-W as SIS inclusion controller.


And I am still using the "ZWave-0.0.2-0710-32bit.bz2" driver. I have already compiled a newer one, but not installed it yet.

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: hari on May 28, 2009, 11:10:39 am
The Viasens is from Seluxit, not Innovus ;-)

Does the operation only fail for timed events or also for manual floorplan/web admin operation? Do you have some timestamps for me when problems occured?

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: Viking on May 29, 2009, 11:01:53 am
Uuups, OK then viasens :)

I very rarely turn off theese lights manual. The idea is that the outside lights go on at sunset and the frontlight (Merten) goes off at sunrise. The lights in the garten is turned off at 23:59 (when we go to bed). With the Tricklestar it did not always work with both of them. Very offen it then worked after a quick reload but at least once that did not help. With the Viasens I only had the problem once and there the ACT(garten off at midnight) worked, but the fronside light (merten off at sunrise) did NOT work.

Timestamps - I would say search for "ON" and "OFF" as it is only done very rearely ;) and those at sunset/rise are the ones.

I hope that helps :)

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: Viking on May 29, 2009, 12:53:17 pm
Just FYI

Today it worked again, it will probably work for some days and then stop working again. S

As I noted above IIRC then there always was the "something has changed, reload router?" message on the orbiter when it did not work.

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: Viking on June 01, 2009, 10:07:00 pm
Hi Hari,

tried a newer driver from SVN - compiled fine, but did not work :

Code: [Select]
05      06/01/09 21:05:12.662           void ClientSocket::Disconnect() on this socket: 0x807a1c0 (m_Socket: 7) <0xb78c26c0>
Return code: 2
2       06/01/09 21:05:12       35 (spawning-device)    Device requests restart... count=2/50 dev=35
Mon Jun  1 21:05:12 CEST 2009 Restart
========== NEW LOG SECTION ==========
1       06/01/09 21:05:21       35 (spawning-device)    Starting... 2
1       06/01/09 21:05:21       35 (spawning-device)    Found /usr/pluto/bin/ZWave
Return code: 139
3       06/01/09 21:05:35       35 (spawning-device)    Device died... count=2/50 dev=35
Mon Jun  1 21:05:35 CEST 2009 died
========== NEW LOG SECTION ==========
1       06/01/09 21:05:45       35 (spawning-device)    Starting... 3
1       06/01/09 21:05:45       35 (spawning-device)    Found /usr/pluto/bin/ZWave
Return code: 139
3       06/01/09 21:05:45       35 (spawning-device)    Device died... count=3/50 dev=35
Mon Jun  1 21:05:45 CEST 2009 died

I pressed "Quick reload" and the copied it while it was unloaded. but it somehow died with error code 139.

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: hari on June 02, 2009, 08:08:40 am
139 is a segfault. How did you compile it? Did you mix libraries? If not I'd be interested in the coredump (should be in /usr/pluto/coredump/).

br, Hari
Title: Re: New Z-Wave driver
Post by: hari on June 02, 2009, 08:43:15 am
Hi Viking,

was checking the provided logs, we had no error on the ON commands that I found in the logs:

light has been off, see the polling results:
36   05/27/09 21:50:53.415      Got basic report from node 3, value: 0 <0xb78d9b90>
36   05/27/09 21:50:53.571      Got basic report from node 4, value: 0 <0xb78d9b90>

then we get the DCE command:
36   05/27/09 21:51:01.914      ON RECEIVED FOR CHILD 4 <0xb68d7b90>
36   05/27/09 21:51:01.916      ON RECEIVED FOR CHILD 3 <0xb68d7b90>

we send a job to node 4, after the 0x13 (ZW_SEND) you see the node id (0x4):
40   05/27/09 21:51:02.014      Sending job 0x840e7e8 (cb 141) - 0x1 0xa 0x0 0x13 0x4 0x3 0x20 0x1 0xff 0x5 0x8d 0xb7 (#\n#### #####) <0xb78d9b90>

and we succeed:
36   05/27/09 21:51:02.062      ZW_SEND was successful, removing job <0xb78d9b90>

same for node 3:
40   05/27/09 21:51:02.162      Sending job 0x840ea08 (cb 142) - 0x1 0xa 0x0 0x13 0x3 0x3 0x20 0x1 0xff 0x5 0x8e 0xb3 (#\n#### #####) <0xb78d9b90>
36   05/27/09 21:51:02.210      ZW_SEND was successful, removing job <0xb78d9b90>

next report shows them switched on:
36   05/27/09 21:51:35.264      Got basic report from node 3, value: 255 <0xb78d9b90>
36   05/27/09 21:51:35.420      Got basic report from node 4, value: 255 <0xb78d9b90>


I've also checked the OFF commands, and this is where things get interesting:

node 3 is off and node 4 is on:
36   05/28/09 4:47:21.079      Got basic report from node 3, value: 0 <0xb78d9b90>
36   05/28/09 4:47:21.161      Got basic report from node 4, value: 255 <0xb78d9b90>

we get the OFF:
36   05/28/09 4:47:22.284      OFF RECEIVED FOR CHILD 4 <0xb68d7b90>
36   05/28/09 4:47:22.285      OFF RECEIVED FOR CHILD 3 <0xb68d7b90>

send to 4 and 3, both succeed:
40   05/28/09 4:47:22.286      Sending job 0x8479f08 (cb 185) - 0x1 0xa 0x0 0x13 0x4 0x3 0x20 0x1 0x0 0x5 0xb9 0x7c (#\n#### ####|) <0xb78d9b90>
36   05/28/09 4:47:22.334      ZW_SEND was successful, removing job <0xb78d9b90>
40   05/28/09 4:47:22.439      Sending job 0x847a128 (cb 186) - 0x1 0xa 0x0 0x13 0x3 0x3 0x20 0x1 0x0 0x5 0xba 0x78 (#\n#### ####x) <0xb78d9b90>
36   05/28/09 4:47:22.487      ZW_SEND was successful, removing job <0xb78d9b90>

but on the next report:
36   05/28/09 4:47:53.076      Got basic report from node 3, value: 0 <0xb78d9b90>
36   05/28/09 4:47:53.234      Got basic report from node 4, value: 255 <0xb78d9b90>

Please note that the node 4 is not off. But we got an acknowledge from that exact node that the ZW_SEND did succeed. Did you manually operate it between the OFF and the next polling report?

The third OFF occurence has no errors either:
36   05/27/09 23:59:20.353      OFF RECEIVED FOR CHILD 3 <0xb68d7b90>
40   05/27/09 23:59:20.407      Sending job 0x842fb28 (cb 136) - 0x1 0xa 0x0 0x13 0x3 0x3 0x20 0x1 0x0 0x5 0x88 0x4a (#\n#### ####J) <0xb78d9b90>
36   05/27/09 23:59:20.455      ZW_SEND was successful, removing job <0xb78d9b90>

That makes me assume that you don't have a problem with the DCE Z-Wave driver or the dongle itself. I can't see any errors for the ON/OFF commands in the log. When you further look at the issue, just check for ON/OFF log entries like above. When you see the "ZW_SEND was successful" for that job, everything from the z-wave side is fine for that command.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: hari on June 03, 2009, 12:20:19 pm
i was busy finishing the associaton stuff and supporting non-listening devices without wake up command class. So you can now set associations for e.g. merten remote switches with the  web admin and then tripple press the switch to awake.

I've looked a the needed command for the softreset, is very easy, I'm just thinking about how (and how often) to trigger that. Be prepared to see some code over the next days.

br,Hari
Title: Re: New Z-Wave driver
Post by: hari on June 03, 2009, 10:33:11 pm
the event (on/off) will come soon (already there for EnOcean, just need to implement). Be aware that we are not able to distinguish the different paddles, z-wave does not give us that information.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: caiman on June 03, 2009, 11:01:48 pm
Hi Hari and team,

has anyone tried or made the Schlage z-wave doorlock work with LMCE ?
http://consumer.schlage.com/LiNK/ (http://consumer.schlage.com/LiNK/)

It is sold with its own zwave controller, but of course I would love to integrate it with the existing LMCE network and be able to get notifications in LMCE when someone unlocks the door...
Title: Re: New Z-Wave driver
Post by: hari on June 03, 2009, 11:58:37 pm
encryption support is a different beast, I'm not aware of any secure inclusion controllers. So only pairing in reach of the core, and we'd need a bunch of code for the needed command classes and utilize some aes implementation. I don't think I feel like doing that until those devices are available in Europe. But if you want to look into z-wave development, I can assist you with that task :-)

br, Hari
Title: Re: New Z-Wave driver
Post by: hari on June 04, 2009, 11:32:48 pm
Hi Domodude,

I've added the soft reset to the code. But it is not yet triggered automatically. Would you mind to try the latest svn revision and send a "StatusReport" DCE command to the Z-Wave interface when it locks up? That will do soft reset. If this solves the problem I'll add some error counters and a trigger.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: Viking on June 05, 2009, 03:14:12 pm
139 is a segfault. How did you compile it? Did you mix libraries? If not I'd be interested in the coredump (should be in /usr/pluto/coredump/).

Sorry for the late reply, my house, wife, kids and jobs cost me a lot of time at the moment ;)

Some time ago I did this on my core :

Code: [Select]
svn co http://svn.linuxmce.org/svn/trunk #this will take a while
cd trunk
./configure
make

And when building again I went to the Zwave directory on that checkout, did a svn update (which did not do anything) and then IIRC I did a "make clean" and a "make ; make bin"

What is the right way of doing it ? And what do you mean by "did you mix libraries" ?

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: hari on June 05, 2009, 04:06:34 pm
no, thats not the proper way of doing it. Something like that should work:

Code: [Select]
svn co http://svn.linuxmce.org/svn/branches/LinuxMCE-0710/src LinuxMCE-0710/src
svn co http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src/ZWave LinuxMCE-0810/src/ZWave
cd LinuxMCE-0710/src
cp /usr/pluto/lib/*.so lib/
rm -r ZWave
cp -r ../../LinuxMCE-0810/src/ZWave .
cd ZWave

# edit the file 'Makefile' and remove this line: SNR_CPPFLAGS ?= <-mkr_t_compile_defines->

make bin

(all commands are from memory, so you maybe have to tweak one path or the other)

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: hari on June 05, 2009, 06:24:31 pm
http://vt100.at/files/ZWave-0710-32bit-20090605.bz2

br, Hari
Title: Re: New Z-Wave driver
Post by: hari on June 06, 2009, 12:35:56 am
Hi Domodude,

cool to hear. Yes, watch it for a few days and I'll prepare some code in the meantime.

br, Hari
Title: Re: New Z-Wave driver
Post by: hari on June 06, 2009, 10:25:02 pm
yeah, that script should do the job in the meantime.

Btw, how often does the stick get stuck for you?

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: hari on June 06, 2009, 10:30:28 pm
@domodude: btw, my remote switches are just being reflashed by merten. They should work without issues when I get them back. With the recent code additions, you can set all associations from the web admin for them.

br, Hari
Title: Re: New Z-Wave driver
Post by: pga57 on June 07, 2009, 07:18:50 pm
http://vt100.at/files/ZWave-0710-32bit-20090605.bz2

br, Hari

Hello Hari,

I have those errors when extracting the archive:

linuxmce@dcerouter:~$ sudo tar jxvf ZWave-0710-32bit-20090605.bz2
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Error exit delayed from previous errors

I have made a lot of downloads with the same result :-(
Is the file ok on your side ?

Philippe
Title: Re: New Z-Wave driver
Post by: pga57 on June 07, 2009, 09:03:17 pm
Hi Philippe,

It is not a tar archive. All you need is to bunzip it (command is bunzip2 if I remember correctly).

Good luck,
Mark

[/quote]

Hi Mark,
I thought there was a problem because the input file did not have the same name as the previous version (ZWave-0710-32bit-20090605 instead ZWave).
So, I've use bunzip2 and have install this new version on my core.
I'll see if that corrects the problems that I described
previously (April 15)

Thank's for your help !
Philippe

Title: Re: New Z-Wave driver
Post by: pga57 on June 09, 2009, 07:24:57 am
Hello Hari,

For me, the lastest ZWave driver (ZWave-0710-32bit-20090605.bz2) don't resolve the error I have    
after a few days of proper functioning.
The Seluxit viaSENS Homecontroller give me the same problem I have with my previous Tricklestar 300ZW-EU-W and ZWave-0.0.2-0710-32bit.bz2 driver.

36   06/09/09 7:12:43.254      ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb792fb90>
36   06/09/09 7:12:46.353      No callback received: await_callback: 141 timer: 31 <0xb792fb90>
36   06/09/09 7:12:46.353      ERROR: Dropping command, no callback received after three resends <0xb792fb90>
36   06/09/09 7:13:16.461      We have been idle for 30 seconds, polling device states <0xb792fb90>

Do I set all associations    again?

Philippe
Title: Re: New Z-Wave driver
Post by: pga57 on June 09, 2009, 06:54:41 pm
The StatusReport command works, but ZWave worked again this after-noon without intervention.
I thought the reset would be automatic with this new driver.
I did not translate correctly your exchanges.

Thank you for these details

Philippe
Title: Re: New Z-Wave driver
Post by: hari on June 09, 2009, 09:02:39 pm
mark, did you use the merten tool to setup the network? 10 seconds is nearly the worst case scenario. You should be able to tweak links between devices and get sub-second times. Or is your mesh not dense enough?

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: Viking on June 09, 2009, 10:14:16 pm
http://vt100.at/files/ZWave-0710-32bit-20090605.bz2

Thanks hari :)

I have now installed the new version and will report back what happens.

Greetings
Viking
Title: Re: New Z-Wave driver
Post by: scott on July 29, 2009, 07:09:45 pm
Hi I am new to Zwave development.
For a prototype I was thinking to control a zwave device from my linux box.
I have few quick questions on your zwave driver

1. what USB dongle should I buy to use your zwave driver?

2. what zwave device should I buy to control it from your control point.

Any help is greatly appreciated...

Thanks
scott
Title: Re: New Z-Wave driver
Post by: Murdock on July 29, 2009, 09:26:34 pm
Scott -

  Here's what I'm running right now (not much, but building):
http://wiki.linuxmce.org/index.php/User:Murdock#Z-Wave_Setup

  It's a good starting point for the controller plus a dimmer, my zwave setup was fully plug and play which is really nice.

  All zwave items are here:
http://wiki.linuxmce.org/index.php/Category:ZWave

Ryan
Title: Re: New Z-Wave driver
Post by: scott on July 29, 2009, 11:39:19 pm
Thanks Ryan
I have seen your setup instructions and it seems like I need to install kubuntu to install LinuxMCE. I have both Intel X86 Atom board and Arm board. I am not sure if I can put kubuntu on either of it.

If i attach MiCasa Verde USB Controller to X86 Atom board,
How can my app communicate to  controller? Is there anyway I can download Zwave controller on to my board.

What I was expecting is, there may be Zwave controller souce code which I can put on the board and it will do serial communication to usb dongle. please let me know if iam going in wrong direction.

Thank You
Scott

Title: Re: New Z-Wave driver
Post by: hari on July 30, 2009, 03:00:18 pm
you mean you want to run the Z-Wave driver outside of LinuxMCE, say like in the below listed example on Fedora?

Code: [Select]
[root@test bin]# more /etc/redhat-release
Fedora release 10 (Cambridge)
[root@test bin]# ./ZWave -d 20
ZWave, open edition, v.0.2
Visit www.linuxmce.org for source code and license information

05 07/30/09 14:57:13.696 Creating child 21 <0xb8055a60>
05 07/30/09 14:57:13.697 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb8055a60>
05 07/30/09 14:57:13.697 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb8055a60>
05 07/30/09 14:57:13.697 Creating child 22 <0xb8055a60>
05 07/30/09 14:57:13.698 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb8055a60>
05 07/30/09 14:57:13.698 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb8055a60>
05 07/30/09 14:57:13.715 Router::RemoveAndDeleteSocket 0x8f0ac98 20 <0xaf1f9b90>
05 07/30/09 14:57:16.695 No callback received: await_callback: 3674480 timer: 31 <0xb8054b90>
05 07/30/09 14:57:16.904 Got reply to ZW_MEMORY_GET_ID, Home id: 0x00061e9b, our node id: 1 <0xb8054b90>
05 07/30/09 14:57:17.112 Got reply to GET_SUC_NODE_ID, node: 1 <0xb8054b90>
08 07/30/09 14:57:17.367 Received Message from 20 (ZWave / ) to 4 (unknown / ), type 1 id 718 Command:Create Device, retry none, parameters: <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 2(PK_Device): 0 <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 44(PK_DeviceTemplate): 1945 <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 47(Mac address):  <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 57(PK_Room): 0 <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 58(IP Address):  <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 109(Data String): 12|1 <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 150(PK_DHCPDevice): 0 <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 156(PK_Device_ControlledVia): 20 <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 163(Description):  <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 198(PK_Orbiter): 0 <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 201(PK_Device_Related): 0 <0xb05fbb90>
05 07/30/09 14:57:17.368 Sender: 20 sent message type: 1 ID: 718 and expected a message reply from 4 <0xb05fbb90>
08 07/30/09 14:57:17.473 Received Message from 20 (ZWave / ) to 4 (unknown / ), type 1 id 718 Command:Create Device, retry none, parameters: <0xb05fbb90>
08 07/30/09 14:57:17.473   Parameter 2(PK_Device): 0 <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 44(PK_DeviceTemplate): 37 <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 47(Mac address):  <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 57(PK_Room): 0 <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 58(IP Address):  <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 109(Data String): 12|2 <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 150(PK_DHCPDevice): 0 <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 156(PK_Device_ControlledVia): 20 <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 163(Description):  <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 198(PK_Orbiter): 0 <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 201(PK_Device_Related): 0 <0xb05fbb90>
05 07/30/09 14:57:17.474 Sender: 20 sent message type: 1 ID: 718 and expected a message reply from 4 <0xb05fbb90>
08 07/30/09 14:57:17.579 Received Message from 20 (ZWave / ) to 4 (unknown / ), type 1 id 718 Command:Create Device, retry none, parameters: <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 2(PK_Device): 0 <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 44(PK_DeviceTemplate): 37 <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 47(Mac address):  <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 57(PK_Room): 0 <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 58(IP Address):  <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 109(Data String): 12|3 <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 150(PK_DHCPDevice): 0 <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 156(PK_Device_ControlledVia): 20 <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 163(Description):  <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 198(PK_Orbiter): 0 <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 201(PK_Device_Related): 0 <0xb05fbb90>
05 07/30/09 14:57:17.580 Sender: 20 sent message type: 1 ID: 718 and expected a message reply from 4 <0xb05fbb90>
05 07/30/09 14:57:17.581 Finished building node list: <0xb8054b90>
05 07/30/09 14:57:17.581 Node: 1 basic: 0x2 generic: 0x2 specific: 0x20 pluto: 1945 <0xb8054b90>
05 07/30/09 14:57:17.581 Node: 2 basic: 0x3 generic: 0x10 specific: 0x0 pluto: 37 <0xb8054b90>
05 07/30/09 14:57:17.581 Node: 3 basic: 0x3 generic: 0x10 specific: 0x0 pluto: 37 <0xb8054b90>

br, Hari
Title: Re: New Z-Wave driver
Post by: ivanp on August 04, 2009, 07:07:27 pm
I feel stupid:(.
I have Aeon Labs Z-Wave Interface with built-In Inclusion Remote (EU) and Everspring SP103 Z-Wave Motion Detector and cant get them to work. I paired them together, put Aeon into USB, core picked it up and Sarah video came up. I couldnt finisk the setup, so went to webadmin and there i could see 3 Zwave interfaces: 28 Zwave, 29 Zwave Embedded Climate Interface, 30 ZWave Embedded Security Interface. I manually added Motion detections ensor udner Security, but after i do quick reload of the Core, sensor disappers from the Security.
Next, i downloaded the new Zwave driver, "unziped it" and placed it in usr/pluto/bin/. After it the Zwave device could not start. I renamed it to Zwave, like the original file, but still the same. After putting back the original file all worked ok.
What am i doing wrong? Hoping for any help on this, i am close to pairing the motion detector with my IP camera.
Title: Re: New Z-Wave driver
Post by: davegravy on September 04, 2009, 04:52:02 am
Having a similar issue with the Aeon, but with ACT Homepro Dimmable Lamp Modules. After pairing and pluggin in the stick, it says

"Waiting for the new device to startup..... One moment, please."

Then says

"The device failed to start properly. Something is not right."

Here's the ZWave device log:

Code: [Select]
Return code: 2
2 09/03/09 21:03:51 32 (spawning-device) Device requests restart... count=1/50 dev=32
Thu Sep  3 21:03:51 EDT 2009 Restart
========== NEW LOG SECTION ==========
1 09/03/09 21:03:59 32 (spawning-device) Starting... 1
1 09/03/09 21:03:59 32 (spawning-device) Found ./ZWave
05 09/03/09 21:04:00.020 Creating child 33 <0xb794e6c0>
05 09/03/09 21:04:00.020 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb794e6c0>
05 09/03/09 21:04:00.020 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb794e6c0>
05 09/03/09 21:04:00.021 Creating child 34 <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb794e6c0>
05 09/03/09 21:04:00.021 Creating child 39 <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 1945 that this has no custom event handler for.  It will not fire events. <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 1945 that this has no custom handler for.  This is normal for IR. <0xb794e6c0>
05 09/03/09 21:04:00.021 Creating child 45 <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb794e6c0>
05 09/03/09 21:04:00.021 Creating child 46 <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb794e6c0>
05 09/03/09 21:04:00.021 Creating child 47 <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb794e6c0>
05 09/03/09 21:04:00.021 Creating child 48 <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb794e6c0>
05 09/03/09 21:04:03.117 No callback received: await_callback: -1 timer: 31 <0xb794db90>
05 09/03/09 21:04:03.325 Got reply to ZW_MEMORY_GET_ID, Home id: 0x00061b58, our node id: 1 <0xb794db90>
05 09/03/09 21:04:03.537 Got reply to GET_SUC_NODE_ID, node: 1 <0xb794db90>
05 09/03/09 21:04:04.006 Finished building node list: <0xb794db90>
05 09/03/09 21:04:04.006 Node: 1 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 1945 <0xb794db90>
05 09/03/09 21:04:04.006 Node: 4 basic: 0x3 generic: 0x11 specific: 0x1 pluto: 38 <0xb794db90>
05 09/03/09 21:04:04.006 Node: 5 basic: 0x3 generic: 0x11 specific: 0x1 pluto: 38 <0xb794db90>

EDIT: For shits and giggles, I installed the new driver (even though I'm running 810 and read that it was already included in 810). Everything's running fine now as far as I can tell.
Title: Re: New Z-Wave driver
Post by: hari on September 05, 2009, 04:50:32 am
I manually added Motion detections ensor udner Security, but after i do quick reload of the Core, sensor disappers from the Security.
because you did not include the devices into _your z-wave network_. The z-wave driver gets the node list from the dongle.

I really wish people would read the z-wave manuals that come with the hardware before attempting to do strange things...

Quote
Next, i downloaded the new Zwave driver, "unziped it" and placed it in usr/pluto/bin/. After it the Zwave device could not start. I renamed it to Zwave, like the original file, but still the same. After putting back the original file all worked ok.
What am i doing wrong? Hoping for any help on this, i am close to pairing the motion detector with my IP camera.
Include the devices, then they will show up "automagically".

Hari
Title: Re: New Z-Wave driver
Post by: hari on September 05, 2009, 04:53:38 am
Having a similar issue with the Aeon, but with ACT Homepro Dimmable Lamp Modules.
this is not even slighty related to the previous post.

Quote
EDIT: For shits and giggles, I installed the new driver (even though I'm running 810 and read that it was already included in 810). Everything's running fine now as far as I can tell.

this is not needed and just coincidence. It could be related to the LaunchManager problems, tschak fixed them a few hours ago. You probably rebooted the core or something like that when replacing the binary.

Hari
Title: Re: New Z-Wave driver
Post by: davegravy on September 05, 2009, 05:58:50 am
this is not needed and just coincidence [...] You probably rebooted the core or something like that when replacing the binary.

Hari

Actually I didn't. Before replacing the binary I rebooted, reloaded the router, removed the usb stick, replaced the usb stick, and did a spiritual dance around my CORE about 20 times in just about every possible sequence to no avail. As soon as I replaced the binary it started working instantly.
Title: Re: New Z-Wave driver
Post by: hari on September 05, 2009, 07:10:39 am
are you trying to argue with me over my own code? This is not related to the z-wave driver version.
Title: Re: New Z-Wave driver
Post by: hari on September 05, 2009, 07:12:43 am
btw, the log from your previous post shows perfect operation on the z-wave side.
Title: Re: New Z-Wave driver
Post by: davegravy on September 05, 2009, 05:31:03 pm
are you trying to argue with me over my own code?

Not at all, just posting my observations in the hopes that it may help others in the future.
Title: Re: New Z-Wave driver
Post by: hari on September 05, 2009, 06:30:17 pm
the device startup problem is a general one, not related to z-wave, and was fixed by tschak a few hours ago. The new launchmanager package should prevent those issues from happening, for bluetooth, HID, zwave (either driver), ...

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: Kooma on September 05, 2009, 06:59:56 pm
hari, do you have an idea how long this general startup issues has been present? I've had this annoying bluetooth problem..
PS. Thanks for you work on the Z-wave driver!
Title: Re: New Z-Wave driver
Post by: hari on September 05, 2009, 07:10:36 pm
all 0810 alpha releases are affected, the new launchmanager package should be available very soon.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: PeteK on September 07, 2009, 08:06:20 pm
Hari--

Thanks for the info and again for the driver.  I can confirm that the z-wave devices does start correctly with Thom's updated launch manager.  However, I did notice some quirkiness with the Hybrid orbiter (random orbiter screens appearing and disappearing).  The z-wave interface seems to be working, but I didn't get the wizard that cycled the lights and allowed me assign rooms.  Is this wizard still present or has that gone away.

Thanks!
PeteK
Title: Re: New Z-Wave driver
Post by: tschak909 on September 07, 2009, 08:13:27 pm
Yes, this screen is still present.

-Thom
Title: Re: New Z-Wave driver
Post by: hari on September 07, 2009, 09:52:26 pm
i've never tried to run a z-wave device on a MD..

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: pga57 on September 11, 2009, 06:01:00 pm
Hello Hari,

I had a problem with my remote control and have receive a new one (Tricklestar 200ZW-EU-W).
   
I tried using the SIS mode to register it on the network with a "download configuration" command and have lost my zwave setup ! ;-)
So, I tried to make a new configuration but I can no more include each ZWave devices into the ZWave network.
The remote control do not see them more !

Is there something special to do?

Else, when I do a "quick reload router", I find 4 Zwave Remote Controleur in the device tree !!!
One should suffice no? ;-)
If I delete the 3 last, they reappear after a "quick reload router".

Best Regards,
Philippe
Title: Re: New Z-Wave driver
Post by: hari on September 12, 2009, 03:37:06 pm
when you initiate a download configuration on the lmce side, it will replicate the network information from a controller. LMCE sets the SIS (static update controller with node id server) flags. When you have a recent portable controller, and do the download config step, it will enable the sis. **But it will also remove any stored network information from the dongle on the lmce side**. It will also use the network id of the portable controller. When all your controllers were reset, the portable controller will have node id 1, the static controller (dongle) on the lmce side will have id 2. You then usually start to add other devices.

When the static controller on the lmce side shall be the primary controller, you just send the "reset" command to it with the web admin. It is then the primary static (update) controller (with node id server). You can then use the "add node" command from 0810 to add any inclusion controllers. The static controller will then have node id 1 and use its own factory programmed network id. After that start to add your other z-wave devices. I prefer this approach but it needs 0810 as the add/remove node commands needed for primary operation were not present in 0710.

As you've "lost" your old remote, and you got a new one without any network configuration, you've replicated the "empty" network to the dongle. That is why you've "lost" all devices. Reset all your z-wave nodes and re-add them after doing one of the above initialization methods.

best regards,
Hari
Title: Re: New Z-Wave driver
Post by: pga57 on September 12, 2009, 04:11:07 pm
Thank you Hari for detailed explanations !

I'll try that.

Regards,
Philippe
Title: Re: New Z-Wave driver
Post by: dlewis on September 12, 2009, 04:23:05 pm
This thread is has been locked. If you have specific z-wave issues, please begin a new thread. Thank you!