-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
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.
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
2024.2.0 not starting for unknown reason #109908
Comments
Do you have hikvision_next installed? |
I have exactly the same issue after pulling the 2024.2.0 image. |
same problem. Yes, hikvision_next are installed. |
Same problem. |
The hikvision_next config entries should be removed and someone should create an issue at hikvision_next repository |
We got this issue during beta, but the guy didn't need the integration anymore and I didn't have time to file an issue |
I also had a similar error with my Home Assistant, but I am not using hikvision. I see that it's an ip camera integration... I am using a custom integration for my doorbell which is Eufy home: https://github.com/fuatakgun/eufy_security Here are my logs, for what they're worth:
|
Same issues this is my log... 2024-02-08 10:14:51.561 ERROR (MainThread) [root] Uncaught exception |
Same issue here, I do also have hikvision_next in custom components |
I have the same issue, however I do not have hikvision integrations. |
same issue . I have the next add-on moved the integration elsewhere but still failing on boot. error parts of logs are as follows but can't see anything in it pointing to anything I recognise
|
Same issue, i'm using the docker image... |
Everyone who uses the Hikvision, please stop posting as we know it's an issue. For the others, I'll cook up a script with which we can identify the integration you're struggling with |
jq -r '.data.entries[] | select(.unique_id | type == "array") | {unique_id, domain}' /config/.storage/core.config_entries |
If you execute that, it will note down integrations which have an unique_id setup incorrectly |
Mine was |
Do you use a custom integration for this? |
I believe I am using a built in integration: https://github.com/home-assistant/core/tree/dev/homeassistant/components/schlage |
Can you please confirm this? Does Did you use a custom component for schlage before you migrated to core? When did you install schlage? Cc @dknowles2 |
I'm fairly confident the schlage integration has always set |
@jcarr Can you maybe post the output of the command so we know what the unique_id was? |
I'm having the same issue as well after attempting to upgrade to v2024.2.0 using a docker container image.
I do have a custom component for Schlage (I believe there was a reason for this?) (https://github.com/mcnutter1/homeasssitant-schlage) root@Server:/mnt/zfs-nvme/docker/homeassistant# ls -lart custom_components/schlage/ |
The problem
Just updated my docker container to latest version - 2024.2.0 from 2024.1.6 and getting the following error in docker logs:
container keeps restarting.
I guess it might be some custom integration I have enabled, but no idea which one. The information is so vague, so I cannot even know where to dig.
What version of Home Assistant Core has the issue?
2024.2.0
What was the last working version of Home Assistant Core?
2024.1.6
What type of installation are you running?
Home Assistant Container
Integration causing the issue
No response
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
The text was updated successfully, but these errors were encountered: