New Fibaro Switch FGS-223 is driving me nuts

sihui · February 27, 2017, 5:57am

I bought one of those devices two weeks ago and I can confirm that it works fine with openHAB2 (RPi, Zwave.me USB stick)

You should not hear the relay clicking while pressing the B-Button three times! Either the device is faulty or maybe you did not reset the device correctly (I also had to reset the FGS223 before inclusion worked).

Reset: Apply power, hold the B-button until the yellow light turns on, while the yellow light is on (that is only the case for 2 or 3 seconds), release the button and click it again once. After successful reset the red light comes on for some seconds.
Then try the inclusion again …
BTW, it is recommended to use HABmin for dealing with zwave devices, it is specifically designed for that.

vossivossi · February 27, 2017, 7:32am

I also spent several days to sort out the issues with these devices and OH2. It now works.
Make sure that you use the inclusion function from within OH2 (worked for me with both Paper UI and Habmin) when your Z-Wave stick is connected. I had trouble when I included the devices first decentrally with my Aeon Z-Stick5 and then started OH2, as in these cases the different endpoints were never usable.
Additionally I had to add the association group for lifeline to the OH controller (I did this with Habmin). Then it worked for me.

sihui · February 27, 2017, 7:48am

You can avoid that by setting “Controller is Master” in your “Z-Wave network settings” for your USB Stick. You need to switch to “Tools” “Show advanced settings” though.

andreasBCN · February 27, 2017, 10:05am

Thanks for the prompt support. Glad to hear that it should work with OpenHAB2, so it should be either an issue with the UZB stick on the Mac or a problem with this particular device.

I have reset the FGS 223 several times. It starts with a pale blue (white?) LED, then turns green, then purple and then yellow. When I then release the button, it does not do anything, so it does not turn red for a few seconds. Is that a malfunction of the device? Also: should it indicate that it’s in inclusion mode by any LED signal?

Best regards,

Andreas

vossivossi · February 27, 2017, 11:20am

I just activated the switch to “Show advanced settings” but the “Controller is Master” setting was already active. Nonetheless I had to set the lifeline association for all FGS-223 in Habmin to make it run (I spent the complete Sunday yesterday with these devices… ) I am running OH2.0.0 Release Build with 2.0.0 Z-Wave binding on Windows with Aeon Z-Stick 5.

sihui · February 27, 2017, 12:13pm

You forgot one step: as long as the led is yellow, release the button and click it again. Then the led should turn red.

sihui · February 27, 2017, 12:15pm

Hmmm, actually the Lifeline association should have been set automatically because of “Mastercontroller true”.
But as long as it is set, it doesn’t matter … it’s just for convenience.

andreasBCN · March 3, 2017, 6:35pm

Hi sihui,

thanks for that clarification. I just returned home and tried it out and have now been able to reset the FGS-232 with a red LED signal in response. It however did not change anything with regards to the inclusion. The log before and after the reset is identical. Is the UZB stick not working well or is the FGS-232 broken or do you have any other idea?

Best regards,

Andreas

sihui · March 3, 2017, 9:13pm

I’m using the same one and it is working fine.

I had to repeat the inclusion process two or three times until it worked. Keep going …

andreasBCN · March 7, 2017, 4:58pm

Hi,
I have now changed the UZB stick against a Z-Stick and have been able to include the device. It works well for Switch 1, however Switch 2 keeps me confused. When I switch it on, it does turn on the lights, but if I switch it off, then it ignores it completely. This was already the case before I included the device through Z-WAVE when I switched it with the manual switch, but I had hoped to be able to change the parameters of switch 2 so that it works appropriately. I however don’t find a way to configure it right.

Initially I had it configured as toggle switch and then showed the following behaviour for switching through ZWAVE:

switching on: lights go on
switching off: lights go off for a fraction of a second and then go on again

I then changed it to switch parameter to „toggle stable“ and thereafter the behaviour for switching through ZWAVE is as desired, but the switching with the manual switch still remains broken:

switching on: lights go on
switching off: no effect, lights stay on. (I double-checked that there is power on S2 when the switch is on and no power on S2 when the switch is off)

Any idea, how I can fix this issue?

Thanks,

Andreas

sihui · March 7, 2017, 5:01pm

Make sure you have the correct channels:

S1 = switch_binary1
S2 = switch_binary2

andreasBCN · March 7, 2017, 5:15pm

Where can I look this up?

If I look at HABmin under channels, it shows
"Switch the power on and off" behind every switch. Below in the last section it says
Z-Wave Plus Node TypeON_OFF_POWER_SWITCH
Basic ClassROUTING_SLAVE
StandardklasseBINARY_SWITCH
Specific ClassPOWER_SWITCH_BINARY

Also, I forgot to mention that when I switch S2 on the manual switch and it turns the light on, on BasicUI the linked switch item stays unchanged (off).

Andreas

sihui · March 7, 2017, 5:40pm

I do my setup manually, so it looks like this in the items file:

Switch FibFGS223_1_Sw_1 "Living Room 1" (gRestore) { channel="zwave:device:158b44ebf65:node30:switch_binary1" }
Switch FibFGS223_1_Sw_2 "Living Room 2" (gRestore) { channel="zwave:device:158b44ebf65:node30:switch_binary2" }

If you have configured it through HABmin or PaperUI, you should see the channel under “Configuration” → “Things”
The first switch from the top is switch_binary, don’t use it, the second is switch_binary1, link that to your S1 item switch, the third switch is binary_switch2, link that to your S2 item switch.

BTW, what version of the zwave binding (and openHAB runtime) are you using? You will definitely need one of the newer zwave snapshot 2.1.x bindings, it won’t work with the stable 2.0.0 zwave binding.

Matt77 · December 1, 2017, 12:09pm

i know the last post is already a bit older but i was wandering if this problem also occur in the latest snapshot build #1099
in combination with the latest dev. Z-Wave binding (secure).

i’m asking cause i have exactly the same problem with my FGS-223. the channel for Switch 1 and/or 2 are not getting updated in OH2 if i use the physical switch.

my FGS-223 is on firmware 3.2

i also tried to set the Association Group for Lifeline to the openHAB controller, however the entry seems to get removed later, at least after saving and refreshing the screen its empty again?

sihui · December 1, 2017, 3:18pm

I’m using those switches now for a year, and that problem never occured
Again, make sure you:

Matt77 · December 1, 2017, 7:01pm

i wish i had that luck.

checked everything and the config looks ok. however if i use the toggle switch (physical switch) only the Switch item in HABmin is changing. not the actual switch 1.

one more thing, if i use the physical switch which is connected to S1 the light on Q1 gets turned ON, however in the log only switch_binary gets triggered not switch_binary1

