Zwave 2.2 binding - snapshot vs release (fibaro fgs223 status from channel 2)

hello,
After upgrading to openhab 2.2 I do not get status updates (when pressing physical Button nothing happens in OH2) from Channel 2.
I had this problem with oh2.1 and fixed it by using zwave snapshot binding + update the lifeline in the device associations…
Now I tried to work with the 2.2 binding and updated the lifeline + on/off of S2 to openhab controller and still no update from channel 2.

When I press the physical button I see those logs:

18-Dec-2017 23:36:10.218 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 08 07 03 20 01 FF 20
18-Dec-2017 23:36:10.221 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
18-Dec-2017 23:36:10.223 [DEBUG] [nhab.binding.zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 08 07 03 20 01 FF 20
18-Dec-2017 23:36:10.225 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 08 07 03 20 01 FF 20
18-Dec-2017 23:36:10.228 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=08 07 03 20 01 FF
18-Dec-2017 23:36:10.229 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 7: Application Command Request (ALIVE:DONE)
18-Dec-2017 23:36:10.231 [DEBUG] [protocol.initialization.ZWaveNodeInitStageAdvancer] - NODE 7: Starting initialisation from DONE
18-Dec-2017 23:36:10.233 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1c0b5e4 already registered
18-Dec-2017 23:36:10.233 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 07 03 20 01 FF 28
18-Dec-2017 23:36:10.235 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 7: Incoming command class BASIC
18-Dec-2017 23:36:10.236 [DEBUG] [ernal.protocol.commandclass.ZWaveBasicCommandClass] - NODE 7: Received Basic Request
18-Dec-2017 23:36:10.238 [DEBUG] [ernal.protocol.commandclass.ZWaveBasicCommandClass] - NODE 7: Basic Set sent to the controller will be processed as Basic Report
18-Dec-2017 23:36:10.240 [DEBUG] [ernal.protocol.commandclass.ZWaveBasicCommandClass] - NODE 7: Basic report, value = 0xFF
18-Dec-2017 23:36:10.241 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
18-Dec-2017 23:36:10.243 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
18-Dec-2017 23:36:10.245 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
18-Dec-2017 23:36:10.247 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Updating channel state zwave:device:Zwave:node7:switch_binary to ON [OnOffType]
18-Dec-2017 23:36:10.250 [DEBUG] [ernal.protocol.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=7, callback=181, payload=07 07 60 0D 01 02 25 01 00
18-Dec-2017 23:36:10.253 [DEBUG] [ernal.protocol.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=08 07 03 20 01 FF
18-Dec-2017 23:36:10.254 [DEBUG] [ernal.protocol.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=181, expected=SendData, cancelled=false MISMATCH
18-Dec-2017 23:36:10.256 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
18-Dec-2017 23:36:10.258 [DEBUG] [nhab.binding.zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 07 03 20 01 FF 28
18-Dec-2017 23:36:10.260 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 07 03 20 01 FF 28
18-Dec-2017 23:36:10.263 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 07 03 20 01 FF
18-Dec-2017 23:36:10.265 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 7: Application Command Request (ALIVE:DONE)
18-Dec-2017 23:36:10.266 [DEBUG] [protocol.initialization.ZWaveNodeInitStageAdvancer] - NODE 7: Starting initialisation from DONE
18-Dec-2017 23:36:10.268 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1c0b5e4 already registered
18-Dec-2017 23:36:10.270 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 7: Incoming command class BASIC
18-Dec-2017 23:36:10.271 [DEBUG] [ernal.protocol.commandclass.ZWaveBasicCommandClass] - NODE 7: Received Basic Request
18-Dec-2017 23:36:10.273 [DEBUG] [ernal.protocol.commandclass.ZWaveBasicCommandClass] - NODE 7: Basic Set sent to the controller will be processed as Basic Report
18-Dec-2017 23:36:10.274 [DEBUG] [ernal.protocol.commandclass.ZWaveBasicCommandClass] - NODE 7: Basic report, value = 0xFF
18-Dec-2017 23:36:10.276 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
18-Dec-2017 23:36:10.278 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
18-Dec-2017 23:36:10.279 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
18-Dec-2017 23:36:10.282 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Updating channel state zwave:device:Zwave:node7:switch_binary to ON [OnOffType]
18-Dec-2017 23:36:10.285 [DEBUG] [ernal.protocol.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=7, callback=181, payload=07 07 60 0D 01 02 25 01 00
18-Dec-2017 23:36:10.287 [DEBUG] [ernal.protocol.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 07 03 20 01 FF
18-Dec-2017 23:36:10.289 [DEBUG] [ernal.protocol.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=181, expected=SendData, cancelled=false MISMATCH

But still the openhab item not getting an update…

After restoring the zwave binding of snapshot 2.2 it came back to work…
Am I missing something? as far as I know the release should contain the snapshot…

The day the stable release gets published the 2.2 snapshot binding becomes the 2.2 stable binding and the 2.2 snapshot binding becomes the 2.3 snapshot binding.

Make sure you are using the
switch_binary1 and switch_binary2 channels and not the switch_binary

I’m using the same item, just replaces the jars and the snapshot is working, the release not…