Battery/Wireless Zwave devices all "unavailable"

Configuration Z-Wave
1

We had a power outage earlier this evening. Once everything came back up, I noticed that none of my Zwave motion sensors or remotes were working.

Checking the dev tools shows that they all have a status of “unavailable”

I tried a reboot of the Pi that I run Home Assistant on, but no change. Where should I start looking to trouble-shoot?

Running core-2021.10.3 with the (now deprecated) zwave integration, not the JS version.

The only log messages that I see related to Zwave are that some items weren’t ready yet:

Z-Wave node 54 not ready after 30 seconds, continuing anyway

The last such message was logged 20 minutes ago, shortly after reboot. I’m not sure what device that represents - there’s no entity with a node_id of 54 on the states page of dev tools.

2

Over night, one of my sensors returned - a magnetic door open/close sensor. All of the remotes and motion sensors are still “unavailable”

3

Battery operated devices only communicate periodically. I know the new zwavejs based integration will patiently wait. I have had some take several hours to fully interview.

It has been years since I used the old integration so I do not recall how it behaves in your situation. Since the developer has basically stopped supporting the old integration perhaps you should consider moving. I prefer using zwavejs2mqtt due to its superior control panel for z-wave,

4

My experience has been that z-wave js is superior to OZW. And it is getting better all the time. There is a guide to converting from OZW to z-wave js.

1 Like
5

Indeed!
I left HA 3 years ago primarily because of OZW. I am coming back not because of zwavejs.

6

After waiting about 12hrs to see if things worked themselves out, I ended up restoring my HA install from a backup. After the restore, everything worked fine again. I guess that the power outage corrupted a file related to OZW.

Glad to have things working. I wanted a working OZW install before I started moving to Zwave JS. So then if something acts weird, I know its from the migration, not an pre-existing issue.