ZWave API

[chrisbirkinshaw]

Which switch modules with LEDs are we talking about here? Having some feedback in my system would be great. At the moment if I press an X10 switch downstairs before I go out to switch my lights off using a macro I have to look around the house to see that they have actually been switched off! Might there be a way to have a button trigger a LMCE event and then LMCE set the button colour once the macro has been completed?

[hari]

Hi Andrew,

Any progress on the floorplan update issue when using non-load remote switches paired with dimmer modules?

I was pretty busy this week, but half of the code is ready, the other half should follow this weekend.

best regards,
Hari

[totallymaxed]

Which switch modules with LEDs are we talking about here? Having some feedback in my system would be great. At the moment if I press an X10 switch downstairs before I go out to switch my lights off using a macro I have to look around the house to see that they have actually been switched off! Might there be a way to have a button trigger a LMCE event and then LMCE set the button colour once the macro has been completed?

Hmmm... well the basic problem with X10 is that you cannot be sure command was acted on... as there is no feedback from the controlled device. Before Hari's new driver this was essentially true of the 'old' ZWave driver too... the only difference was that ZWave is inherently more reliable in its communication protocol so meesages generally get through.

With Haris's new driver we have full bi-directional control :-)

The modules we are referring too earlier in this thread are ACT wall switches that have a single LED on each 'paddle' of the switch used to indicate the various 'states' that the paddle is in or in some cases the associated dimmer module that the 'paddle' is controlling. We are testing the scenario where a dimmer modules has been set to a new 'state' by LinuxMCE and therefore the assciated wall switch 'paddle' should have that new 'state' communicated to it and this 'state' should be reflected by the LED.

All the best

Andrew

[totallymaxed]

Hi Andrew,

Any progress on the floorplan update issue when using non-load remote switches paired with dimmer modules?

I was pretty busy this week, but half of the code is ready, the other half should follow this weekend.

best regards,
Hari

Great Hari... guessed you were busy ;-)

Andrew

[hari]

hi andrew,

the code for the right paddle is checked in, but not yet tested. Left one will follow.

best regards,
Hari

[totallymaxed]

hi andrew,

the code for the right paddle is checked in, but not yet tested. Left one will follow.

best regards,
Hari

Hey great Hari... I will test that first thing on Monday as I dont have the ACT hardware to test with here at home this weekend.

I will get that Zwave kit off to you early next week... sorry just did not get to it last week.

Andrew

[hari]

just added code for the left paddle. The associations are fetched from the remote switch at device startup:

Code:

36 08/31/08 11:49:25.095 Nodes:  <0xb7986b90>
36 08/31/08 11:49:25.095 6 <0xb7986b90>
36 08/31/08 11:49:25.095 32 <0xb7986b90>
36 08/31/08 11:49:25.095 Built nodelist: 6,32 <0xb7986b90>

when we receive a node information frame (left paddle pressed), we request reports from the associated devices in group 1:

Code:

36 08/31/08 11:49:54.945 FUNC_ID_ZW_APPLICATION_UPDATE:UPDATE_STATE_NODE_INFO_RECEIVED received from node 3 -  <0xb7986b90>
36 08/31/08 11:49:54.945 This is a remote switch, we will traverse the association list and request reports <0xb7986b90>
36 08/31/08 11:49:54.945 Adding job: 0x80dc838 <0xb7986b90>
36 08/31/08 11:49:54.945 Setting callback type: 19 <0xb7986b90>
36 08/31/08 11:49:54.945 Adding job: 0x80dca58 <0xb7986b90>
36 08/31/08 11:49:54.945 Setting callback type: 19 <0xb7986b90>

then we receive the reports and send the events to update the state within lmce and the floorplan:

Code:

36 08/31/08 11:49:55.582 Got basic report from node 6, value: 0 <0xb7986b90>
36 08/31/08 11:49:55.582 Sending EVENT_State_Changed_CONST event from node 6, level 0 <0xb7986b90>
36 08/31/08 11:49:55.886 Got basic report from node 32, value: 0 <0xb7986b90>
36 08/31/08 11:49:55.886 Sending EVENT_State_Changed_CONST event from node 32, level 0 <0xb7986b90>

best regards,
Hari

[totallymaxed]

just added code for the left paddle. The associations are fetched from the remote switch at device startup:

Code:

36 08/31/08 11:49:25.095 Nodes:  <0xb7986b90>
36 08/31/08 11:49:25.095 6 <0xb7986b90>
36 08/31/08 11:49:25.095 32 <0xb7986b90>
36 08/31/08 11:49:25.095 Built nodelist: 6,32 <0xb7986b90>

when we receive a node information frame (left paddle pressed), we request reports from the associated devices in group 1:

Code:

36 08/31/08 11:49:54.945 FUNC_ID_ZW_APPLICATION_UPDATE:UPDATE_STATE_NODE_INFO_RECEIVED received from node 3 -  <0xb7986b90>
36 08/31/08 11:49:54.945 This is a remote switch, we will traverse the association list and request reports <0xb7986b90>
36 08/31/08 11:49:54.945 Adding job: 0x80dc838 <0xb7986b90>
36 08/31/08 11:49:54.945 Setting callback type: 19 <0xb7986b90>
36 08/31/08 11:49:54.945 Adding job: 0x80dca58 <0xb7986b90>
36 08/31/08 11:49:54.945 Setting callback type: 19 <0xb7986b90>

then we receive the reports and send the events to update the state within lmce and the floorplan:

Code:

36 08/31/08 11:49:55.582 Got basic report from node 6, value: 0 <0xb7986b90>
36 08/31/08 11:49:55.582 Sending EVENT_State_Changed_CONST event from node 6, level 0 <0xb7986b90>
36 08/31/08 11:49:55.886 Got basic report from node 32, value: 0 <0xb7986b90>
36 08/31/08 11:49:55.886 Sending EVENT_State_Changed_CONST event from node 32, level 0 <0xb7986b90>

best regards,
Hari

Hari thats great we'll test that first thing tomorrow!

Does this mean that the reverse situation will get reported correctly now too? ie we change the state of the associated dimmer using the floorplan... does that change get passed back to the appropriate paddle on the wall switch?

All the best

Andrew

[hari]

Does this mean that the reverse situation will get reported correctly now too? ie we change the state of the associated dimmer using the floorplan... does that change get passed back to the appropriate paddle on the wall switch?

No. The switch itself polls the devices every two minutes and changes the led accordingly.

best regards,
Hari

ps: btw, the ACT wall dimmer with double paddle is so loud (humming sound) that even my girlfriend noticed it in the sleeping room. I'm really looking forward to the merten units..

[totallymaxed]

Does this mean that the reverse situation will get reported correctly now too? ie we change the state of the associated dimmer using the floorplan... does that change get passed back to the appropriate paddle on the wall switch?

No. The switch itself polls the devices every two minutes and changes the led accordingly.

best regards,
Hari

ps: btw, the ACT wall dimmer with double paddle is so loud (humming sound) that even my girlfriend noticed it in the sleeping room. I'm really looking forward to the merten units..

Of course we discussed the fact that the Switch polls the associated devices every two mins by default. I forgot to check the docs on what values that polling period can be set to.

What ACT 2-paddle dimmer switch are you getting a hum from? I'll check that against one of our units to see if its a common fault!

I have sent another email to Seluxit about there multi-sensor... nothing back from them yet though.

Thanks

Andrew

[hari]

What ACT 2-paddle dimmer switch are you getting a hum from? I'll check that against one of our units to see if its a common fault!

ZDM230. The ZDP plugs also make noise if you get close..

I have sent another email to Seluxit about there multi-sensor... nothing back from them yet though.

Daniel gave me a short notice, he was on holidays. He said he will send me one in two weeks.

best regards,
Hari

[totallymaxed]

What ACT 2-paddle dimmer switch are you getting a hum from? I'll check that against one of our units to see if its a common fault!

ZDM230. The ZDP plugs also make noise if you get close..

I have sent another email to Seluxit about there multi-sensor... nothing back from them yet though.

Daniel gave me a short notice, he was on holidays. He said he will send me one in two weeks.

best regards,
Hari

I'll check our ZDM230's for 'hum'... I have noticed some very low level hum from the ZDP plugin dimmers.

Good news re multi-sensor from Daniel :-)

Andrew

[Domodude]

ps: btw, the ACT wall dimmer with double paddle is so loud (humming sound) that even my girlfriend noticed it in the sleeping room. I'm really looking forward to the merten units..

These are nearly noiseless. With your ear against a superdimmer unit, you can hear a slight hum. Same with the relais switch units (not surprising since it contains a relay).

I don't know about ACT units, but merten units have a separate transmitter and receiver in their own software. I hope this will be the case in the new zwave api, too!

[totallymaxed]

ps: btw, the ACT wall dimmer with double paddle is so loud (humming sound) that even my girlfriend noticed it in the sleeping room. I'm really looking forward to the merten units..

These are nearly noiseless. With your ear against a superdimmer unit, you can hear a slight hum. Same with the relais switch units (not surprising since it contains a relay).

I don't know about ACT units, but merten units have a separate transmitter and receiver in their own software. I hope this will be the case in the new zwave api, too!

Hari's new code is fully bi-directional by the way and is a real 'quantum leap' in capability for LinuxMCE - for first time we have a really fully capable ZWave driver thanks to Hari. Give it a try... you'll love it!

Andrew

[hari]

we still miss thermostat and multisensor support. Multisensor will come soon, but I still search somebody with a wired Z-Wave thermostat.

best regards,
Hari

btw: domodude: what do you mean with seperate receiver and transmitter?