You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just updated the supervisor, which managed to produce an error about websockets in the logs. I'm fairly sure it's not a coincidence.
I wonder if an upgrade can't make components shutdown gracefully. Because you see, maybe this error is totally normal. Although "Unexpected exception" tells me it's rather unexpected, so maybe not so normal. Either way, don't litter the logs with errors just as a result of shutting down stuff that might've been working on something and producing an error as a result. These are assumptions though, but what else could it be in an otherwise mostly error-free installation.
What version of Home Assistant Core has the issue?
2025.1.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:245
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 11:55:15 (1 occurrences)
Last logged: 11:55:15
[140397006294032] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 262, in async_install
await self.coordinator.supervisor_client.supervisor.update()
File "/usr/local/lib/python3.13/site-packages/aiohasupervisor/supervisor.py", line 43, in update
await self._client.post(
...<3 lines>...
)
File "/usr/local/lib/python3.13/site-packages/aiohasupervisor/client.py", line 182, in post
return await self._request(
^^^^^^^^^^^^^^^^^^^^
...<7 lines>...
)
^
File "/usr/local/lib/python3.13/site-packages/aiohasupervisor/client.py", line 129, in _request
await self._raise_on_status(response)
File "/usr/local/lib/python3.13/site-packages/aiohasupervisor/client.py", line 76, in _raise_on_status
raise exc_type(result.message, result.job_id)
aiohasupervisor.exceptions.SupervisorBadRequestError: No supervisor update available - 2025.02.0
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<7 lines>...
)
^
File "/usr/src/homeassistant/homeassistant/core.py", line 2795, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2838, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1006, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
hass, entity, func, data, call.context
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1078, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 157, in async_install
await entity.async_install_with_progress(version, backup)
File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 489, in async_install_with_progress
await self.async_install(version, backup)
File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 264, in async_install
raise HomeAssistantError(
f"Error updating Home Assistant Supervisor: {err}"
) from err
homeassistant.exceptions.HomeAssistantError: Error updating Home Assistant Supervisor: No supervisor update available - 2025.02.0
Additional information
No response
The text was updated successfully, but these errors were encountered:
Hey there @home-assistant/supervisor, mind taking a look at this issue as it has been labeled with an integration (hassio) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of hassio can trigger bot actions by commenting:
@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign hassio Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
The problem
I just updated the supervisor, which managed to produce an error about websockets in the logs. I'm fairly sure it's not a coincidence.
I wonder if an upgrade can't make components shutdown gracefully. Because you see, maybe this error is totally normal. Although "Unexpected exception" tells me it's rather unexpected, so maybe not so normal. Either way, don't litter the logs with errors just as a result of shutting down stuff that might've been working on something and producing an error as a result. These are assumptions though, but what else could it be in an otherwise mostly error-free installation.
What version of Home Assistant Core has the issue?
2025.1.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: