After restore many battery Zwave devices are not available

Configuration Z-Wave
1

Last week I had a hardware error where the solution was to get a new memory card and reinstall. So that’s what I did. This past weekend I reinstalled HA v0.97.1 and then I restored all of my configuration files.

Everything seems to be working except for most of my battery powered Z Wave devices. I say most because my 2 door locks work fine. All of the other battery powered devices are not showing up at all in any menu. It’s like the devices never existed.

I was wondering if there was a way to get these back because from what I understand, Z Wave devices are registered on the Z Stick which in my case is an Aeotec Z Stick.

Here is my log file…

2019-08-13 09:04:16 INFO (MainThread) [homeassistant.components.zwave] Z-Wave USB path is /dev/ttyACM0
2019-08-13 09:04:21 WARNING (MainThread) [homeassistant.setup] Setup of input_number is taking over 10 seconds.
2019-08-13 09:04:23 WARNING (MainThread) [homeassistant.setup] Setup of person is taking over 10 seconds.
2019-08-13 09:04:24 WARNING (MainThread) [homeassistant.components.lifx.light] LIFX no longer works with light platform configuration.
2019-08-13 09:04:24 WARNING (MainThread) [homeassistant.setup] Setup of input_boolean is taking over 10 seconds.
2019-08-13 09:04:27 WARNING (MainThread) [homeassistant.components.scene] Setup of platform lifx_cloud is taking over 10 seconds.
2019-08-13 09:04:32 INFO (SyncWorker_13) [homeassistant.components.zwave] Starting Z-Wave network...
2019-08-13 09:05:06 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 12 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:06 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 13 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:06 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 14 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:06 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 6 not ready after 31 seconds, continuing anyway
2019-08-13 09:05:06 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 6 Sensor (node_id: 6) not ready after 31 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 20 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 21 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 22 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 23 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 24 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 25 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 27 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 28 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 29 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 30 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 31 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 32 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 33 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 34 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:07 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 35 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 39 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 40 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:32 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 41 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:32 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 42 not ready after 30 seconds, continuing anyway
2019-08-13 09:05:32 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 43 not ready after 30 seconds, continuing anyway
2019-08-13 09:09:33 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave not ready after 300 seconds, continuing anyway
2019-08-13 09:09:33 INFO (MainThread) [homeassistant.components.zwave] final network state: 5 Driver initialised
2019-08-13 09:09:33 INFO (SyncWorker_4) [homeassistant.components.zwave] Z-Wave polling interval set to 60000 ms
2019-08-13 09:12:37 INFO (Dummy-5) [homeassistant.components.zwave] Z-Wave network is ready for use. All awake nodes have been queried. Sleeping nodes will be queried when they awake.
2

Z-Wave and ZigBee devices are paired to the device, like you said. Home Assistant definitely shows it knows others exist.

I would suggest running a “Add Node” (Secured if needed) and ‘waking’ up the devices by pressing their button to see if they come back. I’ve had to do that in the past with devices. It’s just the nature of the beast unfortunately.

3

So Add a node through HA and then try waking the device? Or pairing the device?

4

It’s basically the same thing. Devices and controllers (HA) know where the devices belong if they’ve already been paired.

You can try simply waking the devices up by pressing their pairing button but typically in situations like this, you need to run an “Add Node” and pressing the button on the device to get them to start talking together again. Most times, they’ll just resync up.

5

I had this multiple times after adding or removing a zwave device. I noticed that it seems to occur when I do not save the zwave config from HA. Also, be sure Zwave is fully ready and not still starting before you restart HA. Backup your HA and restore the backup to have all your devices back.

6

As a test I put new batteries in one of my motion sensors and I pressed the button multiple times to force a wakeup and the status updated in HA.

I did not do anything in HA.

So I am going to try that and report back.

7

Could you have missed the zwcfg*.xml file when you restored your config files?

8

No, I copied it over. But I was told long ago that file is overwritten on boot.

9

The cache file is updated when the network starts, as in the node values are updated to their current state, but it is not wiped clean. If you lose the cache file, the zwave network is fine, but HA will not know about any of the entities until OZW refreshes the information about the nodes. Battery devices may take time to update, either through value updates, wake ups, or by physically press a button to re-send the info.

10

It’s been 2 days and the devices are still not showing up. So I think I need to activate the device to and see if the status updates.