I’m running HAOS on a RPi4 and using SkyConnect, and it has been working fine.
Now I’ve tinkered a bit to hunt down high CPU usage, but must’ve changed something I shouldn’t have (and stupidly didn’t create a backup beforehand) as after the last reboot, no Zigbee2MQTT devices are available any longer.
I can control them fine through the Zigbee2MQTT interface, so it seems to be a problem on the MQTT broker side? I don’t see anything strange there neither though…
Well, not close enough it seems, as when I look again I can see this:
Logger: homeassistant.components.mqtt.util
Source: components/mqtt/util.py:78
integration: MQTT (documentation, issues)
First occurred: 2:09:47 PM (60 occurrences)
Last logged: 3:56:44 PM
Error talking to MQTT: The client is not currently connected.
So, for some reason no connection could be made? However now when I came back from an errand, the devices are available, meaning MQTT has been able to connect, without me changing anything.
It has actually taken some time for the Zigbee-devices to come online also after my latest reboots previously, but I haven’t really investigated it, as it’s been ~10-30minutes (ok, that’s quite long as well, but not 2h…). So it seems to be some underlying problem, and I’m quite it will be the same the next time I restart.
Any idea how I can investigate further? During the whole time, I could connect/see the devices using MQTT Explorer (and zigbee2mqtt) by the way, it was only HA that claimed they were unavailable.
(I currently have another issue with high CPU load, ~30%, which might or might not be related…)
