I am running Homey Self Hosted latest version 13.3.1 on a Synology DS423+ and using a Homey Bridge as the Z-Wave gateway.
I have two Fibaro Flood Sensors (FGFS-101, firmware version 25) that worked perfectly for many years with the original Homey Early 2016. After migrating to Homey Self Hosted, temperature and battery reports still work correctly, but water alarms and tamper alarms are no longer detected.
Setup:
- Homey Self Hosted: 13.3.1
- Hardware: Synology DS423+
- Z-Wave controller: Homey Bridge
- Fibaro app: 3.8.9 (official app)
- Device: Fibaro Flood Sensor FGFS-101
- Firmware version: 25
What works:
- Temperature reports
- Battery reports
- Wake-up notifications
What does not work:
- Water alarms
- Tamper alarms
- Flow triggers related to these alarms
I already tried:
- Removing and re-including the devices
- Factory reset of the sensors
- Re-interviewing the devices
- Changing Z-Wave parameter 5 from BASIC_SET to ALARM_WATER (5,1,0)
- Testing multiple sensors
The Z-Wave log shows that the sensor correctly sends a water alarm via COMMAND_CLASS_BASIC:BASIC_SET, but Homey rejects it as unsupported:
Plain text
COMMAND_CLASS_MULTI_CHANNEL:MULTI_CHANNEL_CMD_ENCAP
COMMAND_CLASS_BASIC:BASIC_SET
Value: 255
unsupported command class COMMAND_CLASS_BASIC
Complete log excerpt:
Plain text
[zwave:bridge:1] handleRxCommand COMMAND_CLASS_BASIC:BASIC_SET from 1
Value: 255
[zwave:bridge:1] unsupported command class COMMAND_CLASS_BASIC - BASIC_SET
[zwave:bridge] error handling command from node 5.0, command=600d01012001ff unsupported command class COMMAND_CLASS_BASIC
The sensor itself is working correctly because the alarm frames are received by Homey, but they are ignored by the current Z-Wave stack or Fibaro app.
Is support for the legacy FGFS-101 alarm frames (BASIC_SET / tamper notifications) missing in Homey Self Hosted or in the Fibaro app?
Any idea how to solve this issue and make my two flood sensors now work again also with the new setup?
Thank you.
