Lovelace - can I update and not use it (without too much faffing)?

Configuration Frontend
1

Hey,
I have a large-ish config now, with many groups (and subgroups), includes, packages, secrets and such. I want to stay up to date with HASS versions, but can’t find clear info on how to keep my setup running as it is in the GUI. I’ve read, in various places, how i can:

  • just let lovelace ‘do it’s thing’ and my GUI will look the same. I have my doubts.

  • click on the ‘i’ in developer tools and click ‘run states gui’ (or words to that effect). I can’t see whether that’s device-centric, or will apply to my whole config with one click.

for claritys sake, can anyone offer advice (from experience) on how to disable lovelace as default, globally, simply, and successfully.

I want to use the benefits of lovelace…at some point… but just not right now… :slight_smile: I also accept the tinkerer nature of HASS, and accept that breaking changes occur, usually for the greater good. I just don’t want to lose a weekend rebuilding a GUI that currently works for me as it is.

If i’ve missed an obvious topic/announcement on this, feel free to mock me and point me to it!

2

If you are currently using groups to organize your frontend, it will just convert that over to lovelace

it’s device-centric. I wouldn’t go this route though. I’m going to guess that this option will eventually be removed from HA.

why?

3

thanks for the response.
why do i seek a clear explanation of a method from someone who has used it themselves? to allow me to follow the instructions and move on with my life, and also for future forumites’ benefit.

re:groups - i use groups with view: true for the ‘tabs’ on my GUI. Are you saying that these groups will maintain there structure and contents?

4

you were asking how to disable lovelace globally. I asked WHY.

Yes. When you upgrade it converts YOUR groups config to lovelace and it looks just like it did before.

5

thanks for the clarification. Sorry if i wasn’t clear with my language. I used the work globally in reference to the ‘per-device’ method in dev tools.

wohoo! thanks @flamingm0e

6

However…

At that point I think you need to start using the lovelace editor (either thru the GUI or the raw editor or using yaml mode) to make changes.

Does anyone know if you can continue to make changes to your groups just as with the old ui and the lovelace auto-config will continue to catch those changes and update lovelace or is it a one time and done conversion process?

I use yaml mode so I’ve never needed to worry myself with that stuff.

7

As far as I know it’s a one pump hump

8

That was my understanding too.

9

This is gold :rofl:

10

this setting is per device - it’s stored on your browser cookies.

Once you have set it to ‘states’ then it should always use the older Polymer UI on that device from now on.