Updated Hass.io And Now All Zwave Devices Are Listed As Unavailable

Tags: #<Tag:0x00007f77ff4e4c50>

Hello everyone,

I updated Hass.io/Home Assistant through the Web UI and now all my Zwave light switches are listed as Unavailable:

The only Zwave device that works is my Schlage Zwave Deadbolt:

image

Here’s an error I see in the OZW Logs:

2020-02-08 13:21:46.640 Info, Node040, UPDATE_STATE_NODE_INFO_RECEIVED from node 40
2020-02-08 13:21:46.640 Detail, Node040, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Dynamic live=1
2020-02-08 13:21:46.640 Detail, Node040, QueryStage_Dynamic
2020-02-08 13:21:46.640 Detail, Node040, Queuing (Send) SwitchBinaryCmd_Get (Node=40): 0x01, 0x09, 0x00, 0x13, 0x28, 0x02, 0x25, 0x02, 0x25, 0x86, 0x4b
2020-02-08 13:21:46.640 Detail, Node040, Queuing (Query) Query Stage Complete (Dynamic)
2020-02-08 13:21:46.640 Detail,
2020-02-08 13:21:46.641 Info, Node040, Sending (Send) message (Callback ID=0x86, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=40): 0x01, 0x09, 0x00, 0x13, 0x28, 0x02, 0x25, 0x02, 0x25, 0x86, 0x4b
2020-02-08 13:21:46.649 Detail, Node040,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-02-08 13:21:46.650 Detail, Node040,   ZW_SEND_DATA delivered to Z-Wave stack
2020-02-08 13:21:46.671 Detail, Node040,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x28, 0x03, 0x25, 0x03, 0xff, 0x00
2020-02-08 13:21:46.671 Detail,
2020-02-08 13:21:46.671 Info, Node040, Response RTT 30 Average Response RTT 114
2020-02-08 13:21:46.671 Info, Node040, Received SwitchBinary report from node 40: level=On
2020-02-08 13:21:46.672 Detail, Node040, Refreshed Value: old value=false, new value=true, type=bool
2020-02-08 13:21:46.672 Detail, Node040, Changes to this value are not verified
2020-02-08 13:21:46.672 Detail, Node040, Notification: ValueChanged
2020-02-08 13:21:46.857 Detail, Node040,   Received: 0x01, 0x07, 0x00, 0x13, 0x86, 0x00, 0x00, 0x15, 0x78
2020-02-08 13:21:46.857 Detail, Node040,   ZW_SEND_DATA Request with callback ID 0x86 received (expected 0x86)
2020-02-08 13:21:46.857 Info, Node040, Request RTT 216 Average Request RTT 169
2020-02-08 13:21:46.857 Detail,   Expected callbackId was received
2020-02-08 13:21:56.642 Error, Node040, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-08 13:21:56.642 Detail, Node040, Removing current message
2020-02-08 13:21:56.642 Detail, Node040, Notification: Notification - TimeOut
2020-02-08 13:21:56.647 Detail, Node040, Query Stage Complete (Dynamic)
2020-02-08 13:21:56.648 Detail, Node040, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Configuration live=1
2020-02-08 13:21:56.648 Detail, Node040, QueryStage_Configuration
2020-02-08 13:21:56.648 Detail, Node040, QueryStage_Complete
2020-02-08 13:21:56.648 Warning, CheckCompletedNodeQueries m_allNodesQueried=1 m_awakeNodesQueried=1
2020-02-08 13:21:56.648 Detail, Node040, Notification: NodeQueriesComplete

Here is my home-assistant.log:

config $ cat home-assistant.log 

2020-02-08 13:18:07 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'True') is deprecated, please remove it from your configuration. This option 
will become invalid in version 0.107.0
2020-02-08 13:18:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 17 not ready after 30 seconds, continuing anyway
2020-02-08 13:18:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 17 Switch (node_id: 17) not ready after 30 seconds, continuing anyway
2020-02-08 13:18:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 18 not ready after 30 seconds, continuing anyway
2020-02-08 13:18:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 18 Switch (node_id: 18) not ready after 30 seconds, continuing anyway
2020-02-08 13:18:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 19 not ready after 30 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 19 Switch (node_id: 19) not ready after 30 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 20 not ready after 30 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 20 Switch (node_id: 20) not ready after 30 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 21 not ready after 30 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 3 not ready after 31 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 3 Switch (node_id: 3) not ready after 31 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 4 not ready after 31 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 21 Switch (node_id: 21) not ready after 30 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 4 Switch (node_id: 4) not ready after 31 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 10 not ready after 31 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 22 not ready after 30 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 10 Switch (node_id: 10) not ready after 31 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 11 not ready after 31 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 11 Switch (node_id: 11) not ready after 30 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 12 not ready after 30 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 12 Switch (node_id: 12) not ready after 30 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 13 not ready after 30 seconds, continuing anyway
2020-02-08 13:18:45 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 13 Level (node_id: 13) not ready after 30 seconds, continuing anyway
2020-02-08 13:18:46 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 22 Switch (node_id: 22) not ready after 30 seconds, continuing anyway
2020-02-08 13:18:46 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 23 not ready after 30 seconds, continuing anyway
2020-02-08 13:18:46 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 23 Level (node_id: 23) not ready after 30 seconds, continuing anyway
2020-02-08 13:18:46 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 28 not ready after 30 seconds, continuing anyway
2020-02-08 13:18:46 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 28 Switch (node_id: 28) not ready after 30 seconds, continuing anyway
2020-02-08 13:18:46 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 30 not ready after 30 seconds, continuing anyway
2020-02-08 13:18:46 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 30 Switch (node_id: 30) not ready after 30 seconds, continuing anyway
2020-02-08 13:18:46 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 31 not ready after 30 seconds, continuing anyway
2020-02-08 13:18:46 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 31 Switch (node_id: 31) not ready after 30 seconds, continuing anyway
2020-02-08 13:18:46 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 32 not ready after 30 seconds, continuing anyway
2020-02-08 13:18:46 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 33 not ready after 30 seconds, continuing anyway
2020-02-08 13:18:46 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 33 Switch (node_id: 33) not ready after 30 seconds, continuing anyway
2020-02-08 13:18:47 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 43 not ready after 30 seconds, continuing anyway

and my hass.io info:

config $ hassio info
arch: aarch64
channel: stable
hassos: "3.9"
homeassistant: 0.105.2
hostname: hassio
logging: info
machine: raspberrypi3-64
supervisor: "199"
supported_arch:
- aarch64
- armv7
- armhf
timezone: America/New_York

My Zwave gateway is an: AEON Labs ZW090 Z-Stick Gen5 US

Anyone know what’s going on and how I can correct this issue to get my Zwave devices back online?
I’ve tried several reboots but it did not make any difference.

Do you have a backup before you upgrade? Sure you do right? You could try and restore your zwcfg xml file and stop HA. Then replace the file and start it again. If that doesn’t help, then i don’t know (other then removing zwave and re-adding and then adding the file again. Just make sure you make backups when you play.

You can also try to delete that file. HA will automatically recreate a new one when you restart. The node information is stored on the stick itself so you will not lose any of your zwave network.

I took a snapshot a few weeks ago and have not added any devices since then. I assume the snapshot taken on the prior version of HA will import okay into this new version of HA?

I executed:

config $ mv ./zwcfg_0xf72d953d.xml ./zwcfg_0xf72d953d.xml.bak

then rebooted and hass.io recreated a new: zwcfg_0xf72d953d.xml file but it did not matter as the Zwave devices are still listed as: “Unavailable”.

I executed:

config $ mv ./zwcfg_0xf72d953d.xml ./zwcfg_0xf72d953d.xml.bak

which I assumed was acceptable?

One thing I did notice is there is no “homeassistant” user

config $ id homeassistant
id: unknown user homeassistant

and the AEON Labs ZW090 Z-Stick Gen5 US (/dev/tty/ACM0) I thought according to this should be in the “dialout” group?

config $ ls -ltr /dev/ttyA*|tail -n 2
crw-rw----    1 root     audio     204,  64 Feb  8 14:26 /dev/ttyAMA0
crw-rw----    1 root     audio     166,   0 Feb  8 14:26 /dev/ttyACM0

(/dev/ttyACM0 from what I understand is the RPi’s UART)

I executed:

config $ chmod g+rw /dev/ttyACM0

crw-rw----    1 root     dialout   166,   0 Feb  8 14:26 /dev/ttyACM0

and reloaded the groups as well as restarted the server but it makes no difference and the Zwave devices are still: “Unavailable”.

executing:

config $ hassio host reboot

causes the group /dev/ttyACM0 to revert back to “audio” group:

~ $ ls -ltr /dev/ttyA*|tail -n 2
crw-rw----    1 root     audio     204,  64 Feb  8 21:06 /dev/ttyAMA0
crw-rw----    1 root     audio     166,   0 Feb  8 21:06 /dev/ttyACM0

So I have been using Home Assistant 0.105.2 for a few days but ran into some issues along the way.

  1. I restored 0.104.3 snapshot and then proceeded to upgrade to 0.105.2 but after rebooting my Zwave devices were listed as: “Unavailable” again.

  2. I restored 0.104.3 snapshot again but this time deleted the: zwcfg_0xf72d953d.xml before upgrading to 0.105.2.

This seems to work as it has survived several reboots and my Zwave devices are still available. Not really sure if this was the problem or just coincidence. I appreciate all the help though!

Also facing the same issue, but it seems to only affect my battery powered devices.

(from memory, so apply about a half-full hand of salt):
On home assistant core (venv, pi4)
Upgraded from 0.104.x to 0.105.2 - no reboot.
Did not notice that some of the z-wave devices didn’t work, but didn’t specifically check.
Upgraded from 0.105.2 to 0.105.5 and also rebooted. Spotted the devices that are not working.
Was playing a bit with this and other unrelated things, but never fully diagnosed it.

@riemers - actually have really good backups, but too lazy to figure out the combination of events and configuration changes to find the point in time I need to restore.
The devices not working are not currently very integral to my setup. But I will safeguard those backups so they won’t be rotated off my backup server.
This comment is intended as a #metoo , but with an added level of laziness… If needed I will of course debug.

I am facing the same issues, but I dont have any error in the zwave logs. I can see the devices trigger in the logs yet they are unavailable.

I had the same issue a couple week ago following a lost of electricity for 12h and then intermittent up and down. I fixed it by removing the 3 troubled nodes and then re-added them. It worked great but now I have zombie node that I can’t removed.

3 days ago, I restarted HA following addition of a new device_tracker using the UI restart and the same issue happen again, with the same 3 nodes being unavailable.

I tried the solution to downgrade, delete the zwcfg.xml and upgrade, but this didn’t fix my issue. I suppose I will have to manually remove and re-added those node… All 3 nodes are battery powered. I have other battery powered devices that doesn’t cause this issue.

I am open to investigate further, but I don’t know where to start.