2026.3.0 and soft reboot

Installation
1

After upgrade Home Assistant Core to 2026.3.0 reboot of Home Assistant no longer work.
I need to reboot entire HAOS to be able to reboot it.
When looking at the Home Assistant container log i can see this when trying the soft reboot (container restart)

s6-rc: info: service legacy-services: stopping
2026-03-05 12:43:51.148 WARNING (MainThread) [custom_components.tuya_local.device] Shed Light - PIR Spotlight receive loop has terminated
2026-03-05 12:43:51.245 WARNING (MainThread) [homeassistant.core] Task <Task pending name='service homeassistant.restart' coro=<_async_admin_handler() running at /usr/src/homeassistant/homeassistant/helpers/service.py:944> wait_for=<Task pending name='admin service homeassistant.restart' coro=<async_setup.<locals>.async_handle_core_service() running at /usr/src/homeassistant/homeassistant/components/homeassistant/__init__.py:238> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove(), Task.task_wakeup()]> cb=[set.remove()]> was still running after final writes shutdown stage; Integrations should cancel non-critical tasks when receiving the stop event to prevent delaying shutdown
Found 3 non-daemonic threads.
[11:44:04] INFO: Home Assistant Core finish process exit code 0
[11:44:04] INFO: Home Assistant Core service shutdown
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 229, in <module>
    sys.exit(main())
             ~~~~^^
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 188, in main
    from . import config, runner  # noqa: PLC0415
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/runner.py", line 27, in <module>
    from . import bootstrap
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 41, in <module>
    from .components import (
    ...<22 lines>...
    )
  File "/usr/src/homeassistant/homeassistant/components/api/__init__.py", line 17, in <module>
    from homeassistant.components.http import (
    ...<4 lines>...
    )
  File "/usr/src/homeassistant/homeassistant/components/http/__init__.py", line 50, in <module>
    from homeassistant.helpers.network import NoURLAvailableError, get_url
  File "/usr/src/homeassistant/homeassistant/helpers/network.py", line 10, in <module>
    from hass_nabucasa import remote
  File "/usr/local/lib/python3.14/site-packages/hass_nabucasa/__init__.py", line 87, in <module>
    from .remote import RemoteUI
  File "/usr/local/lib/python3.14/site-packages/hass_nabucasa/remote.py", line 22, in <module>
    from .acme import AcmeClientError, AcmeHandler, AcmeJWSVerificationError
  File "/usr/local/lib/python3.14/site-packages/hass_nabucasa/acme.py", line 15, in <module>
    from acme import challenges, client, crypto_util, errors, messages
  File "/usr/local/lib/python3.14/site-packages/acme/__init__.py", line 15, in <module>
    import josepy as jose # noqa: F401
    ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/josepy/__init__.py", line 71, in <module>
    from josepy.jws import JWS, Header, Signature
  File "/usr/local/lib/python3.14/site-packages/josepy/jws.py", line 52, in <module>
    class Header(json_util.JSONObjectWithFields):
    ...<103 lines>...
                raise errors.DeserializationError(error)
  File "/usr/local/lib/python3.14/site-packages/josepy/json_util.py", line 236, in __new__
    raise ValueError(
        f"Field `{key}` in JSONObject `{name}` has no type annotation."
    )
ValueError: Field `alg` in JSONObject `Header` has no type annotation.
[11:44:08] INFO: Home Assistant Core finish process exit code 1
[11:44:08] INFO: Home Assistant Core service shutdown
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

I am running HAOS 17.1
HA Core: 2026.3.0
HA Supervisor: 2026.02.3 (I still cannot update it)
Frontend: 20260304.0

Any ideas?

2

Hi,
All of your versions are current - including Supervisor 2026.02.3.

I was going to suggest something to do with the update to Python 3.14 but you say you are on HAOS so that should have been handled.

Bare metal or a VM manager?

I’ve seen some comments that Proxmox needs some extra settings, but deliberately avoid virtualisation.

A search for PLC0415 brought up a few similar virtualisation issues such as:

3

Mine is doing the same, every 10 min approximately. All versions are current. Mine is running in a Yellow…A friend has a Yellow too experimenting the same issue…

I tried also running in safe mode and still the same issue…

4

I’m having the same issue. Same error in the log. The only workaround is reboot of the host or rebuild the core.

System information

Version core-2026.3.0
Installation type Home Assistant OS
Development false
Supervisor true
Docker true
Container architecture amd64
User root
Virtual environment false
Python version 3.14.2
Operating system family Linux
Operating system version 6.12.67-haos
CPU architecture x86_64
Timezone Europe/Copenhagen
Configuration directory /config

Home Assistant Supervisor

Host operating system Home Assistant OS 17.1
Update channel stable
Supervisor version supervisor-2026.02.3
Agent version 1.8.1
Docker version 29.1.3
5

I received 3.1 while ago, first restored to 2.3 then update to 3.1 and the rebooting issue still…

6

I’m seeing the same with mine.

I caught the following error from the ha core logs:

s6-rc: info: service legacy-services successfully started
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 229, in <module>
    sys.exit(main())
             ~~~~^^
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 188, in main
    from . import config, runner  # noqa: PLC0415
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/runner.py", line 27, in <module>
    from . import bootstrap
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 41, in <module>
    from .components import (
    ...<22 lines>...
    )
  File "/usr/src/homeassistant/homeassistant/components/api/__init__.py", line 17, in <module>
    from homeassistant.components.http import (
    ...<4 lines>...
    )
  File "/usr/src/homeassistant/homeassistant/components/http/__init__.py", line 50, in <module>
    from homeassistant.helpers.network import NoURLAvailableError, get_url
  File "/usr/src/homeassistant/homeassistant/helpers/network.py", line 10, in <module>
    from hass_nabucasa import remote
  File "/usr/local/lib/python3.14/site-packages/hass_nabucasa/__init__.py", line 87, in <module>
    from .remote import RemoteUI
  File "/usr/local/lib/python3.14/site-packages/hass_nabucasa/remote.py", line 22, in <module>
    from .acme import AcmeClientError, AcmeHandler, AcmeJWSVerificationError
  File "/usr/local/lib/python3.14/site-packages/hass_nabucasa/acme.py", line 15, in <module>
    from acme import challenges, client, crypto_util, errors, messages
  File "/usr/local/lib/python3.14/site-packages/acme/__init__.py", line 15, in <module>
    import josepy as jose # noqa: F401
    ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/josepy/__init__.py", line 71, in <module>
    from josepy.jws import JWS, Header, Signature
  File "/usr/local/lib/python3.14/site-packages/josepy/jws.py", line 52, in <module>
    class Header(json_util.JSONObjectWithFields):
    ...<103 lines>...
                raise errors.DeserializationError(error)
  File "/usr/local/lib/python3.14/site-packages/josepy/json_util.py", line 236, in __new__
    raise ValueError(
        f"Field `{key}` in JSONObject `{name}` has no type annotation."
    )
ValueError: Field `alg` in JSONObject `Header` has no type annotation.

It’s very frustrating that this keeps happening.

7

I have same error. Running on proxmox. When i update something and it needs to reboot it doesnt come back up. I need to manully reboot the proxmox VM haos.

This is frustating.

8

Seems like its the integration of AULA that causes the issue. Update to newest AULA version or deactivate it.

The aula integration’s PyJWT>=2.4.0 requirement pulls in josepy 1.15.0 , which overwrites Home Assistant’s expected josepy 2.2.0 . This breaks the ACME certificate process used by Home Assistant Cloud (Nabu Casa) for remote access.