Web UI won't load after crash during Lovelace tweaks

Installation Home Assistant OS
1

So I was editing Lovelace in the web UI. Rearranging tabs, editing name fields, that type of stuff when the connection dropped all of a sudden. I went to refresh the page and it wouldn’t come back up. I have it running as a Docker container so I restarted it. Still nothing. I can’t connect to the web UI over the local network or even from the machine that hosts it.

I checked the logs and see HA setting up various types of sensors and the normal “can’t connect to some device” that is no longer on the network messages. I’ve been running 0.108.1 just about since it came out with no issues. I’m out of ideas besides scrapping my config folder and adding my yaml files back one by one. Which I really don’t want to do. At different times I’ve tried renaming (in order to autocreate new ones) the home-assistant_v2.db file, .storage/lovelace, and .storage/core.config_entities. None of those single changes made a difference so I renamed them all back to their original names.

Any ideas? I would really appreciate the help.

TIA

2

If you use YAML mode just copy the lovelace.yaml file from a snapshot to your config folder and restart.

That’s not normal. If they don’t exist any more remove them from HA.

3

Thanks for the suggestion. It sounds like the .storage/lovelace file should be where the issues are.

A snapshot would be a good idea if I was smart enough to have made one. :man_facepalming:

And I should clarify, I meant “no longer on the network” as in temporarily turned off or not at home “for the moment”.

Edit: Looks like I misunderstood your comment, I’m not using Lovelace YAML mode. However, I’m still looking through the lovelace config to see if anything sticks out.

1 Like
4

If you move out lovelace from .storage, HA should start up again in lovelace autogen mode.

5

I moved it from .storage and it still isn’t working so maybe something different is going on and it was just a coincidence that I was messing with the UI Editor when it first crashed?

6

OK, leave it out of .storage, and rename your configuration.yaml to configuration.old. Create a new configuration.yaml with just

default_config:

in it. See if HA starts up now.

7

That worked! …kind of. It launched the Web UI and I can login. The only unexpected thing is that the main lovelace page that is now defaulted, is full of various sensors. I guess those are probably integrations that aren’t configured in my configuration.yaml so that makes some sense. I should be able to change my configuration.yaml back and check it for errors in the web ui before restarted it unless you have a better strategy. Thanks for the help!

Edit: I was able to also restore .storage/lovelace and my UI is back to normal but with a bunch of missing entities that a fixed configuration.yaml should clear up.

8

I would put piece by piece back in, and check configuration after each piece.

9

There were a couple things that were configured in YAML and also as an integration. I just removed them from my YAML and Home Assistant started working. I didn’t try testing with and without them in the configuration.yaml. I’m not sure why they started causing an issue but everything is working correctly now so I can’t really complain. Thanks for all the help.