Your screenshot tells something different.
[quote=“sihui, post:106, topic:13987, full:true”]
[quote=“Matt77, post:105, topic:13987”]
yes, the actual once to be used are switch_binary1 and switch_binary2.
the screenshot was showing that switch_binary is getting changed to ON but not switch_binary1 as also shown in the log. till now all looks like that the fgs-223 is not reporting back the status of switch_binary1 and 2 if its getting triggered by S1/S2 and the status needs to get polled by OH2.
screenshot below all OFF
below after using physical switch on S2 (light on Q2 turned on but Switch_binary2 got no update)
after manual refresh in HABmin
Sorry, can’t follow what your are trying to do 
Remove the item connected to channel sensor_binary and see what happens.
Last idea: check the correct wiring.
Edit: I know it does not help, but: I used the device with the snapshot binding and now with the development binding and never had any issues …
Very last idea: reset the device
the only thing i’m trying is simply using the physical switch on S1 to turn ON/OFF the light on Q1, which is working.
BUT the status of Switch 1 (switch_binary1) in HABmin never gets automatically updated. only if the status gets polled from the FGS-223.
if i use the switch 1 in HABmin everything is working.
Did you check your events.log? Maybe it’s just a UI glitch.
This is what I get when switching the physical switches:
2017-12-01 23:04:33.024 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_2 changed from ON to OFF
2017-12-01 23:04:34.652 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_2 changed from OFF to ON
2017-12-01 23:04:36.335 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_1 changed from ON to OFF
2017-12-01 23:04:39.654 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_1 changed from OFF to ON
no nothing like that in the logs for me. only this:
2017-12-02 02:22:33.272 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Application Command Request (ALIVE:DONE)
2017-12-02 02:22:33.275 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-02 02:22:33.277 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Incoming command class COMMAND_CLASS_BASIC, endpoint 0
2017-12-02 02:22:33.279 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_BASIC
2017-12-02 02:22:33.281 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Received COMMAND_CLASS_BASIC V1 BASIC_SET
2017-12-02 02:22:33.283 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 37: Basic report, value = 255
2017-12-02 02:22:33.285 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2017-12-02 02:22:33.287 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-12-02 02:22:33.289 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_BASIC, value = 255
2017-12-02 02:22:33.291 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Updating channel state zwave:device:15f1ee0619b:node37:switch_binary to ON [OnOffType]
2017-12-02 02:22:33.296 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Commands processed 1.
2017-12-02 02:22:33.297 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@f4b5cc.
2017-12-02 02:22:33.299 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2017-12-02 02:22:33.301 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
showing that switch_binary gets changed to ON
Unfortunately I am not an expert on debugging logs, cannot find something obvious, sorry.
Edit: btw, I meant the events.log, not the openhab/zwave.log …
I had the same trouble that a physical switch was not reported back. I removed node and performed a factory reset on the node. After doin this the problem was gone.
Yepp, with another Fibaro device type I made that same experience a while ago …
My experience is that the correct functionality depends
a) on the OH Binding Version IN THE MOMENET OF INCLUSION of the device and
b) on THE WAY HOW THE DEVICE WAS INCLUDED (use OH network wide inclusion from the UI not the button on the Z-Stick)
ok, for the inclusion i user HABmin and the current binding i’m using is the latest dev. version.
my i ask with which one you got it working the way it should work?
That is indeed a good question as I switched around the different versions of the dev binding and added switches time after time…
I think it worked with the dev binding versions 201709182108 and 201710241752 as I used them most of the time in the last months.So far I did not test it with the newest dev version.
Firmware version of my FGS223 is 3.2
same FW version here. i tried now even the qubino flus 2 relays and have exact the same behavior as with the Fibaro FG223. i tried it this time with OH2 2.2 stable and the latest Z-Wave Dev binding. exactly the same behavior. Using the hardware (physical) switch is not changing the status of the Item, neither in HABmin or any of the other UI.
@chris any ideas on this?
It would be interesting to see if the older versions (like 201709182108 ) would work for you. If you want I can email you the .jar file of the old version.
got it finally working, fgs-223 and qubino flush 2 relay.
i removed the dev-Zwave binding, removed al xml files and things as well as reset the Z-Wave usb.
then installed the z-Wave binding from the OH2 2.2 stable and started to include the devices. all working now.
but would be nice to have the security from the dev-binding as well.
Hi, I struggle with the reset, too. I never receive the red LED. Do I need to detach some of the wires or something? I see the yellow LED and click again, but nothing happens afterwards?! Thanks for any input.
I don’t think so, bit I had only the power wires attached during the reset process.
The magic for me was: do the reset directly after applying power to the device (within a few seconds).
Good luck.
Hi, after a lot of frustration I was finally able to reset the device. Key was to ensure that S1, S2, O1 and O2 were without voltage before starting the reset process. I used S2 only virtually and thus did not check, if there still was voltage on O2. Thanks a lot for your support.
1 Like