2017-12-01 23:33:18.402 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Application Command Request (ALIVE:DONE)
2017-12-01 23:33:18.405 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-01 23:33:18.407 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Incoming command class COMMAND_CLASS_SWITCH_BINARY, endpoint 0
2017-12-01 23:33:18.410 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_SWITCH_BINARY
2017-12-01 23:33:18.412 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Received COMMAND_CLASS_SWITCH_BINARY V1 SWITCH_BINARY_REPORT
2017-12-01 23:33:18.415 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 37: Switch Binary report, value = 255
2017-12-01 23:33:18.420 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-12-01 23:33:18.423 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SWITCH_BINARY, value = 255
2017-12-01 23:33:18.426 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Updating channel state zwave:device:15f1ee0619b:node37:switch_binary to ON [OnOffType]
2017-12-01 23:33:18.430 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Commands processed 1.
2017-12-01 23:33:18.433 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@a087f4.
2017-12-01 23:33:18.513 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Application Command Request (ALIVE:DONE)
2017-12-01 23:33:18.515 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-01 23:33:18.518 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Incoming command class COMMAND_CLASS_BASIC, endpoint 0
2017-12-01 23:33:18.520 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_BASIC
2017-12-01 23:33:18.522 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Received COMMAND_CLASS_BASIC V1 BASIC_SET
2017-12-01 23:33:18.524 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 37: Basic report, value = 255
2017-12-01 23:33:18.529 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-12-01 23:33:18.532 [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-01 23:33:18.534 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Updating channel state zwave:device:15f1ee0619b:node37:switch_binary to ON [OnOffType]
2017-12-01 23:33:18.537 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Commands processed 1.
2017-12-01 23:33:18.539 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1d5588c.
2017-12-01 23:33:18.551 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Application Command Request (ALIVE:DONE)
2017-12-01 23:33:18.553 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-01 23:33:18.555 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Incoming command class COMMAND_CLASS_BASIC, endpoint 0
2017-12-01 23:33:18.558 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_BASIC
2017-12-01 23:33:18.560 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Received COMMAND_CLASS_BASIC V1 BASIC_SET
2017-12-01 23:33:18.561 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 37: Basic report, value = 255
2017-12-01 23:33:18.565 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-12-01 23:33:18.568 [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-01 23:33:18.570 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Updating channel state zwave:device:15f1ee0619b:node37:switch_binary to ON [OnOffType]
2017-12-01 23:33:18.573 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Commands processed 1.
2017-12-01 23:33:18.575 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1fb824a.
2017-12-01 23:33:18.613 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Application Command Request (ALIVE:DONE)
2017-12-01 23:33:18.615 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-01 23:33:18.616 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Incoming command class COMMAND_CLASS_SWITCH_MULTILEVEL, endpoint 0
2017-12-01 23:33:18.618 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Command class COMMAND_CLASS_SWITCH_MULTILEVEL not found, trying to add it.
2017-12-01 23:33:18.619 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Creating new instance of command class COMMAND_CLASS_SWITCH_MULTILEVEL
2017-12-01 23:33:18.621 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Command class COMMAND_CLASS_SWITCH_MULTILEVEL, endpoint 0 created
2017-12-01 23:33:18.623 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Adding command class COMMAND_CLASS_SWITCH_MULTILEVEL to endpoint 0
2017-12-01 23:33:18.625 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Adding command class COMMAND_CLASS_SWITCH_MULTILEVEL to the list of supported command classes.
2017-12-01 23:33:18.626 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_SWITCH_MULTILEVEL
2017-12-01 23:33:18.628 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Received COMMAND_CLASS_SWITCH_MULTILEVEL V0 SWITCH_MULTILEVEL_SET
2017-12-01 23:33:18.629 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 37: Switch Multi Level set, value = 255
2017-12-01 23:33:18.632 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-12-01 23:33:18.634 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SWITCH_MULTILEVEL, value = 255
2017-12-01 23:33:18.636 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Commands processed 1.
2017-12-01 23:33:18.638 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@eba217.
2017-12-01 23:33:18.647 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Application Command Request (ALIVE:DONE)
2017-12-01 23:33:18.648 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-01 23:33:18.650 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Incoming command class COMMAND_CLASS_SWITCH_MULTILEVEL, endpoint 0
2017-12-01 23:33:18.652 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_SWITCH_MULTILEVEL
2017-12-01 23:33:18.653 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Received COMMAND_CLASS_SWITCH_MULTILEVEL V0 SWITCH_MULTILEVEL_SET
2017-12-01 23:33:18.655 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 37: Switch Multi Level set, value = 255
2017-12-01 23:33:18.658 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-12-01 23:33:18.660 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SWITCH_MULTILEVEL, value = 255
2017-12-01 23:33:18.662 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Commands processed 1.
2017-12-01 23:33:18.663 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@c21cd9.
2017-12-01 23:33:21.116 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Application Command Request (ALIVE:DONE)
2017-12-01 23:33:21.119 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-01 23:33:21.121 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Incoming command class COMMAND_CLASS_METER, endpoint 0
2017-12-01 23:33:21.124 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_METER
2017-12-01 23:33:21.126 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Received COMMAND_CLASS_METER V3 METER_REPORT
2017-12-01 23:33:21.129 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 37: Meter: Type=Electric(1), Scale=W(2), Value=11.3
2017-12-01 23:33:21.134 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveMeterValueEvent
2017-12-01 23:33:21.142 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_METER, value = 11.3
2017-12-01 23:33:21.146 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Updating channel state zwave:device:15f1ee0619b:node37:meter_watts to 11.3 [DecimalType]
2017-12-01 23:33:21.150 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Commands processed 1.
2017-12-01 23:33:21.152 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@11c25b5.

only after a manual refresh in HABmin switch_binary1 gets updated.

2017-12-01 23:40:53.120 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@10b4580.
2017-12-01 23:42:55.585 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Command received zwave:device:15f1ee0619b:node37:switch_binary1 --> REFRESH
2017-12-01 23:42:55.592 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Polling intialised at 1800 seconds - start in 50 milliseconds.
2017-12-01 23:42:55.611 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Command received zwave:device:15f1ee0619b:node37:meter_kwh1 --> REFRESH
2017-12-01 23:42:55.615 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Polling intialised at 1800 seconds - start in 50 milliseconds.
2017-12-01 23:42:55.625 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Command received zwave:device:15f1ee0619b:node37:meter_watts1 --> REFRESH
2017-12-01 23:42:55.629 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Polling intialised at 1800 seconds - start in 50 milliseconds.
2017-12-01 23:42:55.679 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Polling...
2017-12-01 23:42:55.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Polling zwave:device:15f1ee0619b:node37:switch_binary1
2017-12-01 23:42:55.682 [DEBUG] [converter.ZWaveBinarySwitchConverter] - NODE 37: Generating poll message for COMMAND_CLASS_SWITCH_BINARY, endpoint 1
2017-12-01 23:42:55.683 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 37: Creating new message for application command SWITCH_BINARY_GET
2017-12-01 23:42:55.686 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Encapsulating message, endpoint 1
2017-12-01 23:42:55.688 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Encapsulating message, instance / endpoint 1
2017-12-01 23:42:55.690 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 37: Creating new message for command MULTI_CHANNEL_ENCAP endpoint 1
2017-12-01 23:42:55.691 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_MULTI_CHANNEL
2017-12-01 23:42:55.693 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Command Class COMMAND_CLASS_MULTI_CHANNEL is NOT required to be secured
2017-12-01 23:42:55.694 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Polling zwave:device:15f1ee0619b:node37:switch_binary1
2017-12-01 23:42:55.696 [DEBUG] [ternal.converter.ZWaveBasicConverter] - NODE 37: Generating poll message for COMMAND_CLASS_BASIC endpoint 1
2017-12-01 23:42:55.698 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Encapsulating message, endpoint 1
2017-12-01 23:42:55.700 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Encapsulating message, instance / endpoint 1
2017-12-01 23:42:55.702 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 37: Creating new message for command MULTI_CHANNEL_ENCAP endpoint 1
2017-12-01 23:42:55.703 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_MULTI_CHANNEL
2017-12-01 23:42:55.705 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Command Class COMMAND_CLASS_MULTI_CHANNEL is NOT required to be secured
2017-12-01 23:42:55.706 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Polling zwave:device:15f1ee0619b:node37:meter_kwh1
2017-12-01 23:42:55.708 [DEBUG] [ternal.converter.ZWaveMeterConverter] - NODE 37: Generating poll message for COMMAND_CLASS_METER, endpoint 1
2017-12-01 23:42:55.709 [DEBUG] [ternal.converter.ZWaveMeterConverter] - NODE 37: Generating poll message for COMMAND_CLASS_METER, endpoint 1
2017-12-01 23:42:55.711 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 37: Creating new message for application command METER_GET
2017-12-01 23:42:55.714 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Encapsulating message, endpoint 1
2017-12-01 23:42:55.716 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Encapsulating message, instance / endpoint 1
2017-12-01 23:42:55.717 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 37: Creating new message for command MULTI_CHANNEL_ENCAP endpoint 1
2017-12-01 23:42:55.719 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_MULTI_CHANNEL
2017-12-01 23:42:55.721 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Command Class COMMAND_CLASS_MULTI_CHANNEL is NOT required to be secured
2017-12-01 23:42:55.722 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Polling zwave:device:15f1ee0619b:node37:meter_watts1
2017-12-01 23:42:55.723 [DEBUG] [ternal.converter.ZWaveMeterConverter] - NODE 37: Generating poll message for COMMAND_CLASS_METER, endpoint 1
2017-12-01 23:42:55.725 [DEBUG] [ternal.converter.ZWaveMeterConverter] - NODE 37: Generating poll message for COMMAND_CLASS_METER, endpoint 1
2017-12-01 23:42:55.726 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 37: Creating new message for application command METER_GET
2017-12-01 23:42:55.729 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Encapsulating message, endpoint 1
2017-12-01 23:42:55.731 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Encapsulating message, instance / endpoint 1
2017-12-01 23:42:55.732 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 37: Creating new message for command MULTI_CHANNEL_ENCAP endpoint 1
2017-12-01 23:42:55.734 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_MULTI_CHANNEL
2017-12-01 23:42:55.735 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Command Class COMMAND_CLASS_MULTI_CHANNEL is NOT required to be secured
2017-12-01 23:42:55.737 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Adding to device queue
2017-12-01 23:42:55.738 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Added to queue - size 0
2017-12-01 23:42:55.763 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: listening == true, frequentlyListening == false, awake == false
2017-12-01 23:42:55.772 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 37: Sending REQUEST Message = 01 0D 00 13 25 06 60 0D 01 01 25 02 25 EF 42 
2017-12-01 23:42:55.810 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Adding to device queue
2017-12-01 23:42:55.819 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 37: sentData successfully placed on stack.
2017-12-01 23:42:55.821 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Added to queue - size 0
2017-12-01 23:42:55.831 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: TID 1127: Transaction not completed
2017-12-01 23:42:55.842 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Adding to device queue
2017-12-01 23:42:55.844 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Added to queue - size 0
2017-12-01 23:42:55.845 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 37: SendData Request. CallBack ID = 239, Status = Transmission complete and ACK received(0)
2017-12-01 23:42:55.846 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-01 23:42:55.851 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Adding to device queue
2017-12-01 23:42:55.853 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Added to queue - size 0
2017-12-01 23:42:55.855 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Response processed after 79ms
2017-12-01 23:42:55.856 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: TID 1127: Transaction completed
2017-12-01 23:42:55.858 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: notifyTransactionResponse TID:1127 DONE
2017-12-01 23:42:55.861 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2017-12-01 23:42:55.866 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Application Command Request (ALIVE:DONE)
2017-12-01 23:42:55.867 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-01 23:42:55.870 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2017-12-01 23:42:55.871 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Incoming command class COMMAND_CLASS_SWITCH_BINARY, endpoint 1
2017-12-01 23:42:55.872 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_SWITCH_BINARY
2017-12-01 23:42:55.873 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Received COMMAND_CLASS_SWITCH_BINARY V1 SWITCH_BINARY_REPORT
2017-12-01 23:42:55.875 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 37: Switch Binary report, value = 255
2017-12-01 23:42:55.877 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-12-01 23:42:55.879 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_SWITCH_BINARY, value = 255
2017-12-01 23:42:55.881 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: listening == true, frequentlyListening == false, awake == false
2017-12-01 23:42:55.881 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Updating channel state zwave:device:15f1ee0619b:node37:switch_binary1 to ON [OnOffType]
2017-12-01 23:42:55.884 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Commands processed 1.
2017-12-01 23:42:55.885 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@cb0832.
2017-12-01 23:42:55.890 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 37: Sending REQUEST Message = 01 0D 00 13 25 06 60 0D 01 01 20 02 25 F0 58 
2017-12-01 23:42:55.913 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking transaction 1128  ApplicationCommandHandler.
2017-12-01 23:42:55.914 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking transaction : state >> WAIT_RESPONSE
2017-12-01 23:42:55.916 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking transaction : node  >> 37
2017-12-01 23:42:55.917 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking transaction : class >> 37 == 32.
2017-12-01 23:42:55.918 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking transaction : commd >> 3 == 3.
2017-12-01 23:42:55.920 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Ignoring transaction since not waiting for data.
2017-12-01 23:42:55.936 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 37: sentData successfully placed on stack.
2017-12-01 23:42:55.944 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: TID 1128: Transaction not completed
2017-12-01 23:42:55.956 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 37: SendData Request. CallBack ID = 240, Status = Transmission complete and ACK received(0)
2017-12-01 23:42:55.957 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-01 23:42:55.966 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Response processed after 73ms
2017-12-01 23:42:55.967 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: TID 1128: Transaction completed
2017-12-01 23:42:55.968 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: notifyTransactionResponse TID:1128 DONE
2017-12-01 23:42:55.971 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2017-12-01 23:42:55.975 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Application Command Request (ALIVE:DONE)
2017-12-01 23:42:55.977 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-01 23:42:55.978 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2017-12-01 23:42:55.979 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Incoming command class COMMAND_CLASS_BASIC, endpoint 1
2017-12-01 23:42:55.980 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_BASIC
2017-12-01 23:42:55.982 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Received COMMAND_CLASS_BASIC V0 BASIC_REPORT
2017-12-01 23:42:55.983 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 37: Basic report, value = 255
2017-12-01 23:42:55.986 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-12-01 23:42:55.987 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_BASIC, value = 255
2017-12-01 23:42:55.989 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Updating channel state zwave:device:15f1ee0619b:node37:switch_binary1 to ON [OnOffType]
2017-12-01 23:42:55.992 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Commands processed 1.
2017-12-01 23:42:55.993 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@374f2.
2017-12-01 23:42:56.016 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: listening == true, frequentlyListening == false, awake == false
2017-12-01 23:42:56.023 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 37: Sending REQUEST Message = 01 0E 00 13 25 07 60 0D 01 01 32 01 10 25 F1 5A 
2017-12-01 23:42:56.058 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 37: sentData successfully placed on stack.
2017-12-01 23:42:56.067 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: TID 1130: Transaction not completed
2017-12-01 23:42:56.086 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 37: SendData Request. CallBack ID = 241, Status = Transmission complete and ACK received(0)
2017-12-01 23:42:56.087 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-01 23:42:56.097 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Response processed after 71ms
2017-12-01 23:42:56.099 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: TID 1130: Transaction completed
2017-12-01 23:42:56.100 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: notifyTransactionResponse TID:1130 DONE
2017-12-01 23:42:56.103 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2017-12-01 23:42:56.108 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Application Command Request (ALIVE:DONE)
2017-12-01 23:42:56.109 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-01 23:42:56.110 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2017-12-01 23:42:56.112 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Incoming command class COMMAND_CLASS_METER, endpoint 1
2017-12-01 23:42:56.113 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_METER
2017-12-01 23:42:56.114 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Received COMMAND_CLASS_METER V3 METER_REPORT
2017-12-01 23:42:56.115 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 37: Meter: Type=Electric(1), Scale=W(2), Value=11.1
2017-12-01 23:42:56.118 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveMeterValueEvent
2017-12-01 23:42:56.120 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_METER, value = 11.1
2017-12-01 23:42:56.122 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Updating channel state zwave:device:15f1ee0619b:node37:meter_watts1 to 11.1 [DecimalType]
2017-12-01 23:42:56.124 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Commands processed 1.
2017-12-01 23:42:56.125 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@6ee52f.
2017-12-01 23:42:56.149 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: listening == true, frequentlyListening == false, awake == false
2017-12-01 23:42:56.155 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 37: Sending REQUEST Message = 01 0E 00 13 25 07 60 0D 01 01 32 01 00 25 F2 49 
2017-12-01 23:42:56.180 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 37: sentData successfully placed on stack.
2017-12-01 23:42:56.187 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: TID 1129: Transaction not completed
2017-12-01 23:42:56.214 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 37: SendData Request. CallBack ID = 242, Status = Transmission complete and ACK received(0)
2017-12-01 23:42:56.215 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-01 23:42:56.223 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Response processed after 66ms
2017-12-01 23:42:56.225 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: TID 1129: Transaction completed
2017-12-01 23:42:56.227 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: notifyTransactionResponse TID:1129 DONE
2017-12-01 23:42:56.231 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2017-12-01 23:42:56.237 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Application Command Request (ALIVE:DONE)
2017-12-01 23:42:56.239 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: resetResendCount initComplete=true isDead=false
2017-12-01 23:42:56.241 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2017-12-01 23:42:56.243 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: Incoming command class COMMAND_CLASS_METER, endpoint 1
2017-12-01 23:42:56.245 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY NOT required on COMMAND_CLASS_METER
2017-12-01 23:42:56.247 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Received COMMAND_CLASS_METER V3 METER_REPORT
2017-12-01 23:42:56.249 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 37: Meter: Type=Electric(1), Scale=kWh(0), Value=0E+1
2017-12-01 23:42:56.252 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveMeterValueEvent
2017-12-01 23:42:56.254 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_METER, value = 0E+1
2017-12-01 23:42:56.256 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Updating channel state zwave:device:15f1ee0619b:node37:meter_kwh1 to 0 [DecimalType]
2017-12-01 23:42:56.260 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Commands processed 1.
2017-12-01 23:42:56.261 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 37: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@15488a7.

sihui · December 1, 2017, 8:18pm

switch_binary1 and switch_binary2, not switch_binary and switch_binary1

Matt77 · December 1, 2017, 8:35pm

yes, the actual once to be used are switch_binary1 and switch_binary2.
but if i use the physical switch connected to S1 only switch_binary gets triggered as showing in my attached logs.
only if i manually refresh in HABmin switch_binary1 gets changed as well.

exactly the same behavior if i connect the switch to S2 only switch_binary gets triggered by the physical switch on S2.

i read in a couple of different forum and it seems that everyone has/had this kind of problem with the fgs-223.
if i only use HABmin to switch switch 1 and 2 no problem but using the physical switch on S1 and/or S2 will not update the software switch.

sihui · December 1, 2017, 8:41pm

Your screenshot tells something different.

Matt77 · December 1, 2017, 9:50pm

[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