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

KingCrab

  • Regular Poster
  • **
  • Posts: 45
    • View Profile
Re: New Z-Wave driver
« Reply #45 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

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #46 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
rock your home - http://www.agocontrol.com home automation

johanr

  • Veteran
  • ***
  • Posts: 144
    • View Profile
Re: New Z-Wave driver
« Reply #47 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
« Last Edit: February 01, 2009, 12:26:24 am by johanr »

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #48 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
rock your home - http://www.agocontrol.com home automation

johanr

  • Veteran
  • ***
  • Posts: 144
    • View Profile
Re: New Z-Wave driver
« Reply #49 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


hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #50 on: February 01, 2009, 06:01:41 pm »
aeh no. I meant "fresh installation" not "fresh media".

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

johanr

  • Veteran
  • ***
  • Posts: 144
    • View Profile
Re: New Z-Wave driver
« Reply #51 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

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #52 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
rock your home - http://www.agocontrol.com home automation

johanr

  • Veteran
  • ***
  • Posts: 144
    • View Profile
Re: New Z-Wave driver
« Reply #53 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

yannko

  • Regular Poster
  • **
  • Posts: 22
    • View Profile
Re: New Z-Wave driver
« Reply #54 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  ;)!

eNoodle

  • Veteran
  • ***
  • Posts: 93
    • View Profile
Re: New Z-Wave driver
« Reply #55 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

yannko

  • Regular Poster
  • **
  • Posts: 22
    • View Profile
Re: New Z-Wave driver
« Reply #56 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!

eNoodle

  • Veteran
  • ***
  • Posts: 93
    • View Profile
Re: New Z-Wave driver
« Reply #57 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

yannko

  • Regular Poster
  • **
  • Posts: 22
    • View Profile
Re: New Z-Wave driver
« Reply #58 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!

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #59 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
« Last Edit: February 18, 2009, 07:22:24 pm by hari »
rock your home - http://www.agocontrol.com home automation