Core: ZHA: Sensors are unavailable, underlying device is online.

[ryanwinter]

Home Assistant release with the issue:
0.88.0

Last working Home Assistant release (if known):
0.87.0

Operating environment (Hass.io/Docker/Windows/etc.):
FreeBSD + HUSBZB-1

Component/platform:
zha

Description of problem:
I have around 12 Smarthings devices (multi + moisture + motion), and 10 ikea light bulbs.
After restarting, the sensors appear as "Unavailable" in lovelace. After waiting for ~1-2 minutes, most devices start functioning but a number still stay unavailable.

Looking in the states panel, all the zha devices are listed as online. I can also query the devices through the zha configuration panel and correctly get responses.

It appears that even though the device is working correctly, somehow the associated sensors are not connected anymore.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

zha:
  usb_path: /dev/cuaU1
  database_path: /mnt/homeassistant/hass/zigbee.db

[dmulcahey]

Can you enable debug logging for zha, and zigpy and bellows and restart? Then give me the logs when you get into this situation?

[ryanwinter]

Hi David,

I have attached the log. Only one device was impacted this time.

• zha.kitchen_door_multi
• nwk: 0x39a0
• ieee: 24:fd:5b:00:01:07:89:07

home-assistant_unavailable_zha.log

[dmulcahey]

I’ll look into this tonight, will have info for you soon hopefully

[techwithjake]

I have the same issues. Removing the Node and re-adding seems to get it working again.

~All the custom names set through the ZHA dashboard are no longer showing either in the ZHA Dashboard. I'm not sure if that's more of a HA issue than a ZigPY/Bellows issue though.~ Already reported https://github.com/home-assistant/home-assistant/issues/21242

[dmulcahey]

@ryanwinter have a couple minutes to help me troubleshoot this? If so, mind jumping on discord?

[speedmann]

I have the same issue with ikea lights.
After i start home assistant, 4-5 out of the 6 lights work normal, 2 stay unavailable.
Restarting home assistant seems to "shift" the problem to other devices, but at least 1-2 devices stay unavailable.
I tried to rejoin the devices to the network, but this did not change anything.
I reverted back to 0.87.1 just to find out the issue persists and only was solved by readding all devices (again) which is quiet tedious.

Let me know if i can help with any more information.

[dmulcahey]

please stop removing / re-adding devices :) that won't help with this. Devices will remain unavailable in general until they communicate with the network and that change is intentional. Ryan's issue is a bit different where the devices show online but the sensors are unavailable. Take a look at the screenshot above. If you don't have the same situation, your devices are functioning as intended. A change was put into this release to show the true state of the entities / devices because what we were presenting before was stale state which led to numerous issues.

[ryanwinter]

Hi David,

I'm still seeing the issue after making the code change. I have attached a new log file.

home-assistant_unavailable_zha_4.log

[speedmann]

sorry @dmulcahey i did not made it clear, i have the exact same behaviour. zha. entity is online and the light entity is unavailable.
But i will leave this report for as long as you do not need me, to stop confusing people.

[dmulcahey]

@speedmann I was just trying to clarify the issue. There is no reason for you to leave the report :) I’ll take debug logs from you as well if you don’t mind.

I should have been more clear in the 2 points I was trying to make:

Removing and re-adding the devices won't help and isn't necessary. In saying that, I am trying to save you time and frustration. :)

people were confused in general about the availability statuses of the sensors. This is something I accept full responsibility for as I should have added more to the PR to describe the impact. I can imagine it must have been a bit jarring to see everything initially marked as unavailable. What I was trying to communicate was that part of this change was 100% intentional and to ensure that people understand that the scenario in the screenshots is where the issue is.

I am sorry if the tone in my original response was off putting and I am sorry for causing the issue in the first place! :)

I'm on the case though and hopefully there is a permanent solution soon.

[ryanwinter]

Should I reopen a new issue?

[dmulcahey]

Not yet, jump on discord again for a sec please

[techwithjake]

Can confirm patches work. Devices need to talk back to HA first but once they do, they will show correct states. The timing is up to the device, range and interference but once they talk, they're good.

[perosb]

Hi,

I'm running 0.88.1 and seeing similar issue.
Some lights will after a while report as "unavailable". If I go and flick the wall switch, it immediately turns up as available again.

I don't have any logs just yet.

[ryanwinter]

I have started to see the same behavior as well. Doing a reconfigure from the zha control panel behind it back online.

[dmulcahey]

I have a solution. It appears some manufacturers don’t report anything even though they are configured to report. I’ll have an update later this evening most likely.

[causefx]

I too tried 88.1 but all but 3 devices showed as unavailable. I left it running throughout the night and when i woke up, all devices were unavailable. All automations were broken since the sensors didnt work. I reverted to 87.1 and all devices started working right away,

[ryanwinter]

Let me know if you need some logs, or if you want me to run some code. The problem is very intermittant for me though, this morning all sensors were fine.

[jlvandusen]

Hello I am seeing the same thing as above...
Sometime after 87.x for me my zigbee sensors started becoming unresponsive... I kept removing and re-adding. Tried re-adding through my old WINK etc... issues with the devices appear to be related to distance but then even close ones also experience this.