Struggling with copying Lovelace config from docker to hassio install

Configuration Frontend
1

I’m on 0.92 and I’ve been using HA under docker for a while but I’m getting jealous of all the great hassio add-ons, so decided to switch to hassio on generic Linux (still on Pi 3 though). I ensured my config files were all backed up, stopped/deleted my old Docker containers and images and used the script to do a hassio install. I stopped the new HA (and supervisor), copied my config directory (and everything under it) to the new area under /usr/share/hassio/homeassistant/ and restarted it.

I had been using Lovelace via the “Configure UI” method, but the new installation seems to be ignoring the .config/lovelace file that I’ve copied across. Instead I get lots of unallocated badges; and tabs that I created via the Lovelace UI editor are all missing. When I check the .storage/lovelace file, it still has the correct contents, but it is being ignored. If I use “raw config editor”, I see the basic file that has been converted from my configuration.yaml. Out of interest I saved it, and only then it does replace the .storage/lovelace file.

I’ve been trying various combinations of stopping HA, recopying the file and using incognito mode to ensure it’s not cached in the browser but not cracked it yet.

I assume I’m missing some file/setting outside of the directory structure I’ve copied over but I can’t think where that would be. I think this exercise has exposed some of my confusion over the different modes that Lovelace can be used in! Can anyone advise please?

2

I guess I could do this:

  1. Stop new hassio installation
  2. Reinstall & start a standard docker image (pointing to old config directory)
  3. Use “raw config editor” in old system and copy all the text
  4. Stop old docker installation, restart new hassio installation
  5. Use “raw config editor” in hassio installation and replace all text via paste

…but I’d prefer to understand what’s happening so I can fix it “properly” if possible!

3

Do you have:

lovelace:
  mode: yaml

in your configuration.yaml? It may be that is causing it to ignore your changes using the raw config editor?

4

Ah - just read you can save the default file so maybe not that.

I just use the lovelace.yaml file - I think it gives me a bit more control for things like floor plans.

5

Thanks. Yeah, I should probably move to the yaml file, just seems a shame to lose the ability to change things from anywhere. I need to work out how to fix this issue first anyway though!

6

After failing to find any other way to fix this, I’ve just gone with my thoughts on re-installing the old image and copying from its raw editor. When I then restarted the new install my Lovelace config was all magically in place! I guess this shows something happening in the browser cache…

It’s a shame I still don’t understand how this works enough to fix it properly, but at least it’s all OK for me now!