HA Keeps Rebooting after update to 2024.2.2

koburg commented 6 months ago

The problem

HA Keeps Rebooting after update to 2024.2.2 the version 2024.2.1 is working had to revert to this

What version of Home Assistant Core has the issue?

core-2024.2.2

What was the last working version of Home Assistant Core?

core-2024.2.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

the HA CORE

Link to integration documentation on our website

No response

Diagnostics information

HA keeps rebooting after upgrade and have changed nothing else revert back to core-2024.2.1 was the solution.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

joostlek commented 6 months ago

This issue has no information that could help us debug the issue. Please provide logs and anything you notice that's different on 2024.2.2.

amzaldua commented 6 months ago

I have the same issue here. I revert to 2014.2.1 version and fixed.

akfrederiksen commented 6 months ago

I'm not able to get any report because it happen as soon as it has been booted first time. Then it says no connection and rebooting in a endless loop so you have to be very fast if ever possible to get any logs.

foxy82 commented 6 months ago

How can we get logs if Home Assistant is constantly restarting? Is there a way to stop it restarting or getting it to save the logs before it crashes? Or any way to access the logs of a previous restart of the docker container?

joostlek commented 6 months ago

You usually have multiple log files in your config folder

foxy82 commented 6 months ago

There is nothing in the home-assistant.log.1 at the restart time that hasn't already repeated several times. Home Assistant stayed up for just under 9 minutes before crashing and restarting:

2024-02-20 17:33:01.919 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device XX:XX:XX:XX:XX:XX
2024-02-20 17:33:07.504 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device XX:XX:XX:XX:XX:XX
2024-02-20 17:33:12.396 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.235', 50853): Connection made to HASS Bridge
2024-02-20 17:33:13.919 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device XX:XX:XX:XX:XX:XX
2024-02-20 17:33:25.676 ERROR (MainThread) [custom_components.nest_protect] Unknown exception.
Traceback (most recent call last):
  File "/config/custom_components/nest_protect/__init__.py", line 80, in async_setup_entry
    auth = await client.get_access_token_from_cookies(issue_token, cookies)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/nest_protect/pynest/client.py", line 158, in get_access_token_from_cookies
    raise Exception(result["error"])
Exception: USER_LOGGED_OUT
2024-02-20 17:33:25.919 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device XX:XX:XX:XX:XX:XX
2024-02-20 17:33:37.919 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device XX:XX:XX:XX:XX:XX
2024-02-20 17:33:41.903 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device XX:XX:XX:XX:XX:XX
2024-02-20 17:33:49.921 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device XX:XX:XX:XX:XX:XX
2024-02-20 17:33:49.921 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device XX:XX:XX:XX:XX:XX
2024-02-20 17:33:56.672 WARNING (MainThread) [homeassistant.components.dnsip.sensor] Exception while resolving host: (1, 'DNS server returned answer with no data')

I know you will comment on the nest_protect custom integration - that message has repeated already but I've removed it on this run to see if that helps.

foxy82 commented 6 months ago

Without Nest the logs look like this stayed up just under 9 minutes again.

2024-02-20 17:39:55.512 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device YY:YY:YY:YY:YY:YY
2024-02-20 17:40:00.670 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device YY:YY:YY:YY:YY:YY
2024-02-20 17:40:12.671 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device YY:YY:YY:YY:YY:YY
2024-02-20 17:40:24.672 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device YY:YY:YY:YY:YY:YY
2024-02-20 17:40:29.436 INFO (MainThread) [pyhap.hap_protocol] ('192.168.1.235', 50855): Connection made to HASS Bridge
2024-02-20 17:40:34.996 WARNING (MainThread) [homeassistant.components.dnsip.sensor] Exception while resolving host: (1, 'DNS server returned answer with no data')
2024-02-20 17:40:36.673 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device YY:YY:YY:YY:YY:YY
2024-02-20 17:41:25.668 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device XX:XX:XX:XX:XX:XX
2024-02-20 17:41:36.677 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device XX:XX:XX:XX:XX:XX
2024-02-20 17:41:48.678 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device XX:XX:XX:XX:XX:XX
2024-02-20 17:42:00.678 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device XX:XX:XX:XX:XX:XX
2024-02-20 17:42:12.679 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device XX:XX:XX:XX:XX:XX

amzaldua commented 6 months ago

