Fibaro Double Switch 2 (FGS-223 ZWave) physical switch state not reliably updating in Homey

Questions & Help
,
1

The trouble started a few months ago when flows are not working anymore.
It has been working for 6 years before.

It seems the state of the Fibaro Double Switch FG223 is not updated in Homey when pressing the physical momentary switch.

Guess:
Some flows should be triggers when devices go on/off but arent’t because Homey doesn’t update the state.

Environment

  • Homey: Homey Pro (2019)

  • Homey firmware: 13.5.0

  • Fibaro app: 3.8.18

  • Device: Fibaro Double Switch 2 (FGS-223)

  • Z-Wave node ID: 29

  • Driver: homey:app:com.fibaro:FGS-223

  • Manufacturer ID: 271

  • Product type ID: 515

  • Product ID: 4096

  • Device status: Ready = Yes, Available = Yes

Problem

Physical switching of the two inputs on a single Fibaro Double Switch does not reliably update the corresponding on/off state in the Homey app.

One of the two switch channels sometimes updates the Homey tile, although with a significant delay. The other channel does not reliably update its tile at all.

The device can eventually be controlled from the Homey app, so it is not completely unresponsive. However, Homey’s displayed state does not consistently reflect the physical switch state. This also affects flows that depend on the on/off state or a device being turned on or off.

The problem has affected 3 of my 8 Fibaro Double Switch devices. At least one other device appears to work correctly.

Steps to reproduce

  1. Open the affected Fibaro Double Switch device in the Homey app.

  2. Observe the current on/off state.

  3. Operate one of the physical wall switches.

  4. Check whether the corresponding Homey tile updates.

  5. Repeat with the other switch input.

  6. Compare the displayed state with the actual physical output state.

Expected result: Homey should update the relevant on/off state promptly whenever either physical switch changes the output state.

Actual result: One channel updates intermittently or slowly, while the other fails to update reliably. The Homey tile can remain in the wrong state even though the physical switch has been operated.

Z-Wave diagnostic observations

I inspected the Z-Wave logs in Homey Developer Tools for node 29 while physically operating the switches.

The logs contain MULTI_CHANNEL_CMD_ENCAP reports for both endpoint 1 and endpoint 2. The reports include:

  • COMMAND_CLASS_BASIC with value 255 (on) and value 0 (off).

  • COMMAND_CLASS_SWITCH_MULTILEVEL with value 255 (on) and value 0 (off).

These reports appeared while I physically operated the switches. This suggests that Z-Wave communication is registering state changes from both endpoints, even when the Homey tile does not update accordingly.

I have not yet established conclusively which endpoint corresponds to the channel whose Homey tile fails to update.

Additional observations

  • Initially, after restarting the Fibaro app, I encountered a Missing Capability Listeners: onoff error when trying to control a device.

  • After waiting a few minutes, the device became controllable from the Homey app again, and the error no longer appeared.

  • Physical switch state reporting remains unreliable despite the device showing as ready and available.

  • The affected device currently has an onoff capability, with its displayed value sometimes not matching the physical state.

  • The meter_power capability has also updated recently, suggesting that at least some device updates are still reaching Homey.

Device details from Homey Developer Tools

The affected device reports the following settings:

  • switch_type: 0

  • save_state: false

  • zw_secure: enabled

  • zw_configuration_value: empty

I have not changed these settings during troubleshooting.

What I would like help investigating

Could this be an issue with how the Fibaro app or Homey’s Z-Wave driver handles physical state reports from the two endpoints of the FGS-223?

In particular:

  1. Are reports from both endpoints being received and mapped to the correct Homey device capabilities?

  2. Could the Missing Capability Listeners: onoff error indicate a problem with capability listener registration?

  3. Is there a known issue with physical switch state reporting on the FGS-223 with the current Fibaro app or Homey firmware?

  4. Is there a recommended diagnostic procedure to determine why Z-Wave state reports appear in the logs but the Homey tile does not update?

I would prefer to avoid removing or re-pairing the device unless necessary, as the device is installed in a wall and can still be controlled from Homey.

Thanks for any suggestions or help investigating this.