FGSD002 Not reporting Smoke Alarm

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within ZWaveJS2MQTT?

NO, my problem is NOT within ZWaveJS2MQTT

Checklist

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there.

Describe the bug

What causes the bug? The Fibaro Smoke Sensor is pickup up correctly but when triggering a Smoke Alarm test on it, I do not see any topics coming in and last seen state is also not updated

What do you observe? No updates come in on ZwaveJS UI

What did you expect to happen? Expect data to come in about Alarm

Steps to reproduce the behavior:

1. Go to ZwaveJS UI and open Device
2. On Physical Fibaro Device trigger Self Test

Before I used OpenZwave in Domoticz and triggering a Self test would give me Alarms coming in.

Device information

Manufacturer: Fibaro Model name: FGSD002 Node ID in your network: 37

How are you using node-zwave-js?

• zwavejs2mqtt Docker image (latest)
• zwavejs2mqtt Docker image (dev)
• zwavejs2mqtt Docker manually built (please specify branches)
• ioBroker.zwave2 adapter (please specify version)
• HomeAssistant zwave_js integration (please specify version)
• pkg
• node-red-contrib-zwave-js (please specify version, double click node to find out)
• Manually built from GitHub (please specify branch)
• Other (please describe)

Which branches or versions?

version: 10.2.0 node-zwave-js branch: 10.2.0 zwavejs2mqtt branch:

zwave-js-ui: 8.0.0 zwave-js: 10.2.0 home id: 3244133030 home hex: 0xc15d8aa6

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

Don’t know, this is a new device

If yes, where did it work?

No response

Attach Driver Logfile

zwavejs_2022-09-21.log

1. Did a device wakeup
2. Initiated Alarm self test
3. did a device wakeup

[AlCalzone]

Not sure what this would mean for Domoticz as I think they use this.

I think long term they should move over to the websocket API, but their dev once said they’d keep using the MQTT api because they already have a system in place for it and it works. I guess that’s fair, but we can’t make any guarantees that everything will work over that API indefinitely.

[AlCalzone]

Ok unless you edited them in the meantime, they are identical. Can you try again with zwave-js, but disable any filtering on the logs? Not that the message was just filtered out.