2024-02-20 17:47:34.861 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tarifa_20td 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
2024-02-20 17:47:34.861 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration bambu_lab 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
2024-02-20 17:47:34.862 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration daikin_residential 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
2024-02-20 17:47:34.862 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration mjpeg_timelapse 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
2024-02-20 17:47:34.863 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration aemet 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
2024-02-20 17:47:34.863 ERROR (SyncWorker_0) [homeassistant.loader] The custom integration 'aemet' does not have a version key in the manifest file and was blocked from loading. See https://developers.home-assistant.io/blog/2021/01/29/custom-integration-changes#versions for more details
2024-02-20 17:47:34.863 WARNING (SyncWorker_0) [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
2024-02-20 17:47:34.864 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration minecraft_server 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
2024-02-20 17:47:34.864 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration solaredge_modbus 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
2024-02-20 17:47:34.864 WARNING (SyncWorker_0) [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
2024-02-20 17:47:34.865 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration powercalc 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
2024-02-20 17:47:34.865 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration scheduler 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
2024-02-20 17:47:34.865 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration smartthinq_sensors 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
2024-02-20 17:47:34.866 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman 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
2024-02-20 17:47:34.866 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration solaredge_modbus_multi 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
2024-02-20 17:47:34.867 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration frigate 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
2024-02-20 17:47:34.867 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration helium_solana 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
2024-02-20 17:47:34.867 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration cupra_we_connect 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
2024-02-20 17:47:34.868 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration irrigation_unlimited 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
2024-02-20 17:47:34.868 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration entity_controller 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
2024-02-20 17:47:34.868 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration balance_neto 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
2024-02-20 17:47:53.216 WARNING (MainThread) [homeassistant.components.climate.const] CURRENT_HVAC_HEAT was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.HEATING instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.219 WARNING (MainThread) [homeassistant.components.climate.const] CURRENT_HVAC_IDLE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.IDLE instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.222 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_AUTO was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.AUTO instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.225 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_HEAT was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.HEAT instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.228 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_OFF was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.OFF instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.230 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_PRESET_MODE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.PRESET_MODE instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.233 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_TARGET_TEMPERATURE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.TARGET_TEMPERATURE instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.236 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_TARGET_TEMPERATURE_RANGE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.TARGET_TEMPERATURE_RANGE instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.239 WARNING (MainThread) [homeassistant.const] TEMP_CELSIUS was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.241 WARNING (MainThread) [homeassistant.const] TEMP_FAHRENHEIT was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.FAHRENHEIT instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.247 WARNING (MainThread) [homeassistant.components.cover] SUPPORT_CLOSE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.CLOSE instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.250 WARNING (MainThread) [homeassistant.components.cover] SUPPORT_OPEN was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.OPEN instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.253 WARNING (MainThread) [homeassistant.components.cover] SUPPORT_SET_POSITION was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.SET_POSITION instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.256 WARNING (MainThread) [homeassistant.components.cover] SUPPORT_STOP was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.STOP instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.258 WARNING (MainThread) [homeassistant.components.cover] SUPPORT_CLOSE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.CLOSE instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.261 WARNING (MainThread) [homeassistant.components.cover] SUPPORT_OPEN was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.OPEN instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.264 WARNING (MainThread) [homeassistant.components.cover] SUPPORT_SET_POSITION was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.SET_POSITION instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.267 WARNING (MainThread) [homeassistant.components.cover] SUPPORT_STOP was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.STOP instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.273 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_DIRECTION was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.DIRECTION instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.275 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_OSCILLATE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.OSCILLATE instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.278 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_SET_SPEED was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.SET_SPEED instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.281 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_DIRECTION was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.DIRECTION instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.284 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_OSCILLATE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.OSCILLATE instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:53.286 WARNING (MainThread) [homeassistant.components.fan] SUPPORT_SET_SPEED was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.SET_SPEED instead, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-02-20 17:47:55.968 WARNING (MainThread) [homeassistant.components.sensor] STATE_CLASS_TOTAL_INCREASING was used from balance_neto, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.TOTAL_INCREASING instead, please create a bug report at https://github.com/MiguelAngelLV/balance_neto/issues
2024-02-20 17:47:55.972 WARNING (MainThread) [homeassistant.components.sensor] DEVICE_CLASS_ENERGY was used from balance_neto, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.ENERGY instead, please create a bug report at https://github.com/MiguelAngelLV/balance_neto/issues
2024-02-20 17:47:55.975 WARNING (MainThread) [homeassistant.components.sensor] STATE_CLASS_TOTAL_INCREASING was used from balance_neto, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.TOTAL_INCREASING instead, please create a bug report at https://github.com/MiguelAngelLV/balance_neto/issues
2024-02-20 17:47:55.979 WARNING (MainThread) [homeassistant.components.sensor] DEVICE_CLASS_ENERGY was used from balance_neto, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.ENERGY instead, please create a bug report at https://github.com/MiguelAngelLV/balance_neto/issues
2024-02-20 17:47:58.875 ERROR (MainThread) [homeassistant.components.forecast_solar] Unexpected error fetching forecast_solar data: Rate limit for API calls reached. (error 429)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 313, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/forecast_solar/coordinator.py", line 67, in _async_update_data
    return await self.forecast.estimate()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 156, in estimate
    data = await self._request(
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 125, in _request
    raise ForecastSolarRatelimit(data["message"])
forecast_solar.exceptions.ForecastSolarRatelimit: Rate limit for API calls reached. (error 429)
2024-02-20 17:47:59.022 ERROR (MainThread) [homeassistant.components.forecast_solar] Unexpected error fetching forecast_solar data: Rate limit for API calls reached. (error 429)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 313, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/forecast_solar/coordinator.py", line 67, in _async_update_data
    return await self.forecast.estimate()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 156, in estimate
    data = await self._request(
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 125, in _request
    raise ForecastSolarRatelimit(data["message"])
forecast_solar.exceptions.ForecastSolarRatelimit: Rate limit for API calls reached. (error 429)
2024-02-20 17:47:59.102 ERROR (MainThread) [homeassistant.components.forecast_solar] Unexpected error fetching forecast_solar data: Rate limit for API calls reached. (error 429)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 313, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/forecast_solar/coordinator.py", line 67, in _async_update_data
    return await self.forecast.estimate()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 156, in estimate
    data = await self._request(
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 125, in _request
    raise ForecastSolarRatelimit(data["message"])
forecast_solar.exceptions.ForecastSolarRatelimit: Rate limit for API calls reached. (error 429)
2024-02-20 17:48:03.698 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esp32-d @ 192.168.0.151: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.151', port=6053))]: [Errno 111] Connect call failed ('192.168.0.151', 6053) (SocketAPIError)
2024-02-20 17:48:06.914 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esp32-c3 @ 192.168.0.155: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.155', port=6053))]: [Errno 113] Connect call failed ('192.168.0.155', 6053) (SocketAPIError)
2024-02-20 17:48:06.914 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esp32-c6 @ 192.168.0.154: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.154', port=6053))]: [Errno 113] Connect call failed ('192.168.0.154', 6053) (SocketAPIError)
2024-02-20 17:48:06.914 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esp32-wrover @ 192.168.0.153: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.153', port=6053))]: [Errno 113] Connect call failed ('192.168.0.153', 6053) (SocketAPIError)
2024-02-20 17:48:06.914 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esp32-u @ 192.168.0.152: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.152', port=6053))]: [Errno 113] Connect call failed ('192.168.0.152', 6053) (SocketAPIError)
2024-02-20 17:48:07.369 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esp32-relay-x8-02 @ 192.168.0.157: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.157', port=6053))]: [Errno 113] Connect call failed ('192.168.0.157', 6053) (SocketAPIError)
2024-02-20 17:48:07.369 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esp32-relay-x8-01 @ 192.168.0.156: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.156', port=6053))]: [Errno 113] Connect call failed ('192.168.0.156', 6053) (SocketAPIError)
2024-02-20 17:48:09.659 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for device_tracker.5d_37_b5_51_e3_50 (<class 'homeassistant.components.device_tracker.legacy.Device'>) took 0.510 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue
2024-02-20 17:48:10.177 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140481174944576] Alvaro Martinez from 192.168.0.19 (Home Assistant/2024.1 (io.robbie.HomeAssistant; build:2024.535; macOS 14.2.1)): Client unable to keep up with pending messages. Reached 4096 pending messages. The system's load is too high or an integration is misbehaving; Last message was: b'{"type":"event","event":{"event_type":"state_changed","data":{"entity_id":"device_tracker.77_fb_a0_b4_aa_eb","old_state":null,"new_state":{"entity_id":"device_tracker.77_fb_a0_b4_aa_eb","state":"not_home","attributes":{"source_type":null,"friendly_name":"77:FB:A0:B4:AA:EB"},"last_changed":"2024-02-20T17:48:10.177186+00:00","last_updated":"2024-02-20T17:48:10.177186+00:00","context":{"id":"01HQ3T3Q21RGDCR7JD46QJCDRH","parent_id":null,"user_id":null}}},"origin":"LOCAL","time_fired":"2024-02-20T17:48:10.177186+00:00","context":{"id":"01HQ3T3Q21RGDCR7JD46QJCDRH","parent_id":null,"user_id":null}},"id":9129}'
2024-02-20 17:48:10.177 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140481174929600] Nora Martinez from 192.168.0.13 (Home Assistant/2024.1 (io.robbie.HomeAssistant; build:2024.535; macOS 14.3.0)): Client unable to keep up with pending messages. Reached 4096 pending messages. The system's load is too high or an integration is misbehaving; Last message was: b'{"type":"event","event":{"event_type":"state_changed","data":{"entity_id":"device_tracker.77_fb_a0_b4_aa_eb","old_state":null,"new_state":{"entity_id":"device_tracker.77_fb_a0_b4_aa_eb","state":"not_home","attributes":{"source_type":null,"friendly_name":"77:FB:A0:B4:AA:EB"},"last_changed":"2024-02-20T17:48:10.177186+00:00","last_updated":"2024-02-20T17:48:10.177186+00:00","context":{"id":"01HQ3T3Q21RGDCR7JD46QJCDRH","parent_id":null,"user_id":null}}},"origin":"LOCAL","time_fired":"2024-02-20T17:48:10.177186+00:00","context":{"id":"01HQ3T3Q21RGDCR7JD46QJCDRH","parent_id":null,"user_id":null}},"id":929}'
2024-02-20 17:48:10.178 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140481174924864] Alvaro Martinez from 192.168.0.19 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Home Assistant/2024.1 (io.robbie.HomeAssistant; build:2024.535; macOS 14.2.1) Mobile/HomeAssistant, like Safari): Client unable to keep up with pending messages. Reached 4096 pending messages. The system's load is too high or an integration is misbehaving; Last message was: b'{"type":"event","event":{"a":{"device_tracker.5c_49_7c_07_16_0f":{"s":"not_home","a":{"source_type":null,"friendly_name":"5C:49:7C:07:16:0F"},"c":"01HQ3T3Q22K2QCP62QBV6N5V1W","lc":1708451290.178694}}},"id":3}'
2024-02-20 17:48:35.780 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_TEMPERATURE was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.TEMPERATURE instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:35.785 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_HUMIDITY was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.HUMIDITY instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:35.789 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_ENERGY was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.ENERGY instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:35.793 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_SIGNAL_STRENGTH was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.SIGNAL_STRENGTH instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:35.797 WARNING (MainThread) [homeassistant.const] ENERGY_KILO_WATT_HOUR was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfEnergy.KILO_WATT_HOUR instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:35.801 WARNING (MainThread) [homeassistant.const] TEMP_CELSIUS was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:35.804 WARNING (MainThread) [py.warnings] /config/custom_components/daikin_residential/daikin_api.py:314: SyntaxWarning: invalid escape sequence '\d'
  regex = "(\d+-\d-\d+)"

2024-02-20 17:48:35.935 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_COOL was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.COOL instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:35.940 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_DRY was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.DRY instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:35.944 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_FAN_ONLY was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.FAN_ONLY instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:35.948 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_HEAT was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.HEAT instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:35.953 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_HEAT_COOL was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.HEAT_COOL instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:35.957 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_OFF was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.OFF instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.693 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_COOL was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.COOL instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.697 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_DRY was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.DRY instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.702 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_FAN_ONLY was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.FAN_ONLY instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.706 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_HEAT was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.HEAT instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.710 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_HEAT_COOL was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.HEAT_COOL instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.715 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_OFF was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.OFF instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.720 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_TARGET_TEMPERATURE was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.TARGET_TEMPERATURE instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.724 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_FAN_MODE was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.FAN_MODE instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.729 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_PRESET_MODE was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.PRESET_MODE instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.733 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_SWING_MODE was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.SWING_MODE instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.738 WARNING (MainThread) [homeassistant.const] TEMP_CELSIUS was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.746 WARNING (MainThread) [homeassistant.components.sensor] STATE_CLASS_MEASUREMENT was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.MEASUREMENT instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.751 WARNING (MainThread) [homeassistant.components.sensor] STATE_CLASS_TOTAL_INCREASING was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.TOTAL_INCREASING instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.763 WARNING (MainThread) [homeassistant.components.sensor] STATE_CLASS_MEASUREMENT was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.MEASUREMENT instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.770 WARNING (MainThread) [homeassistant.components.sensor] STATE_CLASS_TOTAL_INCREASING was used from daikin_residential, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.TOTAL_INCREASING instead, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.779 WARNING (MainThread) [homeassistant.helpers.entity] Entity None (<class 'custom_components.daikin_residential.climate.DaikinClimate'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <ClimateEntityFeature.TARGET_TEMPERATURE|FAN_MODE|PRESET_MODE|SWING_MODE: 57>, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-02-20 17:48:36.779 WARNING (MainThread) [homeassistant.components.climate] Entity None (<class 'custom_components.daikin_residential.climate.DaikinClimate'>) does not set ClimateEntityFeature.TURN_OFF but implements the turn_off method. Please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.779 WARNING (MainThread) [homeassistant.components.climate] Entity None (<class 'custom_components.daikin_residential.climate.DaikinClimate'>) does not set ClimateEntityFeature.TURN_ON but implements the turn_on method. Please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.780 WARNING (MainThread) [homeassistant.components.climate] Entity None (<class 'custom_components.daikin_residential.climate.DaikinClimate'>) implements HVACMode(s): off, fan_only, heat, cool, heat_cool, dry and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.780 WARNING (MainThread) [homeassistant.helpers.entity] Entity None (<class 'custom_components.daikin_residential.climate.DaikinClimate'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <ClimateEntityFeature.TARGET_TEMPERATURE|FAN_MODE|PRESET_MODE|SWING_MODE: 57>, please create a bug report at https://github.com/rospogrigio/daikin_residential/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-02-20 17:48:36.780 WARNING (MainThread) [homeassistant.components.climate] Entity None (<class 'custom_components.daikin_residential.climate.DaikinClimate'>) does not set ClimateEntityFeature.TURN_OFF but implements the turn_off method. Please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.780 WARNING (MainThread) [homeassistant.components.climate] Entity None (<class 'custom_components.daikin_residential.climate.DaikinClimate'>) does not set ClimateEntityFeature.TURN_ON but implements the turn_on method. Please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:36.780 WARNING (MainThread) [homeassistant.components.climate] Entity None (<class 'custom_components.daikin_residential.climate.DaikinClimate'>) implements HVACMode(s): off, fan_only, heat, cool, heat_cool, dry and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/rospogrigio/daikin_residential/issues
2024-02-20 17:48:52.243 ERROR (MainThread) [homeassistant.components.forecast_solar] Unexpected error fetching forecast_solar data: Rate limit for API calls reached. (error 429)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 313, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/forecast_solar/coordinator.py", line 67, in _async_update_data
    return await self.forecast.estimate()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 156, in estimate
    data = await self._request(
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 125, in _request
    raise ForecastSolarRatelimit(data["message"])
forecast_solar.exceptions.ForecastSolarRatelimit: Rate limit for API calls reached. (error 429)
2024-02-20 17:48:52.246 ERROR (MainThread) [homeassistant.components.forecast_solar] Unexpected error fetching forecast_solar data: Rate limit for API calls reached. (error 429)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 313, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/forecast_solar/coordinator.py", line 67, in _async_update_data
    return await self.forecast.estimate()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 156, in estimate
    data = await self._request(
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 125, in _request
    raise ForecastSolarRatelimit(data["message"])
forecast_solar.exceptions.ForecastSolarRatelimit: Rate limit for API calls reached. (error 429)
2024-02-20 17:48:53.065 ERROR (MainThread) [homeassistant.components.forecast_solar] Unexpected error fetching forecast_solar data: Rate limit for API calls reached. (error 429)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 313, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/forecast_solar/coordinator.py", line 67, in _async_update_data
    return await self.forecast.estimate()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 156, in estimate
    data = await self._request(
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 125, in _request
    raise ForecastSolarRatelimit(data["message"])
forecast_solar.exceptions.ForecastSolarRatelimit: Rate limit for API calls reached. (error 429)
2024-02-20 17:49:02.683 ERROR (MainThread) [homeassistant.components.forecast_solar] Unexpected error fetching forecast_solar data: Rate limit for API calls reached. (error 429)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 313, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/forecast_solar/coordinator.py", line 67, in _async_update_data
    return await self.forecast.estimate()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 156, in estimate
    data = await self._request(
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 125, in _request
    raise ForecastSolarRatelimit(data["message"])
forecast_solar.exceptions.ForecastSolarRatelimit: Rate limit for API calls reached. (error 429)
2024-02-20 17:49:02.745 ERROR (MainThread) [homeassistant.components.forecast_solar] Unexpected error fetching forecast_solar data: Rate limit for API calls reached. (error 429)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 313, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/forecast_solar/coordinator.py", line 67, in _async_update_data
    return await self.forecast.estimate()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 156, in estimate
    data = await self._request(
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 125, in _request
    raise ForecastSolarRatelimit(data["message"])
forecast_solar.exceptions.ForecastSolarRatelimit: Rate limit for API calls reached. (error 429)
2024-02-20 17:49:03.440 ERROR (MainThread) [homeassistant.components.forecast_solar] Unexpected error fetching forecast_solar data: Rate limit for API calls reached. (error 429)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 313, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/forecast_solar/coordinator.py", line 67, in _async_update_data
    return await self.forecast.estimate()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 156, in estimate
    data = await self._request(
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/forecast_solar/__init__.py", line 125, in _request
    raise ForecastSolarRatelimit(data["message"])
forecast_solar.exceptions.ForecastSolarRatelimit: Rate limit for API calls reached. (error 429)

amzaldua commented 6 months ago

@joostlek, what do you need? I have sent you the log in the previous comment immediately after restoring to 20114.2.1.

joostlek commented 6 months ago

Wait can you tell me what file this is?

If this is everything, please also check the supervisor logs

foxy82 commented 6 months ago

Stayed up just under 2 mins in safe mode:

2024-02-20 17:55:41.834 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device 
2024-02-20 17:55:41.834 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device 
2024-02-20 17:55:41.834 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device 
2024-02-20 17:55:41.834 INFO (MainThread) [homeassistant.components.bluetooth_le_tracker.device_tracker] Discovered Bluetooth LE device 
2024-02-20 17:55:44.862 WARNING (MainThread) [androidtv.adb_manager.adb_manager_async] Couldn't connect to 192.168.1.47:5555.  TcpTimeoutException: Connecting to 192.168.1.47:5555 timed out (1.
0 seconds)
2024-02-20 17:55:45.142 WARNING (MainThread) [androidtv.adb_manager.adb_manager_async] Couldn't connect to 192.168.1.31:5555.  TcpTimeoutException: Connecting to 192.168.1.31:5555 timed out (1.
0 seconds)
2024-02-20 17:55:46.460 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid or incomplete color value '{'brightness': 254, 'color_mode': 'xy', 'linkquality': 255, 'po
wer_on_behavior': None, 'state': 'OFF', 'update': {'installed_version': -1, 'latest_version': -1, 'state': None}, 'update_available': None}' received for entity light.lower_loft
2024-02-20 17:55:46.506 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid or incomplete color value '{'color_mode': 'xy', 'color_options': None, 'linkquality': 92,
'power_on_behavior': None, 'state': 'OFF', 'update': {'installed_version': 587806257, 'latest_version': 587806257, 'state': 'idle'}, 'update_available': None}' received for entity light.product
_cupboard
2024-02-20 17:55:46.513 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid or incomplete color value '{'color_mode': 'xy', 'color_options': None, 'linkquality': 120,
 'power_on_behavior': None, 'state': 'OFF', 'update': {'installed_version': 587806257, 'latest_version': 587806257, 'state': 'idle'}, 'update_available': None}' received for entity light.upper_
loft_2
2024-02-20 17:55:46.527 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid or incomplete color value '{'color_mode': 'xy', 'linkquality': 100, 'power_on_behavior': N
one, 'state': 'OFF'}' received for entity light.studio_left_front
2024-02-20 17:55:46.529 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid or incomplete color value '{'color_mode': 'xy', 'linkquality': 100, 'power_on_behavior': N
one, 'state': 'OFF'}' received for entity light.studio_left_back
2024-02-20 17:55:46.531 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid or incomplete color value '{'color_mode': 'xy', 'linkquality': 100, 'power_on_behavior': N
one, 'state': 'OFF'}' received for entity light.studio_back_right
2024-02-20 17:55:46.532 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid or incomplete color value '{'color_mode': 'xy', 'linkquality': 96, 'power_on_behavior': No
ne, 'state': 'OFF'}' received for entity light.studio_back_left
2024-02-20 17:55:46.559 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid or incomplete color value '{'color_mode': 'xy', 'state': 'OFF'}' received for entity light
.upper_loft_zigbee_group
2024-02-20 17:55:46.563 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid or incomplete color value '{'color_mode': 'xy', 'state': 'OFF'}' received for entity light
.lower_loft_zigbee_group

What is the best way to access the supervisor logs - there are more logs but it's really difficult to sanitise them for an open forum like this.

joostlek commented 6 months ago

Supervisor logs via HA itself. Maybe you can come on discord and have a chat in the support area to dig a bit deeper, after I'm done cooking I can also pitch in

foxy82 commented 6 months ago

Supervisor logs:

[32m24-02-20 17:48:33 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon[0m
[32m24-02-20 17:48:34 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize[0m
[32m24-02-20 17:48:34 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered[0m
[32m24-02-20 17:48:34 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running[0m
[32m24-02-20 17:48:34 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running[0m
[32m24-02-20 17:48:37 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running[0m
[32m24-02-20 17:52:13 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 257[0m
[32m24-02-20 17:52:13 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed[0m
[33m24-02-20 17:52:13 WARNING (MainThread) [supervisor.homeassistant.websocket] Connection is closed[0m
[32m24-02-20 17:52:13 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 257[0m
[32m24-02-20 17:52:13 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 257[0m
[32m24-02-20 17:52:13 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed[0m
[32m24-02-20 17:52:13 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed[0m
[33m24-02-20 17:52:16 WARNING (MainThread) [supervisor.homeassistant.core] Watchdog found Home Assistant failed, restarting...[0m
[32m24-02-20 17:52:16 INFO (SyncWorker_3) [supervisor.docker.manager] Starting homeassistant[0m
[32m24-02-20 17:52:16 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready[0m
[32m24-02-20 17:52:22 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to NOT_RUNNING[0m
[32m24-02-20 17:52:25 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running[0m
[32m24-02-20 17:52:25 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete[0m
[33m24-02-20 17:52:26 WARNING (MainThread) [supervisor.addons.options] Option 'keytype' does not exist in the schema for Let's Encrypt (core_letsencrypt)[0m
[32m24-02-20 17:53:07 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to RUNNING[0m
[32m24-02-20 17:53:07 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance[0m
[32m24-02-20 17:53:07 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize[0m
[32m24-02-20 17:53:07 INFO (MainThread) [supervisor.api.proxy] WebSocket access from local_heos_link_bridge[0m
[32m24-02-20 17:53:07 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize[0m
[32m24-02-20 17:53:07 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon[0m
[32m24-02-20 17:53:07 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize[0m
[32m24-02-20 17:53:07 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered[0m
[32m24-02-20 17:53:11 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running[0m
[32m24-02-20 17:53:11 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running[0m
[32m24-02-20 17:53:11 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running[0m
[32m24-02-20 17:53:22 INFO (SyncWorker_7) [supervisor.docker.manager] Restarting homeassistant[0m
[32m24-02-20 17:53:23 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 257[0m
[32m24-02-20 17:53:23 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed[0m
[33m24-02-20 17:53:23 WARNING (MainThread) [supervisor.homeassistant.websocket] Connection is closed[0m
[32m24-02-20 17:53:23 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 257[0m
[32m24-02-20 17:53:23 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 257[0m
[32m24-02-20 17:53:23 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed[0m
[32m24-02-20 17:53:23 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed[0m
[32m24-02-20 17:54:24 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready[0m
[32m24-02-20 17:54:33 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to NOT_RUNNING[0m
[32m24-02-20 17:54:33 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running[0m
[32m24-02-20 17:54:33 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete[0m
[33m24-02-20 17:54:33 WARNING (MainThread) [supervisor.addons.options] Option 'keytype' does not exist in the schema for Let's Encrypt (core_letsencrypt)[0m
[32m24-02-20 17:54:41 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'homeassistant'[0m
[32m24-02-20 17:54:42 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache[0m
[32m24-02-20 17:55:13 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize[0m
[32m24-02-20 17:55:13 INFO (MainThread) [supervisor.api.proxy] WebSocket access from local_heos_link_bridge[0m
[32m24-02-20 17:55:15 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to RUNNING[0m
[32m24-02-20 17:55:15 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance[0m
[32m24-02-20 17:55:15 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize[0m
[32m24-02-20 17:55:15 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered[0m
[32m24-02-20 17:55:15 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize[0m
[32m24-02-20 17:55:15 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon[0m
[32m24-02-20 17:55:16 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running[0m
[32m24-02-20 17:55:16 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running[0m
[32m24-02-20 17:55:16 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running[0m
[32m24-02-20 17:55:52 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 257[0m
[33m24-02-20 17:55:52 WARNING (MainThread) [supervisor.homeassistant.websocket] Connection is closed[0m
[32m24-02-20 17:55:52 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed[0m
[32m24-02-20 17:55:52 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 257[0m
[32m24-02-20 17:55:52 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 257[0m
[32m24-02-20 17:55:52 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed[0m
[32m24-02-20 17:55:52 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed[0m
[33m24-02-20 17:55:56 WARNING (MainThread) [supervisor.homeassistant.core] Watchdog found Home Assistant failed, restarting...[0m
[32m24-02-20 17:55:56 INFO (SyncWorker_3) [supervisor.docker.manager] Starting homeassistant[0m
[32m24-02-20 17:55:56 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready[0m
[32m24-02-20 17:56:01 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to NOT_RUNNING[0m
[32m24-02-20 17:56:05 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running[0m
[32m24-02-20 17:56:05 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete[0m
[33m24-02-20 17:56:06 WARNING (MainThread) [supervisor.addons.options] Option 'keytype' does not exist in the schema for Let's Encrypt (core_letsencrypt)[0m
[32m24-02-20 17:56:46 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to RUNNING[0m
[32m24-02-20 17:56:46 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance[0m
[32m24-02-20 17:56:46 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize[0m
[32m24-02-20 17:56:46 INFO (MainThread) [supervisor.api.proxy] WebSocket access from local_heos_link_bridge[0m
[32m24-02-20 17:56:46 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize[0m
[32m24-02-20 17:56:46 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon[0m
[32m24-02-20 17:56:50 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running[0m
[32m24-02-20 17:56:50 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running[0m
[32m24-02-20 17:56:51 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize[0m
[32m24-02-20 17:56:51 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered[0m
[32m24-02-20 17:56:51 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running[0m
[32m24-02-20 17:59:47 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token[0m
[33m24-02-20 18:01:05 WARNING (MainThread) [supervisor.addons.options] Option 'keytype' does not exist in the schema for Let's Encrypt (core_letsencrypt)[0m
[32m24-02-20 18:02:14 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 257[0m
[32m24-02-20 18:02:14 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed[0m
[32m24-02-20 18:02:14 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 257[0m
[32m24-02-20 18:02:14 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed[0m
[33m24-02-20 18:02:14 WARNING (MainThread) [supervisor.homeassistant.websocket] Connection is closed[0m
[32m24-02-20 18:02:14 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 257[0m
[32m24-02-20 18:02:14 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed[0m
[33m24-02-20 18:02:18 WARNING (MainThread) [supervisor.homeassistant.core] Watchdog found Home Assistant failed, restarting...[0m
[32m24-02-20 18:02:18 INFO (SyncWorker_7) [supervisor.docker.manager] Starting homeassistant[0m
[32m24-02-20 18:02:18 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready[0m
[32m24-02-20 18:02:23 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to NOT_RUNNING[0m
[32m24-02-20 18:02:27 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running[0m
[32m24-02-20 18:02:27 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete[0m
[33m24-02-20 18:02:28 WARNING (MainThread) [supervisor.addons.options] Option 'keytype' does not exist in the schema for Let's Encrypt (core_letsencrypt)[0m
[32m24-02-20 18:02:36 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'homeassistant'[0m
[32m24-02-20 18:02:37 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache[0m

Nothing of interest just the crashes - as it is now 6pm here I'm going to have to roll back for the day.

amzaldua commented 6 months ago

Wait can you tell me what file this is?

If this is everything, please also check the supervisor logs

It is the home-assistant.log file from the config folder. If you need, I can reinstall the 2024.2.2 version, but I need to know what I have to provide you with. But give me the instructions as if for a 6-year-old child. ;)

joostlek commented 6 months ago

There's might also be a home-assistant.log.1 or log.fault or something like that, could you see that one?

amzaldua commented 6 months ago

There's might also be a home-assistant.log.1 or log.fault or something like that, could you see that one?

All log files in config folder: https://www.dropbox.com/scl/fi/hms4flwh140oq23qb9jur/Archivo.zip?rlkey=3blgkwqebzp7jku2t09y60qov&dl=0

dermm commented 6 months ago

Hi,

i've the same reboot issue. Tested with 2024.2.2 and 2024.2.3 Logs atached. home-assistant.log home-assistant.log.1.txt home-assistant.log.fault.txt

I'dont see any errors. Boot in safe mode and deactivating many devices and integrations do not help.

Any suggestions? I can provide more if you tell me what is needed.

Best

DanStasiak commented 6 months ago

The problem still exists; skipping 2024.2.2 and installing 2024.2.3 doesn’t help. The consent restarting still exists.

By the way. the only help I found to reset my system to working order is in the CLI to do a “su restart” command and then repeat a “core update --version 2024.2.1” command until “Processing…” shows.

I guess we have to wait until the problem is addressed and fixed. I wonder if the 2024.3 Update will remedy the problem.

foxy82 commented 6 months ago

There isn't much info here to debug it though. Although the fault log that was just uploaded has a python segmentation fault at the top so possibly an issue with the python version bump?

I don't know anything about the fault log. It is very long though. I'll try to upgrade and capture my fault log this weekend.

Human commented 6 months ago

Since the logs aren't providing much insight, and since this is evidently not affecting all users, perhaps it comes down to integrations. Shall we compare ours to see if we find any overlap, maybe some uncommon integration?

I'll start with mine (HACS-related integrations in bold):

Bluetooth Brother Printer DLNA Digital Media Renderer ESPHome Google Cast HACS Hyundai / Kia Connect iBeacon Tracker INKBIRD Internet Printing Protocol (IPP) IQVIA National Weather Service (NWS) Network UPS Tools (NUT) OctoPrin OwnTracks pfSense Ping (ICMP) Roku SMA Solar Speedtest.net Sun Synology DSM Tesla Wall Connector UniFi Network Uptime Xiaomi Miio Xiaomi Miiot Auto Z-Wave

crazymikefra commented 6 months ago

Same here. Versions 2024.2.2 and 2024.2.3 restart on watchdog by supervisor.

I tried to switch on failsafe mode but it is the same.

I suspect one thing a bug with our hardwares/configurations. Here is my setup :

Processor : Inter core I3-6100T
OS : HA OS 11.5 - Generic x86-64
Supervisor : 2024.02.0

Can others can share setup informations ?

crazymikefra commented 6 months ago

In my logs, i see this recurring message with the new versions : [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 257

Is someone know from where it can come ?

I see it each time ha core restarts.

foxy82 commented 6 months ago

Are any 2024.2.x versions working for people? I originally went from 2024.1. straight to 2024.2.2 so had assume it was the upgrade to 2024.2 but looking at the report it started happening at 2024.2.2. I'm trying 2024.2.0 now.

DanStasiak commented 6 months ago

Hardware Intel NUC OS: HA OS 11.5 - Generic x86-64 Supervisor 2024.02.0 Core (working): 2024.2.1 Frontend 20240207.1

HACS Integrations systemd notifier Cryptoinfo Passive BLE monitor integration HACS Watchman Frigate SENEC.Home V2.x/V3/V4 Systems Alexa Media Player Sonoff LAN Presence Simulation Node-RED Companion ShellyForHass (Shelly integration) Battery Notes Dual Smart Thermostat XMR Pool Statistics Local Tuya Spook Not your homie Remote Home-Assistant Yahoo Finance Monitor Docker Deutscher Wetterdienst Senec solar system sensor Balboa Spa Client Reolink Discovery Satellite Tracker (N2YO) iCloud3 v3, Development Version

Add-ons Advanced SSH & Web Terminal DeepStack DOODS DOODS2-amd64 Double Take ESPHome Frigate MariaDB Mosquitto broker Node-RED openWakeWord Piper Ring-MQTT with Video Streaming Samba share Silicon Labs Multiprotocol Studio Code Server Whisper Z-Wave JS UI zabbix-agent2 Zigbee2MQTT

Rikkie80 commented 6 months ago

I only have Spook and LocalTuya installed. The other integrations @DanStasiak had installed are not on my system. Add-ons are Whisper, Studio Code server, Advanced SSH Terminal, Samba share, Piper and Whisper.

crazymikefra commented 6 months ago

Are any 2024.2.x versions working for people? I originally went from 2024.1. straight to 2024.2.2 so had assume it was the upgrade to 2024.2 but looking at the report it started happening at 2024.2.2. I'm trying 2024.2.0 now.

For me, and as i see with other peoples, problems started with 2024.2.1. I have seen an upgrade to python 3.12 but can't remember on which version. Someone remembers ?

On my side, i try to desactivate one by one every integration (ha official also). At this time, the last integration stopped is MQTT.

Rest activated integrations :

amzaldua commented 6 months ago

Processor : Intel Celeron 5105 OS : HA OS 11.5 - Generic x86-64 Supervisor : 2024.02.1

crazymikefra commented 6 months ago

End of my session :

I have a doubt versus bluetooth but not proven
I ended with those remaining components :
- Mobile App
- Home Assistant Supervisor
- System Monitor
- UpTime
I've had a fault with xiamo cloud map extractor which is not visible with the front (only yaml) so i disabled it

crazymikefra commented 6 months ago

Bluetooth seems the culpript on my side, system is stable since 25 minutes without it. I see a future update of bluez coming with next version of HAOS (https://github.com/home-assistant/operating-system/releases)

Other impacted, can you try disable the bluetooth integration to confirm ?

If it is really that part which is malfuntionning, it is not a real surprise. Since last year, there were real difficulties with bluetooth. And, as i see, the pybluez is not really maintained since 2019 (https://github.com/pybluez/pybluez) so someone should check that library one day.

amzaldua commented 6 months ago

I do not have Bluetooth physically on my server, but I use external ESP32 devices as gateways...

crazymikefra commented 6 months ago

I do not have Bluetooth physically on my server, but I use external ESP32 devices as gateways...

Have you tried disabling the bluetooth integration ? Also with esp32 it ends inside the bluetooth integration if i say right. Let's give it a try.

When i say "bluetooth integration" , i speak about then entry inside the integration page not inside the parameters page.

Human commented 6 months ago

I disabled the Bluetooth integration in 2024.2.2, but the web UI still says that it's starting Bluetooth. :shrug:

Once it does come up, and I'm able to see the integrations screen, Bluetooth isn't there. But 2024.2.2 continues to restart itself over and over again. My integrations dashboard is filled with "initializing" and "not loaded" and "failed setup, will retry"

Human commented 6 months ago

@DanStasiak Looks like we overlap on HACS, ESPHome, and ZWave, all of which seem popular enough to be unlikely causes, but we should at least consider them.

amzaldua commented 6 months ago

I don't have ZWave, so the problem probably isn't there. I have Frigate. Does anybody else have Frigate?

Rikkie80 commented 6 months ago

I don't

amzaldua commented 6 months ago

Okay. Probably the best way to narrow down the problem is to install version 2024.2.3 and execute it in secure mode, then start all services one by one.

Human commented 6 months ago

I had three ESPHome devices, so I disabled all of those and tried 2024.2.2 again. After it started up, it seems to have avoided restarting itself continuously. :crossed_fingers: @DanStasiak Could you disable your ESPHome devices and try the same?

EDIT: 3 hours later, it's still stable. Bluetooth and ESPHome integrations are disabled.

Human commented 6 months ago

My ESPHome devices were all flashed with the latest firmware: ESPHome version 2024.2.0 compiled on Feb 21 2024, 12:38:09

Human commented 6 months ago

@amzaldua I infer that you're also using ESPHome. Could you try disabling your ESPHome devices in HASS as above and try 2024.2.2?

DanStasiak commented 6 months ago

@Human , I could try that, but it is only for a test. I have 36 ESPHome devices. :-)

amzaldua commented 6 months ago

I disabled ESPHome, installed HASSIO 2024.2.3, and it restarts every 2-3 minutes.

Human commented 6 months ago

@amzaldua If you have the option, please also disable the Bluetooth integration and try again with 2023.2.2. Then we'll have a more direct comparison.

It's entirely possible that it's not what we disable but something about what we disable. Maybe it's something like the slowest integration to initialize (in our various environments and setups) is the root cause.

crazymikefra commented 6 months ago

@amzaldua If you have the option, please also disable the Bluetooth integration and try again with 2023.2.2. Then we'll have a more direct comparison.

It's entirely possible that it's not what we disable but something about what we disable. Maybe it's something like the slowest integration to initialize (in our various environments and setups) is the root cause.

I'ts really possible. On bluetooth, 1st connections, especially on BLE could take a very long time.

In parallel of that, as said, pybluez has a very old last update (2019). Do you think there can be a bug between the old pybluez and the really more recent bluez and python 3.12 versions ?

I've made some searches and i have a doubt, more recently we have the bleak library. Someone can confirm which library is used by hass actually ?

amzaldua commented 6 months ago

Okay, how can I disable Bluetooth completely? I have Shelly devices too, and Xiaomi BLE...

Human commented 6 months ago

@crazymikefra The python upgrade was in 2023.2.1, but the restarts began with 2023.2.2, so unless people are having this issue in 2023.2.1 but not noticing it, it's likely not a unique cause.

@amzaldua Settings -> Devices and Services -> Bluetooth -> ... menu -> Disable

Note that when I did that, the integration becomes disabled, but HASS still reports starting bluetooth, so I am unsure what that means.

amzaldua commented 6 months ago

@crazymikefra The python upgrade was in 2023.2.1, but the restarts began with 2023.2.2, so unless people are having this issue in 2023.2.1 but not noticing it, it's likely not a unique cause.

@amzaldua Settings -> Devices and Services -> Bluetooth -> ... menu -> Disable

Note that when I did that, the integration becomes disabled, but HASS still reports starting bluetooth, so I am unsure what that means.

My HASS server does not have a dedicated Bluetooth device, so I do not see any Bluetooth options in the 'Devices and Services' menu.

DanStasiak commented 6 months ago

@Human Ok, I did the "disable ESPHome" devices test and after updating to 2024.2.3 the system still reboots. :-(

dermm commented 6 months ago

I have some news.

I have deactivated the Bluetooth entry and the Bluetooth tracker in the configuration.yaml and deactivated the scanner mode for the Shellys. The ESPHome Bluetooth repeater I have is currently offline.

The Bluetooth stick is still connected and the integration under devices is still active.

I have updated to 2024.2.3 after a full system reboot. So far no reboot after 30 minutes.

Thanks to @crazymikefra for the tip and all of you for the great discussion! I'll give another update later

Edit: 4,5 hours without a reboot and stil solid

Rikkie80 commented 6 months ago

Not completely clear to me what you did...

So you kept the Bluetooth integration, but only removed it from your configuration.yaml? The integration doesn't need to be set up in configuration.yaml, right? So why was it there? Just for me to understand it... Or is it the iBeacon tracker you disabled? That is still on in my configuration.

Furthermore you deactivated the "scanner mode for Shelly". Is that Bluetooth part you mean? So also the Shelly remarks are all related to Bluetooth?

Edit: Ow, you're talking about mainly Shelly and a bit ESPHome. So all Bluetooth tracking is switched off, but Bluetooth integration itself is still active, right?

DanStasiak commented 6 months ago

Ok, I also commented out the Bluetooth tracker stuff in the configuration.yaml;

device_tracker:
  - platform: bluetooth_le_tracker
    track_new_devices: true
    interval_seconds: 12

And I updated to the just-released Core Version 2024.2.4. It seems stable. I'll update on if it remains stable in a few hours.

PS: My Bluetooth Proxy devices in ESPHome are untouched and still active, as are all other Bluetooth-related stuff anywhere outside of the configuration.yaml.

Update: I don't know if it was the configuration.yaml edit or the Core Version 2024.2.4 or both but my HA is now over 5 hours stable.

home-assistant / core