I am having some lost connection with my network, and I need to reboot it after a while.

[VitorFrost]

I am having some lost connection with my network, and I need to reboot it after a while. I couldn't find the source of the problem, no logs about anything related to this. But it seems that there is a problem with the zigbee or the database!

[0x28CB:1:0x0500]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
2:49:29 PM – (WARNING) Zigbee Home Automation - message first occurred at 2:49:28 PM and shows up 2 times
Zigbee channel 25 utilization is 91.06%!
2:48:39 PM – (WARNING) components/zha/core/gateway.py - message first occurred at 2:48:39 PM and shows up 2 times
Setup of input_number is taking over 10 seconds.
2:48:11 PM – (WARNING) runner.py - message first occurred at 2:48:11 PM and shows up 9 times
Ended unfinished session (id=11 from 2023-11-22 02:45:28.159329)
2:47:37 PM – (WARNING) Recorder
The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2:47:37 PM – (WARNING) Recorder

As you can see, at 2:49 the warning, and my last update on temperature happened at about 3am.

So i bet this is the main source of the problem. I've tried to implement the local tuya. I will uninstall it to make sure this isn't the problem source.

New logs after restar:

2023-11-22 15:18:02.345 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-11-22 15:18:02.356 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-11-22 15:18:38.578 WARNING (MainThread) [homeassistant.setup] Setup of zone is taking over 10 seconds.
2023-11-22 15:18:38.579 WARNING (MainThread) [homeassistant.setup] Setup of input_text is taking over 10 seconds.
2023-11-22 15:18:38.580 WARNING (MainThread) [homeassistant.setup] Setup of counter is taking over 10 seconds.
2023-11-22 15:18:48.322 WARNING (MainThread) [homeassistant.setup] Setup of input_boolean is taking over 10 seconds.
2023-11-22 15:18:48.323 WARNING (MainThread) [homeassistant.setup] Setup of input_number is taking over 10 seconds.
2023-11-22 15:18:48.323 WARNING (MainThread) [homeassistant.setup] Setup of timer is taking over 10 seconds.
2023-11-22 15:18:48.324 WARNING (MainThread) [homeassistant.setup] Setup of application_credentials is taking over 10 seconds.
2023-11-22 15:19:09.010 WARNING (MainThread) [zigpy.application] Zigbee channel 25 utilization is 91.06%!
2023-11-22 15:19:09.011 WARNING (MainThread) [zigpy.application] If you are having problems joining new devices, are missing sensor updates, or have issues keeping devices joined, ensure your coordinator is away from interference sources such as USB 3.0 devices, SSDs, WiFi routers, etc.

[darkxst]

2023-11-22 15:19:09.010 WARNING (MainThread) [zigpy.application] Zigbee channel 25 utilization is 91.06%!

There is interference on your zigbee channel, that is way too high. Check the energy scan in ZHA diagnostics report and choose a channel with lowest value.

Make sure you wifi channel is not overlapping Zigbee channel also!

[clfberlin]

Yes, I also had major interference problems once and had to physically move Home Assistant from my rack to another area of the house.

[github-actions[bot]]

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.