Since an upgrade last summer, my wall switches (WD500Z-1) have randomly become unavailable (dead). Forcing a “rebuild routes” will restore…briefly.
I am using z-wave JS UI, Zigbee2MQTT, and the Mosquitto broker. I prefer simple, but went this route with mqtt due to more support for older devices.
With the Zigbee side, that has been pretty stable until the 2026 update, which I did over the weekend. Since the upgade (from 2025.11) my wired motion sensor (critical to many automations, flipping state of the house) no longer functions…seen by system, but no motion is reported (device: STSS-IRM-001).
Any others having this much trouble with Home Assistant lately?
Thank you (ahead of time) for any insight and assistance.
I am leveraging a VM off of a synology nas. Been setup for 3 years (?) and no issues till last summer upgrade. Worse with the 2026 update that broke several item (Samsung’s motion 2013 STSS-IRM-001 and Samsung’s multi sensor STSS-MULT-001 2013). Maybe they elected to stop supporting old devices? Tried connecting a new STSS-IRM-001 device (several in drawer unused) and it too will connect, but not function (no state data is transmitted).
For the unavailable issue, rebooting has not solved anything (tried multiple times), nor has any of the updates. I see disconnects/dead devices such as following, which is a 90 min capture (black lines indicate dead device).
Same here. Using Zwave-JS running on docker with 60-70 devices was rock stable for years (since 2018). Last summer, things started to change. I migrated my old zwave stick (Aeotec Gen 5) to Aeotec G5+ and even to a Home Assistant connect ZWA-2.
The ZWA-2 seems a bit more stable but not significant. Since the summer It appears that nodes spontaneously forgot their neighbors from time to time. Some sensors drop ‘dead’ and most sensors become ‘unknown’ in the zwave-js graph. So I spend a couple of hours by forcing powered nodes to find neighbors and setting priority routes. The effect is that most nodes will find their way afterwards and the network becomes responsible again.
This is after manually having devices discover their neighbors. Still lots of grayed devices ('unknown) and some red lines. What has happened this summer? Does this have a relation to the introduction of the long range bullshit that throws the whole mesh principle away? (If you want long range, choose lora instead please)
I am not as sophisticated in describing the situiation but recognize the sympthoms.
Yesterday some 15 of my 64 Zwave devices did not work and shows that they were being re-interviewed, which slowed down HA considerably. It all came back, sometimes by manually turning on/off the switch, but it is an issue that I have had for almost a year,
I use a Yellow Box and a Zooz 800 series ZWave dongle.
