This happened to me once and clearing the data from the android app fixed it for me.
this post was submitted on 16 Jul 2023
16 points (100.0% liked)
homeassistant
12131 readers
17 users here now
Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io
founded 2 years ago
MODERATORS
Tried it, with no success. Searching for an server with no success
According to the error, core.entity_registry is corrupt. Is there any hint as to what line is causing the error? Can you try to paste the JSON in an online linter?
I’m wondering if the default configuration is finding something on the network that is producing this error. You could try starting home assistant without enabling the default configuration by omitting the line from configuration.yaml:
default_config:
Have you added anything to your network recently? By default I believe home assistant does auto discovery so it could be discovering something that is not fully compatible with.
The log provides some error messages on addons/extensions e.g. HACS, miele, Bosch etc but I assume they were standard due to note is only "these are not fully tested with Hass"
However I'm still confused that a fresh install didn't work either. And observer still works.
No new items has been added to my network.
I'll try a docker version fram another server and see if that works
Seems like someone has had this type of error before and the only way to restart HA was to remove the file. Though the issue wasn’t resolved but was perhaps fixed with an update. https://github.com/home-assistant/core/issues/85381
Docker version on synology works... Tried windows VM version according to home-assistant guide, no success but Observer works.
Supervisor logs indicates that home assistant has crashed and failed to restart.
view more: next ›