No you don’t. What do you mean by completely dead? Have you some logs to show us please?
This is the first time I am seeing this article. When I installed HA I used this article Raspberry Pi - Home Assistant. When I checked the install article for Linux I only then found the link to the install requirements, but only under “Install Home Assistant Supervised”. As mentione I am using HA core!
Also the install article explicitely mentions Raspberry Pi as suggested hardware (and I guess a lot of people are using Pi) and here Debian 12 aka bookworm was only realeased last week (see Bookworm — the new version of Raspberry Pi OS - Raspberry Pi).
There are possibilities to upgrade earlier but this isn’t recommended. And if a user would start with HA the installation would have failed before, because Debian 11 image was available before last week.
As much as I enjoy new features in HA I would appreciate if the update strategy would be “less aggressive”. Also if you have an existing installation you wouldn’t always thing about what has stated in the requirements. Wouldn’t it a good practice to also announce drop of support for an OS version as a breaking change in the Release Notes blog?
1 Like
Then that ADR does not apply to you. it is only for supervised installs.
Core is an advanced installation method and you are expected to maintain your own OS and dependencies.
If this is too much, you could switch to a simpler installation method.
3 Likes
I am using core for good reasons, hosting several other web based applications to not waste hardware just for HA.
Not sure if you read all of my post
- Raspberry Pi is one of the hardware recommended by HA
- Offcial OS from raspberry.com is Raspberry Pi OS / Raspbian and bookworm was officially released last week
- Breaking changes due to dependency to a new OS version should be mentioned in the release notes
It is interesting to see how different we look upon Home Assistant. For me HA is the central application in the home and needs to be rock solid. I would not trust other applications to run in parallel on the same hardware. I even don’t trust a a Pi to do it, because of its limitations. I have a dedicated over spec hardware just to make sure it is stable, it gives me peace of mind 
.
I’m not arguing about breaking changes should’t be clearly stated this was just a reflection. 
1 Like
Then Container would be a better plan 
There are none for Core or Container. The only breaking changes come from Python version requirements (Core) or Docker version requirements (Container), and both of those are covered in the release notes.
1 Like
Hosting several other web based applications + home assistant without docker or any other style of containerisation in 2023 and you complain that something is broken because of OS updates… Hmmm hmm. Ok
3 Likes
I just installed the updates for HA-OS and HA-Core. I was afraid that I will get problems with “energy” but my dashboard luckily showed no issues so far.
My Versions on a HA-Blue:
Home Assistant 2023.10.3 / Supervisor 2023.10.0 / Operating System 11.0 / Frontend 20231005.0 - latest
I have a VELUX KIG 300 gateway to control the shutters, but I don’t want to mess it up with this update…
HOW do I know if this gateway is in bridge mode?
I’m very concerned about this particular breaking change: " Existing receivers paired in bridge mode should be re-added in accessory mode."
What does “Bump” mean? Is the update being included or postponed or just getting a new version number?
1 Like
Hello. Anyone else having trouble accessing the camera.record or camera services? snapshot from the HAOs update??? I attach errors obtained in the registry. Greetings
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:226
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 16:21:50 (1 occurrences)
Last logged: 16:21:50
[140443995739200]
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/camera/init.py”, line 961, in async_handle_snapshot_service
await _async_get_stream_image(camera, wait_for_next_keyframe=True)
File “/usr/src/homeassistant/homeassistant/components/camera/init.py”, line 222, in _async_get_stream_image
return await camera.stream.async_get_image(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/stream/init.py”, line 548, in async_get_image
return await self._keyframe_converter.async_get_image(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/stream/core.py”, line 538, in async_get_image
await self._event.wait()
File “/usr/local/lib/python3.11/asyncio/locks.py”, line 213, in wait
await fut
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/websocket_api/commands.py”, line 226, in handle_call_service
await hass.services.async_call(
File “/usr/src/homeassistant/homeassistant/core.py”, line 2012, in async_call
response_data = await coro
^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/core.py”, line 2049, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/script/init.py”, line 605, in _service_handler
response = await self._async_start_run(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/script/init.py”, line 563, in _async_start_run
script_result = await coro
^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/script/init.py”, line 594, in _async_run
return await self.script.async_run(script_vars, context)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 1578, in async_run
return await asyncio.shield(run.async_run())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 420, in async_run
await self._async_step(log_exceptions=False)
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 470, in _async_step
self._handle_exception(
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 493, in _handle_exception
raise exception
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 468, in _async_step
await getattr(self, handler)()
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 704, in _async_call_service_step
response_data = await self._async_run_long_action(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 666, in _async_run_long_action
return long_task.result()
^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/core.py”, line 2012, in async_call
response_data = await coro
^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/core.py”, line 2049, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/entity_component.py”, line 235, in handle_service
return await service.entity_service_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 876, in entity_service_call
response_data = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 948, in _handle_entity_call
result = await task
^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/camera/init.py”, line 959, in async_handle_snapshot_service
async with asyncio.timeout(CAMERA_IMAGE_TIMEOUT):
File “/usr/local/lib/python3.11/asyncio/timeouts.py”, line 111, in aexit
raise TimeoutError from exc_val
TimeoutError
Logger: homeassistant.components.script.camara_vto
Source: helpers/script.py:468
Integration: Script (documentation, issues)
First occurred: 16:21:50 (1 occurrences)
Last logged: 16:21:50
CÁMARA - VTO: Error executing script. Unexpected error for call_service at pos 2:
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/camera/init.py”, line 961, in async_handle_snapshot_service
await _async_get_stream_image(camera, wait_for_next_keyframe=True)
File “/usr/src/homeassistant/homeassistant/components/camera/init.py”, line 222, in _async_get_stream_image
return await camera.stream.async_get_image(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/stream/init.py”, line 548, in async_get_image
return await self._keyframe_converter.async_get_image(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/stream/core.py”, line 538, in async_get_image
await self._event.wait()
File “/usr/local/lib/python3.11/asyncio/locks.py”, line 213, in wait
await fut
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 468, in _async_step
await getattr(self, handler)()
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 704, in _async_call_service_step
response_data = await self._async_run_long_action(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 666, in _async_run_long_action
return long_task.result()
^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/core.py”, line 2012, in async_call
response_data = await coro
^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/core.py”, line 2049, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/entity_component.py”, line 235, in handle_service
return await service.entity_service_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 876, in entity_service_call
response_data = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 948, in _handle_entity_call
result = await task
^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/camera/init.py”, line 959, in async_handle_snapshot_service
async with asyncio.timeout(CAMERA_IMAGE_TIMEOUT):
File “/usr/local/lib/python3.11/asyncio/timeouts.py”, line 111, in aexit
raise TimeoutError from exc_val
TimeoutError
2023.10.4 caused my ZigBee network to fail, zha can’t configure the USB device. A roll back of the core version to 2023.10.3 resolved it.
(Made the mistake of upgrading before bed, now time for sleep.)
1 Like
I did the exact same thing and had the same problem. Restored 10.3 and ZHA is back up. Seems to be this issue
2 Likes
The 2023.10.4 update already got pulled to revert because of the ZHA issues. Personal am happy I not did tryed to do the update yet 
1 Like
There is several issues with ZHA. Also this ZHA network begin extremely slow · Issue #102396 · home-assistant/core · GitHub
and this ZHA very unreliable: AssertionError and later crash of application controller · Issue #100657 · home-assistant/core · GitHub Similar issues. So rather delay the update some more time of 2023.10.x and fix the open issues. 
1 Like
Updated to .4 brake zha, restore to .3 from backup resolve problem. Good that HA have autobackup when you performe update, never before i did need to use it, good to know that restore works
1 Like
Word of advice: decouple.
Use Zigbee2mqtt.
Even if it has problems all you have to do is roll back the add-on version. Rather than the whole home assistant behoobajoob.
8 Likes
These issues not even are on any 2023.10.x version