I have openhab 1.8.3 running under Ubuntu 14.04 using a Aeon Labs Aeotec Z-Wave Z-Stick, Gen5. For the most part everything works fine. One thing I can’t figure out is how to get the current status of a Dragon Tech WD-100 Wall Dimmer Switch.
I am using org.openhab.binding.zwave-1.9.0-SNAPSHOT.jar. Since I can see entries in zwave.log when I turn the switch on or off, I would have expected it was reporting the current status. I cannot however see a change in the events.log file and it will not trigger a rule. I have the z-stick as a member under Association Groups.
Here is the entry in the items file:
Dimmer GuestBedroomLight “Guest Bedroom Dimmer [%d %%]” (Room_Light) { zwave=“24:command=SWITCH_MULTILEVEL” }
I have a different model z-wave dimmer that does work. Is this switch capable of reporting status? If it is not capable, how can I tell which switches can report their status?
Here is the data from zwave.log when I turn the switch on:
2016-10-14 10:56:40.345 [DEBUG] [eController$ZWaveReceiveThread:1530]- Receive Message = 01 14 00 49 84 18 0E 04 11 01 5E 86 72 5A 85 59 73 26 27 70 7A 70
2016-10-14 10:56:40.346 [DEBUG] [eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=1
2016-10-14 10:56:40.346 [DEBUG] [b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
2016-10-14 10:56:40.346 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 14 00 49 84 18 0E 04 11 01 5E 86 72 5A 85 59 73 26 27 70 7A 70
2016-10-14 10:56:40.346 [DEBUG] [b.z.i.protocol.ZWaveController:1195]- Process Message = 01 14 00 49 84 18 0E 04 11 01 5E 86 72 5A 85 59 73 26 27 70 7A 70
2016-10-14 10:56:40.347 [DEBUG] [b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationUpdate (0x49), type = Request (0x00), payload = 84 18 0E 04 11 01 5E 86 72 5A 85 59 73 26 27 70 7A
2016-10-14 10:56:40.347 [DEBUG] [.ApplicationUpdateMessageClass:49 ]- NODE 24: Application update request. Node information received.
2016-10-14 10:56:40.347 [DEBUG] [b.z.i.protocol.ZWaveController:648 ]- Notifying event listeners: ZWaveNodeInfoEvent
2016-10-14 10:56:40.347 [DEBUG] [.z.internal.ZWaveActiveBinding:449 ]- ZwaveIncomingEvent
2016-10-14 10:56:40.347 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1104]- NODE 24: 3 NIF event during initialisation stage PING
2016-10-14 10:56:40.347 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1104]- NODE 24: 22 NIF event during initialisation stage PING
2016-10-14 10:56:40.348 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1104]- NODE 24: 28 NIF event during initialisation stage PING
2016-10-14 10:56:40.348 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1104]- NODE 24: 29 NIF event during initialisation stage PING
2016-10-14 10:56:40.348 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1104]- NODE 24: 23 NIF event during initialisation stage PING
2016-10-14 10:56:40.348 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1104]- NODE 24: 13 NIF event during initialisation stage PING
2016-10-14 10:56:40.348 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1104]- NODE 24: 16 NIF event during initialisation stage PING
2016-10-14 10:56:40.348 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1104]- NODE 24: 30 NIF event during initialisation stage PING
2016-10-14 10:56:40.348 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1104]- NODE 24: 12 NIF event during initialisation stage PING
2016-10-14 10:56:40.348 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1104]- NODE 24: 14 NIF event during initialisation stage PING
2016-10-14 10:56:40.348 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1104]- NODE 24: 11 NIF event during initialisation stage PING
2016-10-14 10:56:40.349 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1104]- NODE 24: 15 NIF event during initialisation stage PING
2016-10-14 10:56:40.349 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:66 ]- Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 09 01 00
2016-10-14 10:56:40.349 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:67 ]- Recv message Message: class = ApplicationUpdate (0x49), type = Request (0x00), payload = 84 18 0E 04 11 01 5E 86 72 5A 85 59 73 26 27 70 7A
2016-10-14 10:56:40.349 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:68 ]- Checking transaction complete: class=ApplicationUpdate, expected=SendData, cancelled=false