Core 2024.2.0 update fail

Installation
23

Hi all. I see this issue is apparently solved but I have the same error and don’t know how to remove the Hikvision HACS integration as I can’t start HA. Not convinced that is the root cause but I do have Hikvision.

HA core docker on ubuntu intel nuc.

I’ve tried rolling back to 2024.1.0 and forward to 2024.2.0b4. Same error.

Tried using non container venv hass with same result.

I think it was working on first upgrade to 2024.2.0 until I was trying to get thread/matter/open border router working but I hope that’s a separate drama.

I don’t have any backups (they’ve never worked) and my reef tank, chickens, home security etc rely on HA. I’ve invested 5 years in this. It’s the first time it has failed and not keen on starting from scratch with another product.

Error is:

> 2024-02-08 18:49:13.196 ERROR (MainThread) [root] Uncaught exception
> 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 221, in <module>
>     sys.exit(main())
>              ^^^^^^
>   File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
>     exit_code = runner.run(runtime_conf)
>                 ^^^^^^^^^^^^^^^^^^^^^^^^
>   File "/usr/src/homeassistant/homeassistant/runner.py", line 188, in run
>     return loop.run_until_complete(setup_and_run_hass(runtime_config))
>            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>   File "/usr/local/lib/python3.12/asyncio/base_events.py", line 684, in run_until_complete
>     return future.result()
>            ^^^^^^^^^^^^^^^
>   File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in setup_and_run_hass
>     hass = await bootstrap.async_setup_hass(runtime_config)
>            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>   File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 203, in async_setup_hass
>     await async_from_config_dict(config_dict, hass) is not None
>     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>   File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 319, in async_from_config_dict
>     await async_load_base_functionality(hass)
>   File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 296, in async_load_base_functionality
>     await asyncio.gather(
>   File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1354, in async_initialize
>     entries[entry_id] = config_entry
>     ~~~~~~~^^^^^^^^^^
>   File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1148, in __setitem__
>     self._domain_unique_id_index.setdefault(entry.domain, {})[
> TypeError: unhashable type: 'list'
24

I run Home Assistant on a virtual machine on an Intel NUC. When I revert back to the state before the 2024.2 update (it loads the previous snapshot backup within a few seconds), everything works. That’s why I’ve tried to update multiple times. The update itself is successful, and HA starts up. It seems that only the Tuya authentication has changed, but following the instructions, authentication is successful. However, the Futurenow thermostats, provided by the FN-stat integration, don’t work at all. After each update, the thermostats completely disappear and cannot be brought back, even though the configuration.yaml file contains the configuration as specified by the thermostat manufacturer, and it used to work before the update. It’s quite embarrassing because it’s the heating season, which is why I unfortunately can’t update. Does anyone use this thermostat: FNIP-12xMZT?

25

Crisis and stress mostly averted. Rum helped.

Made a mistake of downloading 2024.1.0 but not loading it.

Rolling back to 2024.1.0 allowed HA to start but now I have no integrations or frontend components visible in HACS… Not sure if that’s a related issue but one for tomorrow. Also some new authentication required for Tuya.

Deleted hikvision_next integration and could then roll forward to :stable. So seems to be the same root cause. My bad for not rolling back properly.

Smells more catastrophic than breaking change!

26

I don’t know, maybe another integration.
you can try taking a look on GitHub

27

Also failed for me, tried it two times already.

It is weird, because at some point I already saw this feature!

image
image748×728 55.3 KB

Showed me that my tuya integration is not working (which it is, I know that).

Here is a list of my current integrations

image
image2295×784 96.5 KB

28

for hikvision-next specifically there is now a work around in the thread. If you deleted the integration it just requires editing a single file in on the hacs integration. (i’m sure this will be a release soon) If you haven’t deleted the integration i think you’ll also have to edit the config entry as well.

29

Same with tibber_custom from hacs: Does not work with new Home Assistant version · Issue #54 · Danielhiversen/home_assistant_tibber_custom · GitHub

30

sorry can you point out me to this work around?
tnx

31

i think 2024.2.1 likely makes the issue mute. I would try to upgrade to it and likely it will work.

However refer to the thread here https://github.com/maciej-or/hikvision_next/issues/138

Screenshot 2024-02-09 at 8.47.10 AM
Screenshot 2024-02-09 at 8.47.10 AM739×76 6.79 KB

32

I have an HA installation over Home Assistant Green hardware.
the software version is Home Assistant OS 11.5 and Core 2024.1.6
Worked fine until i tried to upgrade to core 2024.2.0 (last), but no success.

The result of the failed update:
Attempting to connect to the HA server via port 1823 no longer works.
(192.168.10.xxx refused a connection).
Connection on port 4357 (observer) works. State:
Supervisor: Connected
Supported: Supported
Healthy: Healthy

Any hints how to solve?

33

I removed tibber and tuya, which seem to cause problems. Still no luck. Anyone an idea how to look into the logs of the update?

MY_INSTANCE:8123/config/logs

doesnt give any hint.

34

Hello everyone!
After I updated my Pi4 to HAOS 2024.2.0 … the dashboard/web gui cannot be accessed anymore.

image
image696×195 10.5 KB

In HA observer everything seems to be fine.
PI can be accessed via ssh but reboot command doesn`t have any influence at all.
Any advices? :frowning:

Thank you.

35

I got exactly same issue. Let me know if you find steps to resolve this?

36

I fixed the issue with the following command send through ssh:

ha core update --version 2024.1.6

Now I don`t know if I should try again the update to the newest version or wait a little bit more …

37

For me apperently there was the issue of more ram consumption. Got an OOM after a while. Had 1GB before, which was working fine in the VM. Now bumped to 4GB. Running smoothly again.

38

I have had a problem since updating to 2024.2 Although the update worked my system was running terribly slow and using a lot of resources. This seems to be due to the 4 cameras from my Nvr, so there may be some issue with camera feeds as your problem was related to your hikvision integration? I have tried putting my camera feeds back, but every time I do the problem returns so I am pretty sure this is where my problem lies.

39

The problem still exists; skipping 2024.2.2 and installing 2024.2.3 doesn’t help. The consent restarting still exists.

By the way. the only help is to do a “su restart” command and then repeat a “core update --version 2024.2.1” command until “Processing…” shows.

I guess we have to wait until the problem is addressed and fixed. I wonder if the 2024.3 Update will remedy the problem.

1 Like
40

So for now it’s better to not update over 2024.2.1… Isn’t this considered a breaking point for future updates? Why update if you know it’s going to slow/bug your system?
It must be fixed asap :confused:

41

Hi folks,

I do not have the Tuya or Hikvision integration.

How can I check the upgrade logs to identify which integration takes a long time and ultimately fails the upgrade?

42

I can’t update core either, and I don’t have Hikvision. Any thoughts?