For newer hardware you need to use the 1.9 snapshot binding…
Hi,
since my update to OH 2 and the 2.0 binding I have the same problem with my Fibaro Switches. I have FGS211 and FGS222 devices and now with all that switches the same problem that the status won’t be reported to the controller when switched by the hardware switch.
I have associated key 1 with the controller as well as settings for the controller updates to the opehHAB controller.
Status updates for key 2 still work perfectly. In OH 1 I set respond_to_basic=true and with that setting the status updates worked well for key 1.
Is there a similar parameter in OH 2 or is there another solution for that problem?
If you need further information (logs etc.) please let me know.
Best regards,
Jens
Yes - the database has a tickbox for this -:
I would suggest checking the logs to see what is happening - otherwise it’s hard to know what the problem actually is…
Where can I set that? I can’t find that setting…
Here’s the log, when I use the wall switch manually. Node 27 is the device in question.
2016-12-24 21:51:52.866 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 27: Transaction not completed: node address inconsistent. lastSent=27, incoming=255
2016-12-24 21:52:00.435 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 1B 03 25 03 FF 33
2016-12-24 21:52:00.440 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-12-24 21:52:00.444 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 1B 03 25 03 FF 33
2016-12-24 21:52:00.447 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 1B 03 25 03 FF 33
2016-12-24 21:52:00.449 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 1B 03 25 03 FF
2016-12-24 21:52:00.451 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 27: Application Command Request (ALIVE:DONE)
2016-12-24 21:52:00.452 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 27: Starting initialisation from DONE
2016-12-24 21:52:00.455 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1d05a04 already registered
2016-12-24 21:52:00.457 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 27: Incoming command class SWITCH_BINARY
2016-12-24 21:52:00.458 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - Received Switch Binary Request for Node ID = 27
2016-12-24 21:52:00.460 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 27: Switch Binary report, value = 255
2016-12-24 21:52:00.461 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2016-12-24 21:52:00.463 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2016-12-24 21:52:00.465 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got a value event from Z-Wave network, endpoint = 0, command class = SWITCH_BINARY, value = 255
2016-12-24 21:52:00.468 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Updating channel state zwave:device:22160db1:node27:switch_binary to ON [OnOffType]
2016-12-24 21:52:00.474 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=27, callback=206, payload=1B 07 60 0D 01 01 25 01 FF
2016-12-24 21:52:00.477 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 1B 03 25 03 FF
2016-12-24 21:52:00.479 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=206, expected=SendData, cancelled=false MISMATCH
2016-12-24 21:52:05.965 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 1B 03 25 03 00 CC
2016-12-24 21:52:05.970 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-12-24 21:52:05.973 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 1B 03 25 03 00 CC
2016-12-24 21:52:05.976 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 1B 03 25 03 00 CC
2016-12-24 21:52:05.978 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 1B 03 25 03 00
2016-12-24 21:52:05.980 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 27: Application Command Request (ALIVE:DONE)
2016-12-24 21:52:05.981 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 27: Starting initialisation from DONE
2016-12-24 21:52:05.983 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1d05a04 already registered
2016-12-24 21:52:05.984 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 27: Incoming command class SWITCH_BINARY
2016-12-24 21:52:05.986 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - Received Switch Binary Request for Node ID = 27
2016-12-24 21:52:05.987 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 27: Switch Binary report, value = 0
2016-12-24 21:52:05.988 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2016-12-24 21:52:05.989 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2016-12-24 21:52:05.991 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got a value event from Z-Wave network, endpoint = 0, command class = SWITCH_BINARY, value = 0
2016-12-24 21:52:05.993 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Updating channel state zwave:device:22160db1:node27:switch_binary to OFF [OnOffType]
2016-12-24 21:52:05.999 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=27, callback=206, payload=1B 07 60 0D 01 01 25 01 FF
2016-12-24 21:52:06.002 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 1B 03 25 03 00
2016-12-24 21:52:06.003 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=206, expected=SendData, cancelled=false MISMATCH
2016-12-24 21:52:09.291 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Command received zwave:device:22160db1:node27:switch_binary1 --> OFF
2016-12-24 21:52:09.293 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 27: Creating new message for application command SWITCH_BINARY_SET
2016-12-24 21:52:09.295 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: Encapsulating message, instance / endpoint 1
2016-12-24 21:52:09.297 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 27: Creating new message for command MULTI_CHANNEL_ENCAP endpoint 1
2016-12-24 21:52:09.308 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2016-12-24 21:52:09.308 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2016-12-24 21:52:09.312 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0E 00 13 1B 07 60 0D 01 01 25 01 00 25 CF 5D
2016-12-24 21:52:09.315 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 27: Sending REQUEST Message = 01 0E 00 13 1B 07 60 0D 01 01 25 01 00 25 CF 5D
2016-12-24 21:52:09.442 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
2016-12-24 21:52:09.449 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-12-24 21:52:09.452 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
2016-12-24 21:52:09.456 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
2016-12-24 21:52:09.457 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 CF 00 00 0D 29
2016-12-24 21:52:09.459 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
2016-12-24 21:52:09.460 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: Sent Data successfully placed on stack.
2016-12-24 21:52:09.464 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-12-24 21:52:09.467 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 CF 00 00 0D 00 00 27
2016-12-24 21:52:09.470 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 CF 00 00 0D 00 00 27
2016-12-24 21:52:09.472 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=CF 00 00 0D
2016-12-24 21:52:09.474 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: SendData Request. CallBack ID = 207, Status = Transmission complete and ACK received(0)
2016-12-24 21:52:09.476 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 27: Starting initialisation from DONE
2016-12-24 21:52:09.478 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1d05a04 already registered
2016-12-24 21:52:09.481 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=27, callback=207, payload=1B 07 60 0D 01 01 25 01 00
2016-12-24 21:52:09.484 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=CF 00 00 0D
2016-12-24 21:52:09.486 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=207, expected=SendData, cancelled=false transaction complete!
2016-12-24 21:52:09.487 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2016-12-24 21:52:09.488 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-12-24 21:52:09.490 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 27: Response processed after 61ms/4272ms.It’s in the database editor. It’s probably already set but I don’t know what devices you actually have so I’m not 100% sure (there are many versions of these devices).
In any case, it doesn’t matter as the log shows that this isn’t the problem - the device isn’t using the BASIC class (hence why it’s always good to look at the logs 
).
What is node 27? The title of this thread is FGS223, but you’ve then mentioned FGS211 and FGS222… Probably the issue here is that the database is probably using EP1 and the device isn’t using the multi-channel for this endpoint so we probably just need to swap the database channels.
I’m using FGS221 and FGS222, both with the same problem. This issue is similar and related to this topic:
But that topic was related to OH1. Now I have the same problem with OH2.
Node 27 in this case is a “FGS222 Double Relay Switch 2x1.5kW”
Please can you check that the log shows the same thing - I really don’t like assuming it’s “the same problem” - as we’ve already seen - the problem isn’t what you thought.
Also, please can you provide the actual devices that you have - there are 4 versions of the FGS221 alone, so we can’t just go on model number as they are likely different.
I have these four devices:
openhab@main()> things | grep FGS
zwave:device:22160db1:node22 (Type=Thing, Status=ONLINE, Label=Z-Wave Node 22: FGS222 Double Relay Switch 2x1.5kW, Bridge=zwave:serial_zstick:22160db1)
zwave:device:22160db1:node27 (Type=Thing, Status=ONLINE, Label=Z-Wave Node 27: FGS222 Double Relay Switch 2x1.5kW, Bridge=zwave:serial_zstick:22160db1)
zwave:device:22160db1:node28 (Type=Thing, Status=ONLINE, Label=Z-Wave Node 28: FGS222 Double Relay Switch 2x1.5kW, Bridge=zwave:serial_zstick:22160db1)
zwave:device:22160db1:node11 (Type=Thing, Status=ONLINE, Label=Z-Wave Node 11: FGS211 Relay Switch 1x3kW, Bridge=zwave:serial_zstick:22160db1)
What further information do you need?
The devices where key 1 will not send an update are the FGS222 nodes.
I’d like to know the version number - it’s displayed in the device properties (Attributes section in HABmin).
Thanks - but what about the FGS221? There’s four different versions of these.
That one has firmware version 2.1 with type id / ID 0400:100a.
Thanks - I’ll try and take a look at this tomorrow if I get a chance.
Cheers
Chris
So, for these devices there should be 3 channels shown - “Switch”, “Switch 1” and “Switch 2”. Switch and Switch 1 should both control the first relay - if you use the one called Switch, it should also receive reports I think due to the way Fibaro is sending the responses.
Let me know if that is the case and we could update the database to make it clearer.
That solved the problem! Changed switch1 to switch did the trick, I thought “switch” would be for both switches at once.
So it would make sense to update the database to make that clearer.
Thank you very much!
Hello @chris,
I too have a problem with the FGS223. I installed it in my livin room, but want to activate the scenes, so I can trigger alternate scenes from my mail light pushbutton.
But I think the options from the scene activation are wrong:
You are able to activate the scene for every one option, but not the combinations:
Like I want to set it to 7, (1, 2 and 3 combined).
Thanks for your input!
Best regards,
Wouter
I’ve updated these configurations to be free entry.
So what does it do when you set it to 7? Does it not accept that value?
You don’t need to have that “7” in “Available Settings”.
Edit: Upps, too late 
Wow, thanks for the fast reaction!!
This also applies to the Single Switch, I’ve submitted a database change.
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/423