2024.5: Just a little bit smaller

PrairieSnpr · May 4, 2024, 7:45pm

Well, that was the most painful upgrade in quite a while. If anyone else has ha in a venv, on a pi4 with a 64bit kernel and 32bit userland, be prepared to start from scratch due to the inclusion of aiohttp-isal.

Mariusthvdb · May 4, 2024, 9:34pm

you can probably fix that using

  card-mod-more-info-yaml: |

    $: |
      .mdc-dialog {
        backdrop-filter: blur(17px) !important;
        -webkit-backdrop-filter: blur(17px) !important;
      }

in a card-mod-theme. All drop-downs remain in front and the background is blurred nicely on more-info

Ildar_Gabdullin · May 4, 2024, 10:01pm

I am not using blurring in themes.
This was for people who tried to use a new functionality & failed.

jumper · May 4, 2024, 10:41pm

Nice that one can drag and drop Tile Features like just reordering them in yaml.

But, how can one specify icons for climate preset-modes? I get generic dots for these (for a water heater that’s modeled as a climate device since esphome does not yet have a water heater model. But that’s another discussion):

features:
 - type: "climate-preset-modes"
   style: "icons"
   preset-modes:
    - Eco Mode
    - Electric
    - Heat Pump
    - High Demand
    - "Off"

K-n-C · May 5, 2024, 1:02am

Using a Shelly 1 for a garage door switch and it kept falling off the network after upgrading to 2024.5.1. Rolled back to 2024.4.4 and all is well again.

K-n-C · May 5, 2024, 1:12am

After upgrading to 2024.5.1 the Dreo (HACS) integration stopped polling for some reason. I could change the panel_sound and it would not change in Developer tools. I could change it from the Dreo App or try to use my mushroom card I posted here.

Also, for the mushroom template that changes icon and color based on state had no styling at all. Could be because HA could not poll the fan, but again rolling back to 2024.4.4 was the solution.

Lastly, I modified the media_player.py for panasonic_bluray, and I am trying to figure out a way to either script a copy or exclude the file from being updated during an upgrade.

parautenbach · May 5, 2024, 5:12am

Using which Shelly integration?

parautenbach · May 5, 2024, 5:12am

Running which OS and version?

nickrout · May 5, 2024, 5:39am

Presumably HA doesn’t have anything to do with your wifi access point, so it can’t take your wifi device off the network.

SteffenDE · May 5, 2024, 7:51am

I’m back to 2024.4.4

No way to get 2024.5.x running or find the problem at debug log. I’m disable different intergrations but HA is running very slow (with high CPU) and so I get ‘database performance issues’ and ‘sensor took longer than the scheduled update interval’.

Do not find where it comes from …

PrairieSnpr · May 5, 2024, 9:41am

This was Raspbian Lite Bookworm, it was an older install though, had started as Buster and been upgraded over the last few years. Looks like @bdraco has a PR pending here Switch out aiohttp-isal for aiohttp-fast-zlib to make isal optional by bdraco · Pull Request #116814 · home-assistant/core · GitHub that would make isal optional, but I just chose to go ahead and move to a fully 64 bit OS and be done with it.

parautenbach · May 5, 2024, 9:58am

Good idea.

nickrout · May 5, 2024, 11:28am

Yet ipmi was obviously giving you problems, but you haven’t disabled that (despite it being pointed out to you) and haven’t posted an issue on their GitHub.

So that one probably won’t be fixed any time soon. Thanks for nothing.

K-n-C · May 5, 2024, 1:22pm

https://www.home-assistant.io/integrations/shelly

Bieniu · May 5, 2024, 2:19pm

Open an issue on GH with attached diagnostics file and debug log for Shelly integration.

RG3 · May 5, 2024, 2:55pm

Same issue as a few others here since upgrading to 2024.5.X. Everything goes well for a few hours then very high CPU usage that limit access to the frontend and makes troubleshooting difficult. I finally got a prolonged high CPU usage overnight and it appeared to be related to the Amcrest integration for me. Checking the open issues I found an issue with a PR for what I’m experiencing, so waiting for 20204.5.2 to hopefully fix it for me.

github.com/home-assistant/core

Amcrest on 2024.5.0 with offline camera causing HA to fail loading completely, got stuck with increased CPU usage

opened 11:58AM - 05 May 24 UTC

paludi

integration: amcrest non-thread-safe operation

