Lights frequently become unavailable

Configuration Zigbee
1

I’m using the HUSBZB-1 and my lights frequently will show as “unavailable” and I need to restart HA or the docker container to get them to show up again. This seems to happen once a day and has occurred for the last several weeks or months, across versions of HA.

These are logs, but this is from after a reboot when the lights are working fine:
019-03-12 00:25:31 WARNING (MainThread) [homeassistant.helpers.config_validation] Your configuration contains extra keys that the platform does not support. Please remove [forecast], [monitored_conditions]. (See /config/configuration.yaml, line 72). 2019-03-12 00:25:41 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=3 command=1 args=[[<ReadAttributeRecord attrid=0 status=0 value=255>]] 2019-03-12 00:25:44 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=6 command=1 args=[[<ReadAttributeRecord attrid=0 status=134>]] 2019-03-12 00:25:44 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=7 command=1 args=[[<ReadAttributeRecord attrid=0 status=134>]] 2019-03-12 00:25:44 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=8 command=1 args=[[<ReadAttributeRecord attrid=7 status=0 value=3>]] 2019-03-12 00:25:44 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=9 command=1 args=[[<ReadAttributeRecord attrid=49 status=0 value=2>]] 2019-03-12 00:25:44 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=6 command=1 args=[[<ReadAttributeRecord attrid=0 status=134>]] 2019-03-12 00:25:44 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=7 command=1 args=[[<ReadAttributeRecord attrid=0 status=134>]] 2019-03-12 00:25:44 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=8 command=1 args=[[<ReadAttributeRecord attrid=7 status=0 value=3>]] 2019-03-12 00:25:44 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=9 command=1 args=[[<ReadAttributeRecord attrid=49 status=0 value=2>]] 2019-03-12 00:25:45 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=6 command=1 args=[[<ReadAttributeRecord attrid=0 status=134>]] 2019-03-12 00:25:45 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=7 command=1 args=[[<ReadAttributeRecord attrid=0 status=134>]] 2019-03-12 00:28:43 WARNING (MainThread) [bellows.zigbee.application] Unexpected message send notification 2019-03-12 00:28:43 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=13 command=1 args=[[<ReadAttributeRecord attrid=0 status=0 value=Bool.true>]] 2019-03-12 00:28:43 WARNING (MainThread) [bellows.zigbee.application] Unexpected message send notification 2019-03-12 00:28:43 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=14 command=1 args=[[<ReadAttributeRecord attrid=0 status=0 value=255>]] 2019-03-12 01:52:36 WARNING (MainThread) [bellows.zigbee.application] Unexpected message send notification

2

Updated to 0.89.2 and two of my lights are unavailable

3

I have similar issues. I’m on the latest HA release with the same HUSBZB hardware and zha.

I was able to get everything up and connected for a while but I was adding stuff to HA last night and had to restart HA a few times and after that no zigbee devices want to connect.

What is the suggested method to reconnect stuff? Do I really need to go and re-pair everything?

Are there others zigbee solutions more reliable than the HUSBZB?

4

I had this issue until I updated to 0.90, ZHA has been rock solid for me ever since

5

Are you on a prerelease version?
Is there any change notes on what they updated?

I’ll give this a try to see if it improves stuff.

6

Yes, I am on 0.90.0b5. Here is the relevant PR https://github.com/home-assistant/home-assistant/pull/21866

7

0.90 worked for a while for me, but while making some changes to my config last night all my zigbee went unresponsive again :frowning: