Checklist
- Home Assistant Core: 2026.6.4
- Home Assistant OS
- Raspberry Pi 5 (64-bit)
- Home Assistant Connect ZWA-2
- Z-Wave JS Driver: 15.25.0
- Z-Wave JS Server: 3.10.0
- ZWA-2 Firmware: 1.2
- Device: POPP Smoke Sensor 004001
- Device Firmware: 2.1
Describe the bug
I have multiple POPP 004001 smoke detectors included in my Z-Wave network.
The smoke detectors are periodically marked as Dead/Unavailable by Z-Wave JS, although they usually come back online automatically after some time without any user interaction.
Sometimes they also recover immediately after pressing the test button, but most of the time they recover on their own.
The issue affects multiple POPP smoke detectors, not just a single device.
Expected behavior
Battery-powered smoke detectors should remain available (or asleep) and should not be marked as dead unless communication has actually failed permanently.
Actual behavior
The smoke detectors are periodically marked as dead/unavailable.
After several minutes or even hours they become available again without re-inclusion or manual repair.
Network information
- Approximately 46 Z-Wave devices
- Many mains-powered routing devices:
- Shelly Wave
- Shelly Wave Plus
- Fibaro Roller Shutter
- Fibaro Switches
- Devolo Alarm Siren
- Mesh coverage is good throughout the house.
- Other battery-powered devices (Fibaro Motion Sensors, Aeotec MultiSensor, etc.) appear to be much more stable.
Z-Wave statistics
The controller statistics do not indicate communication problems:
- TX dropped: 0
- NAK: 0
- ACK timeout: 0
- Response timeout: 0
- Only a few dropped RX packets over thousands of messages
Smoke detector configuration
- No direct Association Groups configured
- Devices report only to Home Assistant
- Automated Smoke Alarm Meshing: Disabled
- Automated Battery Alarm Meshing: Disabled
Additional observations
The Home Assistant Connect ZWA-2 occasionally reports its status as "Jammed" , then shortly afterwards returns to "Ready" .
I am not sure whether this is related.
Troubleshooting already performed
- Re-interviewed devices
- Verified batteries
- Good Z-Wave mesh with many routing nodes
- Latest Home Assistant and Z-Wave JS versions
- Latest ZWA-2 firmware available
- Devices usually recover automatically without manual intervention
Question
Is this expected behaviour for the POPP 004001 because of its sleep behaviour, or could this indicate a compatibility issue between the POPP firmware and recent Z-Wave JS versions?
If additional debug logs are required, I can provide them.
"I have also opened a troubleshooting discussion with the Z-Wave JS maintainers: POPP 004001 smoke detectors periodically become dead and recover automatically · zwave-js/zwave-js · Discussion #8905 · GitHub"