### The problem Updated to 2024.5.0 and 2024.5.1 and noted that HA failed to lo…ad competely. I also noticed an increase in CPU usage (around 10x higher) resulting in CPU usage stabilizing around 30% instead of 3%. - Rolled back to 2024.4.4 and HA loaded correctly, CP immediately dropped. - removed the configuration of camera with the Amcrest integration and 2024.5.1 loaded correctly, with CPU being back at 3%. I have a camera configured that was offline at time of starting HA. (the camera is offline most of the time, I just turn it on when needed) ### What version of Home Assistant Core has the issue? core-2024.5.0 and core-2024.5.1 ### What was the last working version of Home Assistant Core? core-2024.4.4 ### What type of installation are you running? Home Assistant Container ### Integration causing the issue Amcrest ### Link to integration documentation on our website https://www.home-assistant.io/integrations/amcrest/ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml amcrest: - host: 192.168.xxx.xxx username: !secret armcrest_camera_user password: !secret armcrest_camera_password name: "Amcrest Camera" binary_sensors: - online ``` ### Anything in the logs that might be useful for us? ```txt amcrest.exceptions.CommError: HTTPConnectionPool(host='192.168.xxx.xxx', port=80): Max retries exceeded with url: /cgi-bin/magicBox.cgi?action=getMachineName (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f6d6bc8c0>: Failed to establish a new connection: [Errno 113] Host is unreachable')) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/amcrest/camera.py", line 330, in async_on_demand_update self.async_schedule_update_ha_state(True) File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1252, in async_schedule_update_ha_state self.hass.async_create_task( File "/usr/src/homeassistant/homeassistant/core.py", line 816, in async_create_task self.verify_event_loop_thread("async_create_task") File "/usr/src/homeassistant/homeassistant/core.py", line 440, in verify_event_loop_thread frame.report( File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 162, in report _report_integration(what, integration_frame, level, error_if_integration) File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 203, in _report_integration raise RuntimeError( RuntimeError: Detected that integration 'amcrest' calls async_create_task from a thread at homeassistant/components/amcrest/camera.py, line 330: self.async_schedule_update_ha_state(True). Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+amcrest%22. additional logs: self.connect() File "/usr/local/lib/python3.12/site-packages/urllib3/connection.py", line 205, in connect conn = self._new_conn() ^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/urllib3/connection.py", line 186, in _new_conn raise NewConnectionError( urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f6d6bc8c0>: Failed to establish a new connection: [Errno 113] Host is unreachable During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/requests/adapters.py", line 486, in send resp = conn.urlopen( ^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/urllib3/connectionpool.py", line 799, in urlopen retries = retries.increment( ^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/urllib3/util/retry.py", line 592, in increment raise MaxRetryError(_pool, url, error or ResponseError(cause)) urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='192.168.xxx.xxx', port=80): Max retries exceeded with url: /cgi-bin/magicBox.cgi?action=getMachineName (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f6d6bc8c0>: Failed to establish a new connection: [Errno 113] Host is unreachable')) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/amcrest/http.py", line 305, in _command resp = session.get( ^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/requests/sessions.py", line 602, in get return self.request("GET", url, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/requests/sessions.py", line 589, in request resp = self.send(prep, **send_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/requests/sessions.py", line 703, in send r = adapter.send(request, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/requests/adapters.py", line 519, in send raise ConnectionError(e, request=request) requests.exceptions.ConnectionError: HTTPConnectionPool(host='192.168.xxx.xxx', port=80): Max retries exceeded with url: /cgi-bin/magicBox.cgi?action=getMachineName (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f6d6bc8c0>: Failed to establish a new connection: [Errno 113] Host is unreachable')) The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/amcrest/__init__.py", line 193, in command ret = super().command(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/amcrest/http.py", line 253, in command self._generate_token() File "/usr/local/lib/python3.12/site-packages/amcrest/http.py", line 150, in _generate_token resp = self._command(cmd).content.decode() ^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/amcrest/http.py", line 327, in _command raise CommError(error) from error amcrest.exceptions.CommError: HTTPConnectionPool(host='192.168.xxx.xxx', port=80): Max retries exceeded with url: /cgi-bin/magicBox.cgi?action=getMachineName (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f6d6bc8c0>: Failed to establish a new connection: [Errno 113] Host is unreachable')) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/amcrest/camera.py", line 330, in async_on_demand_update self.async_schedule_update_ha_state(True) File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1252, in async_schedule_update_ha_state self.hass.async_create_task( File "/usr/src/homeassistant/homeassistant/core.py", line 816, in async_create_task self.verify_event_loop_thread("async_create_task") File "/usr/src/homeassistant/homeassistant/core.py", line 440, in verify_event_loop_thread frame.report( File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 162, in report _report_integration(what, integration_frame, level, error_if_integration) File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 203, in _report_integration raise RuntimeError( RuntimeError: Detected that integration 'amcrest' calls async_create_task from a thread at homeassistant/components/amcrest/camera.py, line 330: self.async_schedule_update_ha_state(True). Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+amcrest%22. 2024-05-05 11:08:47.681 WARNING (Amcrest Amcrest Camera) [py.warnings] /usr/src/homeassistant/homeassistant/util/logging.py:110: RuntimeWarning: coroutine 'Entity.async_update_ha_state' was never awaited log_exception(format_err, *args) 2024-05-05 11:08:47.681 WARNING (Amcrest Amcrest Camera) [homeassistant.components.amcrest] Error while processing events from Amcrest Camera camera: CommError(ConnectionError(MaxRetryError("HTTPConnectionPool(host='192.168.xxx.xxx', port=80): Max retries exceeded with url: /cgi-bin/magicBox.cgi?action=getMachineName (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f6d6bc8c0>: Failed to establish a new connection: [Errno 113] Host is unreachable'))"))) 2024-05-05 11:08:52.625 WARNING (MainThread) [homeassistant.helpers.entity] Update of camera.amcrest_camera is taking over 10 seconds 2024-05-05 11:08:57.624 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:09:12.625 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:09:27.625 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:09:42.625 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:09:57.625 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:10:08.524 WARNING (MainThread) [homeassistant.components.mqtt.client] Disconnected from MQTT server 192.168.xxx.xxx:1883 (7) 2024-05-05 11:10:12.625 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:10:27.625 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:10:42.626 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:10:57.626 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:11:12.626 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:11:27.626 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:11:42.626 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:11:50.548 WARNING (MainThread) [homeassistant.components.mqtt.client] Disconnected from MQTT server 192.168.xxx.xxx:1883 (7) 2024-05-05 11:11:57.626 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:12:12.627 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:12:27.627 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 2024-05-05 11:12:42.627 WARNING (MainThread) [homeassistant.components.camera] Updating amcrest camera took longer than the scheduled update interval 0:00:15 ``` ### Additional information - The camera was offline when starting HA, therefore the camera was not reachable during startup - when setting "debug: true" in the homeassistant configuration, HA starts normally. "debug: false" (or no setting) reproduces the issue

