I had tried Lovelace on an earlier release but I wanted to remove it before upgrading to 86.2. I deleted ui-lovelace.yaml and checked that there was no file in .storage. However, when I browse to /lovelace, I still see the old Lovelace setup. If I upgrade to 86.2, this is what I get, not a clean setup.
I used the Lovelace Migration add-on to generate a ui-lovelace.yaml file, but I never set it as the default UI. So I assumed just deleting the file would give me a clean start to use the UI editor.
Maybe I’m misunderstanding the migration process here. I reverted back to 85.1 with no ui-lovelace.yaml or .storage/lovelace, and there are no lovelace entries in my configuration.yaml. I then click on Try Lovelace UI in the info panel and I get a Lovelace version of my standard UI with nothing changed. Is this correct?
If I then click on Configure UI I get the warning “By default Home Assistant will maintain your user interface, updating it when new entities or Lovelace components become available. If you take control we will no longer make changes automatically for you.”
I assume this means it is switching Lovelace to yaml mode which I do not want. However, if I click on take control, I get a lovelace file in .storage not a ui-lovelace.yaml!
If I then click on Configure UI again, I get the Lovelace config screen where I can edit cards, etc.
Thank you very much @flamingm0e for the clarification, one last question. Have I lost automatic updating of entities & Lovelace components as the message says, and if so how do I get it back?
If you want it back to home assistant doing it for you (why you would want that I have no idea), just shutdown home assistant and delete the Lovelace file out of .storage and start home assistant back up