New upgrade screwed zigbee wtf

Some new update just completely fucked up zigbee and after Rolling it back, it worked briefly and now won’t work again.. wtf..

If only there was some sort of text file that logged errors so you could see what is going on.

Restarting it does not work. It says initializing infinitely so I can click reload. This is very silly.

Ok I restored it to like two months ago. Apparently it needs to be taken offline and I just need to control it with meshcore. Somehow the meshcore integration is also not working so now that’s a thing I have to deal with

Now it’s failed again and it’s saying this

Logger: homeassistant.components.websocket_api.http.connection
Source: components/zha/helpers.py:1168
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 8:57:55 AM (2 occurrences)
Last logged: 8:57:55 AM

[2902224237808] Error handling message: Unknown error (unknown_error) bob from 192.168.1.207 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/153.0.0.0 Safari/537.36)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 26, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/zha/websocket_api.py", line 464, in websocket_get_device
    zha_gateway_proxy = get_zha_gateway_proxy(hass)
  File "/usr/src/homeassistant/homeassistant/components/zha/helpers.py", line 1168, in get_zha_gateway_proxy
    raise ValueError("No gateway object exists")
ValueError: No gateway object exists

If this does not sound too condescending to you. You will get a far more helpful response if you offer us some info like hardware, software versions etc.

read this.

If i was guessing it will be SD Card or USB power.

Updates swap in and out a very large percentage of your SD if you are using one, so it is the time you see the most failures because of that. All are blamed on the update code but if there is no community trend, (you are the only one in a search here) then it is likely hardware or something you just changed since the last reboot.
:frowning:
Based on many years of observation.