SteffenDE · May 5, 2024, 2:59pm

I disabled it, but the behavior of HA didn’t change even without IPMI. I threw out IPMI completely, so I can’t open a ticket at the moment. Thank you for such great comments and thanks for nothing too.

nickrout · May 5, 2024, 10:30pm

You didn’t tell us you had disabled ipmi. You said you disabled “different integrations” which is meaningless.

Meanwhile the author of ipmi is blissfully unaware.

My pleasure by the way.

DrewXT · May 6, 2024, 12:02am

has anyone seen the following? I’m getting it maybe once or twice a day - also unsure how to work out the triggers…

Specifically watchdog restarting homeassistant …

2024-05-06 09:00:26.364 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqtt'
2024-05-06 09:00:26.929 INFO (MainThread) [supervisor.auth] Successful login for 'mqtt'
2024-05-06 09:05:56.216 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2024-05-06 09:13:01.790 WARNING (MainThread) [supervisor.homeassistant.websocket] Connection is closed
2024-05-06 09:13:05.923 WARNING (MainThread) [supervisor.homeassistant.core] Watchdog found Home Assistant failed, restarting...
2024-05-06 09:13:05.941 INFO (SyncWorker_4) [supervisor.docker.manager] Starting homeassistant
2024-05-06 09:13:06.092 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2024-05-06 09:13:09.402 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2024-05-06 09:13:09.514 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete

ChirpyTurnip · May 6, 2024, 12:13am

Hi,

Shortly after release I reported my Shelly Gen1 devices didn’t reconnect after upgrading to 2024.5. This is now a recurrent problem - after any HA restart (e.g. after upgrading to 2024.5.1, after a HACS update, after a config update, etc) there is a better than average chance that some of the Shelly devices fail to reconnect.

I’ve found a similar issues here: No Shelly connections after 2024.3.0 HA upgrade - #14 by BenZoFly

And posted this update:

So a similar thing here. Everything was PERFECT and ROCK SOLID for at least 18 months…then I install 2024.5 and on restart half my Shelly devices Gen1 are offline…a restart of HA doesn’t not return them, nor does a full reboot, not does just ‘waiting’. However, going to Settings > Integrations > Shelly and then for each Shelly device (I have 38) going Reload causes the Shelly to come back on line. It doesn’t need me to touch the Shelly devices themselves, the reload operation immediately restores the connection.

I do not know what has changed, it is almost like the new “fast startup” stuff that has been added is not allowing enough time to restore everything… I have a mix of Shelly devices, all Gen1, all with no cloud service, all hardcoded to talk directly to HA. Some will connect correctly, others do not. I’m not certain yet if it is the same ones that fail on restart or a random selection. But it wasn’t like this before!

The logs have this:

2024-05-06 11:50:37.929 ERROR (MainThread) [homeassistant.components.shelly] Error fetching Shelly-ConservatoryLights data: Error fetching data: DeviceConnectionError()
2024-05-06 11:50:37.958 ERROR (MainThread) [homeassistant.components.shelly] Error fetching Shelly-Ensuite-Floor data: Error fetching data: DeviceConnectionError()
2024-05-06 11:50:38.825 ERROR (MainThread) [homeassistant.components.shelly] Error fetching Shelly-Bathroom data: Error fetching data: DeviceConnectionError()

And yet reload re-establishes a stable connection until the next restart…so there is no actual connection problem…