New Fibaro Switch FGS-223 is driving me nuts

Hello @vossivossi,

I’m followoing the snapshots for openhab 2. And update around every week / 2 weeks.

Last update was from yesterday I think :slight_smile:

Thank you for this information. So I should also move from the release version to snapshot. Do you download it from cloudbees? (As I am running OH on Windows I need to install and update manually).

@chris:
I also can confirm that the Fibaro FGS223 now works correctly (reporting correctly the different endpoints for Switch1 and Switch2).
BUT: The Qubino ZMNHBD is still NOT working (I tested tonight with Z-Wave binding build 2.1.0.201702181609). I excluded and freshly reincluded 2 of the devices to be sure. The results:

  1. When only the lifeline association is set, no reporting is done to endpoints 1 and 2 (neither for Switch 1/2 nor Power(Watts)1/2).
  2. Even when the association groups for Switch binary or Basic On/Off are set (or both, also tested), NO update comes to the controller for Switch 1/2.
  3. When the assocation groups for power reporting are set, the Power Consumption (Watts) is reported correctly for both endpoints separately(!)

Is there a chance to also get the status reporting of the switches correctly? I have moren than 10 of them installed and can provide any kind of debug log if you tell me what you need. Thanks for your help!

Hello @vossivossi

Im using this script:

Running on Debian linux.

Best regards

Hi Nils,
I have now spent a week trying to get my Fibaro FGS-223 Switch to work with OpenHAB2 on my MacBook Air with UZB stick. I tried to add it through Paper UI on openHAB2 and when I do so, I see the UZB stick flashing blue. Clicking the B-button 3 times on the FGS-223 should usually start the inclusion process, but I only hear the relais click three times (and switch the light), but it does not do anything on openHAB. I have already excluded the security feature for the inclusion process in HABmin. I really don’t know if this is a problem with the FGS 223 or with my openHAB configuration or with the UZB stick. In principle on the Mac with the UZB stick everything looks fine - except for that it does not receive any signal from the FGS-223. I have already reset the FGS 223 various times, but that did not change anything. The Fibaro support team seems tu have no idea. I wonder if you could help me understand the problem?

Please find below the log.

Best regards and many thanks in advance!

Andreas

ZWAVE Log

05:26:25.457 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/tty.usbmodemFA131’
05:26:25.503 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
05:26:25.507 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - Update networkKey
05:26:25.518 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
05:26:25.519 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
05:26:28.669 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 1: Node found
05:26:28.670 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller using Controller API
05:26:28.670 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller is Primary Controller
05:26:28.670 [INFO ] [age.SerialApiGetInitDataMessageClass] - ------------Number of Nodes Found Registered to ZWave Controller------------
05:26:28.670 [INFO ] [age.SerialApiGetInitDataMessageClass] - # Nodes = 1
05:26:28.671 [INFO ] [age.SerialApiGetInitDataMessageClass] - ----------------------------------------------------------------------------

23:52:16.180 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Starting ZWave inclusion scan for zwave:serial_zstick:0ce9f183
23:52:16.181 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller start inclusion - mode 2
23:52:16.182 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Setting controller into INCLUSION mode, highPower:true networkWide:true.
23:52:16.182 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
23:52:16.182 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
23:52:16.186 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A C1 01 70
23:52:16.186 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A C1 01 70
23:52:16.189 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A 01 01 00 00 B2
23:52:16.191 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
23:52:16.191 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 4A 01 01 00 00 B2
23:52:16.191 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 4A 01 01 00 00 B2
23:52:16.192 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 01 00 00
23:52:16.192 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: Learn ready.
23:52:16.192 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInclusionEvent
23:52:16.193 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=C1 01
23:52:16.193 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 01 00 00
23:52:16.194 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=AddNodeToNetwork, callback id=0, expected=AddNodeToNetwork, cancelled=false transaction complete!
23:52:16.194 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
23:52:16.195 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 8ms/169ms.
23:52:46.184 [DEBUG] [ve.internal.protocol.ZWaveController] - Stopping inclusion timer.
23:52:46.185 [DEBUG] [ve.internal.protocol.ZWaveController] - Ending inclusion mode.
23:52:46.185 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.
23:52:46.185 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
23:52:46.186 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
23:52:46.186 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller end inclusion
23:52:46.186 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 05 01 B4
23:52:46.186 [DEBUG] [ve.internal.protocol.ZWaveController] - Stopping inclusion timer.
23:52:46.186 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 01 B4
23:52:46.187 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!
23:52:46.345 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A 01 06 00 00 B5
23:52:46.346 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
23:52:46.347 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 4A 01 06 00 00 B5
23:52:46.347 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 4A 01 06 00 00 B5
23:52:46.348 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 06 00 00
23:52:46.348 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: Done.
23:52:46.348 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInclusionEvent
23:52:46.349 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=05 01
23:52:46.350 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 06 00 00
23:52:46.350 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=AddNodeToNetwork, callback id=0, expected=AddNodeToNetwork, cancelled=false transaction complete!
23:52:46.350 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
23:52:46.351 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 164ms/169ms.

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.

1 Like

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.

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.

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

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…:frowning: ) I am running OH2.0.0 Release Build with 2.0.0 Z-Wave binding on Windows with Aeon Z-Stick 5.

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

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. :slight_smile:

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

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 … :slight_smile:

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

Make sure you have the correct channels:

S1 = switch_binary1
S2 = switch_binary2

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

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.

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?

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