Problems with CENTRAL_SCENE and HS-WD100+ Dimmer Switch

Setup, Configuration and Use Runtime
1

This device was working just fine until recently, now I’m not getting any CENTRAL_SCENE notifications from the device. Is there an issue with the the latest snapshots? I noticed this after turning off simple mode for channel binding and specified my own item.

When I trigger a scene command from the switch nothing shows up in the DEBUG logs. When the wall switch is turned off/on it’s supposed to also send out a CENTRAL_SCENE update. It’s not doing that either, but I do get the following:

2016-10-06 20:26:00.674 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 19 00 49 84 0D 13 04 11 01 5E 86 72 5A 85 59 73 26 27 70 2C 2B 5B 7A EF 5B 9D 
2016-10-06 20:26:00.690 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-10-06 20:26:00.694 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 19 00 49 84 0D 13 04 11 01 5E 86 72 5A 85 59 73 26 27 70 2C 2B 5B 7A EF 5B 9D 
2016-10-06 20:26:00.696 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 19 00 49 84 0D 13 04 11 01 5E 86 72 5A 85 59 73 26 27 70 2C 2B 5B 7A EF 5B 9D 
2016-10-06 20:26:00.700 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 0D 13 04 11 01 5E 86 72 5A 85 59 73 26 27 70 2C 2B 5B 7A EF 5B 
2016-10-06 20:26:00.702 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 13: Application update request. Node information received.
2016-10-06 20:26:00.704 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Starting initialisation from DONE
2016-10-06 20:26:00.706 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@133597e already registered
2016-10-06 20:26:00.708 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=10, callback=232, payload=0A 02 84 08 
2016-10-06 20:26:00.712 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 0D 13 04 11 01 5E 86 72 5A 85 59 73 26 27 70 2C 2B 5B 7A EF 5B 
2016-10-06 20:26:00.713 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationUpdate, callback id=232, expected=SendData, cancelled=false      MISMATCH
2

If the device isn’t sending notifications, then I don’t think that’s likely to be an issue with the binding. If nothing gets received, then it must be a configuration issue in the device I think - maybe the association got removed or something…

3

@chris This would be the associate group, right? I checked and it is empty.

I’ve tried to set it, but it doesn’t seem to stick. Using HABmin, I see this in the logs

2016-10-07 12:04:42.650 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Incoming command class ASSOCIATION
2016-10-07 12:04:42.652 [DEBUG] [ndclass.ZWaveAssociationCommandClass] - NODE 13: Received ASSOCIATION command V1
2016-10-07 12:04:42.654 [DEBUG] [ndclass.ZWaveAssociationCommandClass] - NODE 13: association group 1 has max associations 5
2016-10-07 12:04:42.656 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAssociationEvent
2016-10-07 12:04:42.659 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got an event from Z-Wave network: ZWaveAssociationEvent
2016-10-07 12:04:42.660 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got a value event from Z-Wave network, endpoint = 0, command class = ASSOCIATION, value = 0
2016-10-07 12:04:42.662 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Update ASSOCIATION group_1
2016-10-07 12:04:42.663 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Update ASSOCIATION group_1: 0 members
2016-10-07 12:04:42.665 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Config updated

If I try PaperUI, I see

2016-10-07 12:08:32.614 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Configuration update received
2016-10-07 12:08:32.679 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Configuration update group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@33a264 to []
2016-10-07 12:08:32.683 [INFO ] [ome.io.rest.core.thing.ThingResource] - Received HTTP PUT request for update config at 'things/zwave:device:2b98d8e9:node13/config' for the unknown thing 'zwave:device:2b98d8e9:node13'.
4

This isn’t anything from HABmin - is there something earlier than this. I guess so as this is the readback - not the command.[quote=“grizzlyjere, post:3, topic:14938”]
If I try PaperUI, I see
[/quote]

I would expect to see the same thing when you use HABmin. It looks like PaperUI is removing the association - or at least in this log, it’s not setting the association.

5

I turned on trace logging, cleared the log then did the association from HABmin. Everything that came back is here: Association Command Log - Pastebin.com

6

Thanks. Looks like a bug somewhere - I’ll try and get a fix tonight (once I work out what’s up, but hopefully it won’t be too hard). It looks like it sets the group, and then deletes it again for some reason…

7

Great! Thanks for looking into this. Happy to run more tests if needed.

8

Hopefully this will fix the issue -:

Once the tests have run I’ll start a build so if you update the binding in about an hour, it should hopefully be fixed…

9

@chris Thanks for the quick fix. It worked to allow the association group to now be set.

However for some reason the CENTRAL_SCENE still isn’t being received. There isn’t anything showing up in even the trace logs which I don’t get.

To see if it was a problem with the switch I ran Open Z-Wave Control panel and it’s showing the CENTRAL_SCENE being received. So I’m not sure what’s going on…

10

Strange - there’s nothing that should filter this, so as far as I know, if the log doesn’t show it being received, then it’s not being received. Maybe it’s at maximum range or something and sometimes it works, and sometimes not?