I’m very new to the world of z-wave so please take it easy on me.
I have a Fibaro Double Switch 2 that I just successfully managed to wire up myself (yay) and also got it to pair with the Z-stick. All good.
I added the 2 individual switches to the front end of hass.io but it seems like one of the switches is misbehaving.
Specifically, switch.fibaro_system_fgs223_double_relay_switch doesn’t consistently switch the light on if I switch it on from HA and also vice versa, if I change the state of the light manually at the wall switch, it doesn’t update in HA. The other switch, switch.fibaro_system_fgs223_double_relay_switch_2 seems to work ok though.
Have I done anything wrong, or any suggestions on what/where I can check to figure out why Switch 1 doesn’t work as well as Switch 2?
Did you ever get to the bottom of this?
Sounds like the second switch state is being picked up correctly after polling, but it’s not sending it’s status correctly at event time.
How did you get your fgs223 to connect to your Z-stick? I’m having issues with this and could use some help. If you have any tips could you reply in my post below?
Many thanks!
UPDATE
I finally got the fibaro sensor to connect. Now I just need to figure out how to close the blinds using google home voice commands…
I have and run both these devices.
I have a test rig 40cm from my pi with it’s Z-Stick
I power the device and select add node from the z-wave interface
(careful, you HAVE to add ‘some’ nodes as secure nodes to get full functionality, eg anything with a scene controller and the locks (obviously), the double switch didn’t need it)
After selecting the ‘add node’ (or ‘add secure node’) you triple click the devices ‘B Button’ it then takes 30 seconds or so to handshake and populate (be patient).
I then rename all the entities to my naming conventions and move to the next device. I then install the device in final locations as they become available.
Never had a problem so I don’t know what to suggest.
I think you may have no choice but to Remove Node.
Then re-Add Node but ‘close’ (within 1 metre) to your hub (that leaves issues where you relocate to final position and the node appears dead. operate the switch manually a couple of times (make sure it no longer appears dead via the z wave integration) then Heal the network - don’t do this regularly)
here is a copy of my double switch entity naming notes for reference : -
I have same issue with my Z-Stick. Also same problem with S2 button on Fibaro Dimmer 2. I can manually update state by clicking “Refresh entity” in Z-Wave Network Management but I cannot figure it out how to automatically update state of second button
I also have been experiencing the same behavior for years.
Z-Wave Controller: Aeotec Z-Wave Gen5 USB Stick
Fibaro module: FGS223 + FGS213
As described, the second switch does not report correctly and has some misbehaviors. Power also not being reported for S2 (0W).
I tried with a completely different controller: RaZberry V2 (only for Raspberry Pi’s) and all the issues disappeared. The module started to function normally.
It definitely seems to be an issue between Aeotec Gen5 Controller and the Fibaro Switches. Every single FGS223 had the same issue, until the controller changed.
Unfortunately the RazBerry 2 controller is not that fast than the Aeotec Stick, so I went back to Aeotec.
Now the question: do you guys have been using a recent Aeotec Z-Stick (Gen5). By recent I mean with updated firmware.
Perhaps updating the firmware could solve the issue?
But how to update the Aeotec Z-Stick firmware, never managed to get it done. Lack of information in the documentation of Aeotec.