Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

core not installing #109597

Closed
HughMac01 opened this issue Feb 4, 2024 · 23 comments
Closed

core not installing #109597

HughMac01 opened this issue Feb 4, 2024 · 23 comments
Labels
needs-more-information stale
Milestone
2024.2.0

Comments

@HughMac01
Copy link

The problem

not install core f## System Information

version core-2024.1.5
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.11.6
os_name Linux
os_version 6.1.63-haos-raspi
arch aarch64
timezone Africa/Johannesburg
config_dir /config
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 7
Home 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 ok
Home 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 storage
Recorder
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.2
Sonoff
version 3.5.4 (a4a8c5f)
cloud_online 0 / 2
local_online 2 / 2
Spotify
api_endpoint_reachable ok
eb 2024

What version of Home Assistant Core has the issue?

System Information version | core-2024.1.5 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.11.6 os_name | Linux os_version | 6.1.63-haos-raspi arch | aarch64 timezone | Africa/Johannesburg config_dir | /config
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 | 7
Home 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 | ok
Home 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 | storage
Recorder 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.2
Sonoff version | 3.5.4 (a4a8c5f) -- | -- cloud_online | 0 / 2 local_online | 2 / 2
Spotify 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
@mib1185
Copy link
Contributor

mib1185 commented Feb 4, 2024

since you got these system, information (which also shows you are on core-2024.1.5) i'm not sure, what your issue is?

@HughMac01
Copy link
Author

HughMac01 commented Feb 4, 2024 via email

@mib1185
Copy link
Contributor

mib1185 commented Feb 4, 2024

there is not 2024.2 released, yet. or do you mean the current beta 2024.2.0b4?
if yes, how did you download it?

@MaBeniu
Copy link

MaBeniu commented Feb 4, 2024 •
edited
Loading

image
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

@mib1185 mib1185 added this to the 2024.2.0 milestone Feb 4, 2024
@mib1185
Copy link
Contributor

mib1185 commented Feb 4, 2024

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.

@MaBeniu
Copy link

MaBeniu commented Feb 4, 2024

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

@MaBeniu
Copy link

MaBeniu commented Feb 4, 2024

new beta came in 2024.2.0b5 however result is the same with the same error outcome

@joostlek
Copy link
Member

joostlek commented Feb 4, 2024

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?

@MaBeniu
Copy link

MaBeniu commented Feb 4, 2024

config.txt
location, addresses, names, passwords and tokens replaced with 'hidden' word.

@joostlek
Copy link
Member

joostlek commented Feb 4, 2024

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.

@MaBeniu
Copy link

MaBeniu commented Feb 4, 2024 •
edited
Loading

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?

@joostlek
Copy link
Member

joostlek commented Feb 4, 2024

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.

@joostlek joostlek closed this as completed Feb 4, 2024
@HughMac01
Copy link
Author

HughMac01 commented Feb 4, 2024 via email

@joostlek joostlek reopened this Feb 4, 2024
@joostlek
Copy link
Member

joostlek commented Feb 4, 2024

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?

@mib1185 mib1185 mentioned this issue Feb 7, 2024
Closed
@gambit66 gambit66 mentioned this issue Feb 7, 2024
Closed
@riddik14
Copy link

riddik14 commented Feb 7, 2024

My error starting from module six.moves

@alanburchill
Copy link

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

@HughMac01
Copy link
Author

HughMac01 commented Feb 8, 2024 via email

@joostlek
Copy link
Member

joostlek commented Feb 8, 2024 

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

@ChrisCarini
Copy link

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: mcnutter1/homeasssitant-schlage#23).

Removing that and trying the upgrade again worked successfully!

@HughMac01
Copy link
Author

HughMac01 commented Feb 10, 2024 via email

@alanburchill
Copy link

Updated to 2024.2.1 and issues appears to be resolved.

@issue-triage-workflows
Copy link

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.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 3, 2024
@HughMac01
Copy link
Author

HughMac01 commented Mar 4, 2024 via email

@github-actions github-actions bot locked and limited conversation to collaborators Apr 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
needs-more-information stale
Projects
None yet
Milestone
2024.2.0
Development

No branches or pull requests
7 participants
@ChrisCarini @joostlek @alanburchill @mib1185 @riddik14 @HughMac01 @MaBeniu