Messages

1

Users / Re: New Z-Wave driver

« 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! 

2

Users / Re: WAYNE-DALTON Z-WAVE® THERMOSTAT

« on: February 18, 2009, 07:20:36 pm »

Is it only compatible with US frequencies, or a European version exists? (I didn't find it so far). If a 868 MHz is on the market, we would try to integrate it in our system. I would keep you aware in that case Hari.

3

Users / Re: New Z-Wave driver

« 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!

4

Users / Re: WAYNE-DALTON Z-WAVE® THERMOSTAT

« on: February 18, 2009, 02:37:48 pm »

Anybody using this thermostat succesfully in lmce? I would like to integrate this device in our system, it would be great if anybody had some feedback about it! 

5

Users / Re: New Z-Wave driver

« 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!

6

Users / Re: New Z-Wave driver

« 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  !

7

Users / Re: New Z-Wave driver

« 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!

8

Users / Re: New Z-Wave driver

« 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  ! 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.

9

Users / Re: New Z-Wave driver

« 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!

10

Users / Re: New Z-Wave driver

« 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  !
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.

11

Users / Re: New Z-Wave driver

« 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  !

12

Users / Re: New Z-Wave driver

« 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)?

13

Users / Re: New Z-Wave driver

« 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!

14

Users / Re: New Z-Wave driver

« 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!

15

Users / Re: New Z-Wave driver

« 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!