Hi,
running HA on Raspi 5. After updating to 2026.6.1 yesterday, no history data is shown and the energy card is broken with error message.
Log:
Logger: homeassistant.components.websocket_api.http.connection
Quelle: components/recorder/core.py:350
Integration: Home Assistant WebSocket API (Dokumentation, Probleme)
Erstmals aufgetreten: 13:17:14 (26 Vorkommnisse)
Zuletzt protokolliert: 13:31:39
[547247843712] Error handling message: Unknown error (unknown_error) Tiger_Home from 192.168.178.85 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36 Edg/148.0.0.0)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 26, in _handle_async_response
await func(hass, connection, msg)
File "/usr/src/homeassistant/homeassistant/components/history/websocket_api.py", line 543, in ws_stream
last_event_time = await _async_send_historical_states(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<11 lines>...
)
^
File "/usr/src/homeassistant/homeassistant/components/history/websocket_api.py", line 294, in _async_send_historical_states
last_time_ts, last_time_dt, payload = await instance.async_add_executor_job(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
_generate_historical_response,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<9 lines>...
send_empty,
^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/components/recorder/core.py", line 350, in async_add_executor_job
return self.hass.loop.run_in_executor(self._db_executor, target, *args)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/asyncio/base_events.py", line 898, in run_in_executor
executor.submit(func, *args), loop=self)
~~~~~~~~~~~~~~~^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/concurrent/futures/thread.py", line 205, in submit
raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown
Anyone else with the same problems?
EDIT:
I've restored 5 days old backup with version 2026.5.4. Everything works fine again.
Looks like the error "cannot schedule new futures after shutdown" is a python issue, hope it gets fixed with next release.