Suddenly the URL times out to home assistant we gui, same with android app.
I’m running HASS on an virtual box in windows 11, and tried directly to add a new fresh Debian Virtualbox, but ended up with same result without changing any settings.
According to the observer URL everything is fine, but it seems the heat pump logic isn’t running.
According to home-assistant.log.1 it seems there is an issue with
“could not parse Json content in core.entity_registry”
Any ideas? Due to above issue should not be an issue with an fresh installation!?
This happened to me once and clearing the data from the android app fixed it for me.
Tried it, with no success. Searching for an server with no success
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
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.
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?