2025.7: That's the question

i am running it in a vm in proxmox.

Supervised or HA OS?

i am quite sure it is HA OS. I have downloaded a vm and imported it is proxmox many years ago.

Reboot the VM (from within HA). Restarting HA is not sufficient.

Developer Tools → YAML → Restart → Advanced Options → Reboot.

i just restarted the entire proxmox host. ha starts but many integrations are not available. and if i try to restore from a local backup i get that the backup manager is busy and it is blocked

i try to list the available backups in the ha> console but the list flies very fast and | more doesn’t work.

how can I tell it to restore the latest automatic backup? or what is the namin scheme for the automatic backups?

there is this error at startup:

I’m seeing wierd supervisor network behavior on 2025.7.x as well. No supervisor internet even though I can force download the update on the same box… Haven’t figured out what’s up yet. But something is off in the IP stack. It’s not impacting run, but updates are borked. Mine is HAOS

i solved it! i am running pihole on my network and that decided to misbehave after latest update. so i changed the dns in the router to 1.1.1.1 but for some reason the dns in HA remained the pihole one.

now I have changed the dns to 192.168.1.1 (the router) and now is all good and started!

Sense Power Meter integration probably needs removed. They shut down their API and it is all pointed to SchneiderHome software. Piece of garbage app and probably losing all their customers. Had a nice run…

I’ve been using it. The announce and speak notify entities work well and are stable. There’s a switch to activate ā€œDo Not Disturbā€ and two sensors, one for bluetooth and one for connectivity.

The developer posted a road map and is currently fixing any countries that are having issues using the integration as the top priority. The pull requests show progress in adding other sensors (like dog barking, sound of running water, glass breaking, etc), as well as websocket support for media player controls. The last item on the roadmap is connected devices (which I assume are things like echo glows and other bluetooth, zigbee, or thread connected devices to the alexa ecosystem).

Currently, it’s not as robust as HACS Alexa Media Player. But it will be with time. It’s stable for me in the US. I’m not exactly sure if it’s using the same unofficial API as AMP, but according to AI (which I had review the code), the AI seems to believe Alexa Devices is using an official API via Alexa Developer Console. I suppose only the developer can confirm or deny that.

I have HAOS and running 2025.7.1:

Somehow my instance doesn’t notice there is an update (to .2 and to .3). I already manually hit Check for updates but nothing happens, any ideas?
This hasn’t happened before.

Reboot. Not restart.

Had similar problems in the past, I’ve noticed HA did not connect to update servers in case local network was down for some time and then back up. In the supervisor logs I got many notes about DNS…

not sure if this is new, never noticed before, but check:

in the ESPHome device dashboard for the Atom echo.

there is no way to pull up the more-info on the volume slider. Clicking the icon now is an active toggle for the volume, and the slider sets the volume, as it should.

The toggle seems to be new, and, well, a UI issue…

I’m not getting the option to automatically rename entities when changing device name since I updated to 2025.7.3

Cache has been cleared
Have rebooted
Advanced setting is on
It’s not a sluggified naming issue

Happens on my computer and mobile
Happens on three different home assistant OS systems… the most recently updated one was OK immediately before the update.

Grateful for any advice

Thanks, I just did but still no update available but I guess it’s due to this error?

Logger: homeassistant.components.system_health
Source: components/system_health/__init__.py:89
integration: System Health (documentation, issues)
First occurred: 10:58:45 (1 occurrence)
Last logged: 10:58:45

Error fetching info
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/aiogithubapi/client.py", line 139, in async_call_api
    result = await self._session.request(**request_arguments)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 770, in _request
    resp = await handler(req)
           ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 725, in _connect_and_send_request
    conn = await self._connector.connect(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        req, traces=traces, timeout=real_timeout
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 622, in connect
    proto = await self._create_connection(req, traces, timeout)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1189, in _create_connection
    _, proto = await self._create_direct_connection(req, traces, timeout)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1512, in _create_direct_connection
    hosts = await self._resolve_host(host, port, traces=traces)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1128, in _resolve_host
    return await asyncio.shield(resolved_host_task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/system_health/__init__.py", line 89, in get_integration_info
    data = await registration.info_callback(hass)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hacs/system_health.py", line 29, in system_health_info
    response = await hacs.githubapi.rate_limit()
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiogithubapi/github.py", line 240, in rate_limit
    response = await self._client.async_call_api(endpoint="/rate_limit", **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiogithubapi/client.py", line 141, in async_call_api
    raise GitHubConnectionException(
    ...<2 lines>...
    ) from exception
aiogithubapi.exceptions.GitHubConnectionException: Request exception for 'https://api.github.com/rate_limit' with - 

Or most likely due to this error:

Logger: homeassistant.helpers.entity_component
Source: helpers/entity_component.py:62
First occurred: 10:58:31 (30 occurrences)
Last logged: 11:03:31

Forced update failed. Entity update.tabbed_card_update not found.
Forced update failed. Entity update.telenet_telemeter_update not found.
Forced update failed. Entity update.tesla_update not found.
Forced update failed. Entity update.tp_link_easy_smart_switch_update not found.
Forced update failed. Entity update.xiaomi_vacuum_map_card_update not found.

I noticed those HACS extensions were not showing up in my installed HACS extensions list, which is kind of weird since I do use the tesla one and the vaccuum card. Looks like something went out of sync in HACS…

I think it may be by design, as they have changed the UI to be able to find entities more easily without having to change their names. Changing entity names without being aware that many of the automations and dashboards may subsequently need editing has caused problems for many people. In my case I now welcome not needing to do so.

1 Like

I use the spook integration for that, I was so fed up in things brake without noticing.
Tbh I think spook should be a default feature in ha.

3 Likes

I fixed all errors, did another Reboot (through HA UI) but still nothing, I don’t get any errors in the logs either.

EDIT:

For whoever comes across this post with the same issue, I tried updating through CLI where I got Error updating Home Assistant Core ā€˜HomeAssistantCore.update’ blocked from execution, no host internet connection which probably is a DNS issue (go to network settings), then I forced HA to update to the 2025.7.3 version on the cmd line.

The Updates page in HA should be a bit more verbose, right now it didn’t say anything (no failed message whatsoever)

1 Like