Closed HughMac01 closed 8 months ago
since you got these system, information (which also shows you are on core-2024.1.5) i'm not sure, what your issue is?
Thanks for responding
I downloaded the 2024.2 core update but it will not instsll. I am using a raspberry pi4 HA core Regards
Hugh McCluskey
Mobile: +27813976132
On Sun, 4 Feb 2024 at 13:46, Michael @.***> wrote:
since you got these system, information (which also shows you are on core-2024.1.5) i'm not sure, what your issue is?
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/109597#issuecomment-1925720029, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMGLT6MQOIZRH2TOJLUIATDYR5YJLAVCNFSM6AAAAABCYYNS26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVG4ZDAMBSHE . You are receiving this because you authored the thread.Message ID: @.***>
there is not 2024.2 released, yet. or do you mean the current beta 2024.2.0b4? if yes, how did you download it?
Update fails when I try installing 2024.2.0b4 core update. I am running OVA virtual machine on proxmox 8.1 with the following setup
Core 2024.1.6
Supervisor 2024.01.1
Operating System 11.5.rc3
Frontend 20240104.0
please try again to update to beta and check if you find (after the update failed and HA restarts) a home-assistant.log.1
and/or home-assistant.log.fault
in /config
(fo details see viewing logs) and provide them if existing.
tried once again. home-assistant-rollback.log and the same in home-assistant.log.1 I find this:
2024-02-04 18:00:55.806 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'
home-assistant.log.fault is empty
new beta came in 2024.2.0b5 however result is the same with the same error outcome
Apparently there is a faulty config entry. Could you maybe take your .storage/core.config_entries
file and remove all kinds of entry data (tokens, username, passwords) and share the rest with us?
config.txt location, addresses, names, passwords and tokens replaced with 'hidden' word.
This is really helpful, thanks!
hikvision_next
is the integration that is setting a list as unique id for the config entry. I think we added another index in 2024.2, which is uncovering this bug. (As this was never supported, HA isn't at fault).
This info might not help you, but it would help you specify the problem in the issue to the integration developer.
when I was cleaning up config text file I did found some disabled integrations and hikvision-next was one of those I dont use anymore. cleanup disabled devices, restarted HA. pressed update and it worked like a clock :) thanks for help. I moved to frigate from hikvision integration so not needed anymore :) another question how I could clean up more things like registry of deleted devices and etc... I was very actively testing various stuff and with 6 months passed I am sure I have tons of irrelevant things. is there any guide for doing such task?
I think the people on the discord and the forums probably know a better answer to this :)
Thanks for verifying. I will close the issue.
yes i have ob4
I heard that you have to update Python for Home Assistant. I have not done this so I cannot confirm. I was sent this by Home Assistant (Nabu Casa?) Thanks Regards
Hugh McCluskey
Mobile: +27813976132
On Sun, 4 Feb 2024 at 14:35, Michael @.***> wrote:
there is not 2024.2 released, yet. or do you mean the current beta 2024.2.0b4? if yes, how did you download it?
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/109597#issuecomment-1925734141, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMGLT6O772R2NDOMZ6IRF73YR5573AVCNFSM6AAAAABCYYNS26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVG4ZTIMJUGE . You are receiving this because you authored the thread.Message ID: @.***>
You don't have to, in 2 months it's required.
I just saw that I solved another problem and not the one of the author. Could you share the log files you get?
My error starting from module six.moves
I believe i have same issues.... Upgrade never completes. I did have hikvision add-on installed. Its now removed and issues still persists. On RaspberrryPI5
Solved by removing Hikvision..... Hopefully temporarily... Thanks for responses
On Thu, 08 Feb 2024, 1:56 am alanburchill, @.***> wrote:
I believe i have same issues.... Upgrade never completes. I did have hikvision add-on installed. Its now removed and issues still persists. On RaspberrryPI5
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/109597#issuecomment-1933133795, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMGLT6IIXJYQXXXVSC4ZF7LYSQIBZAVCNFSM6AAAAABCYYNS26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZTGEZTGNZZGU . You are receiving this because you authored the thread.Message ID: @.***>
jq -r '.data.entries[] | select(.unique_id | type == "array") | {unique_id, domain}' /config/.storage/core.config_entries
Please execute this and let us know what it returns
When I ran the above command, it ended up pointing to 'schlage', which was this Schlage integration (not the native one) that was causing issues (specifically: https://github.com/mcnutter1/homeasssitant-schlage/issues/23).
Removing that and trying the upgrade again worked successfully!
Hikvision was my problem
On Sat, 10 Feb 2024, 3:54 pm Chris Carini, @.***> wrote:
When I ran the above command, it ended up pointing to 'schlage', which was this Schlage integration (not the native one) https://github.com/mcnutter1/homeasssitant-schlage that was causing issues (specifically: mcnutter1/homeasssitant-schlage#23 https://github.com/mcnutter1/homeasssitant-schlage/issues/23).
Removing that and trying the upgrade again worked successfully!
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/109597#issuecomment-1937012727, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMGLT6PVJVNL5BTIPON46E3YS53XRAVCNFSM6AAAAABCYYNS26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGAYTENZSG4 . You are receiving this because you authored the thread.Message ID: @.***>
Updated to 2024.2.1 and issues appears to be resolved.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Ok, thanks.
On Mon, 04 Mar 2024, 1:10 am issue-triage-workflows[bot], < @.***> wrote:
Closed #109597 https://github.com/home-assistant/core/issues/109597 as not planned.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/109597#event-11991537517, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMGLT6MVM2DEFE4R7R7ZD63YWOUYDAVCNFSM6AAAAABCYYNS26VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRHE4TCNJTG42TCNY . You are receiving this because you authored the thread.Message ID: @.***>
The problem
not install core f## System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4859 Installed Version | 1.34.0 Stage | running Available Repositories | 1379 Downloaded Repositories | 7Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | March 2, 2024 at 2:00 AM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | true remote_server | us-east-1-9.ui.nabu.casa certificate_status | ready instance_id | c54ed697abf6419e868a6f14c49af2f5 can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 11.5.rc3 -- | -- update_channel | beta supervisor_version | supervisor-2024.01.1 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 219.4 GB disk_used | 14.0 GB healthy | true supported | true board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | Samba share (12.2.0), Terminal & SSH (9.8.1), File editor (5.7.0), eWeLink Smart Home (1.4.3), Studio Code Server (5.15.0), Nginx Proxy Manager (1.0.1), MariaDB (2.6.1), ESPHome (2022.3.1), Mosquitto broker (6.4.0), Node-RED (17.0.4), Whisper (1.0.2), Piper (1.4.0)Dashboards
dashboards | 1 -- | -- resources | 0 views | 1 mode | storageRecorder
oldest_recorder_run | January 25, 2024 at 12:25 PM -- | -- current_recorder_run | February 4, 2024 at 12:23 PM estimated_db_size | 152.39 MiB database_engine | sqlite database_version | 3.41.2Sonoff
version | 3.5.4 (a4a8c5f) -- | -- cloud_online | 0 / 2 local_online | 2 / 2Spotify
api_endpoint_reachable | ok -- | --Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4859 Installed Version | 1.34.0 Stage | running Available Repositories | 1379 Downloaded Repositories | 7Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | March 2, 2024 at 2:00 AM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | true remote_server | us-east-1-9.ui.nabu.casa certificate_status | ready instance_id | c54ed697abf6419e868a6f14c49af2f5 can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 11.5.rc3 -- | -- update_channel | beta supervisor_version | supervisor-2024.01.1 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 219.4 GB disk_used | 14.0 GB healthy | true supported | true board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | Samba share (12.2.0), Terminal & SSH (9.8.1), File editor (5.7.0), eWeLink Smart Home (1.4.3), Studio Code Server (5.15.0), Nginx Proxy Manager (1.0.1), MariaDB (2.6.1), ESPHome (2022.3.1), Mosquitto broker (6.4.0), Node-RED (17.0.4), Whisper (1.0.2), Piper (1.4.0)Dashboards
dashboards | 1 -- | -- resources | 0 views | 1 mode | storageRecorder
oldest_recorder_run | January 25, 2024 at 12:25 PM -- | -- current_recorder_run | February 4, 2024 at 12:23 PM estimated_db_size | 152.39 MiB database_engine | sqlite database_version | 3.41.2Sonoff
version | 3.5.4 (a4a8c5f) -- | -- cloud_online | 0 / 2 local_online | 2 / 2Spotify
api_endpoint_reachable | ok -- | --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
update not working
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response