Per the release 0.84 release notes, there are three Lovelace modes. It’s not clear from the popup window which mode you’re entering when you click on “take control.” I believe the release notes indicate this is Storage Mode, but the " Take control of your Lovelace UI" notice has no mention of “Storage Mode” in the text below.
Should this text be updated to make this clear that clicking on “TAKE CONTROL” will move the user into Storage Mode?
Take control of your Lovelace UI
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.
Are you sure you want to take control of your user interface?
Also, is it possible to go back to auto-generated?
However, there are some good reasons I’ve seen to move to yaml (custom cards, e.g. the new thermostat isn’t easy to use), so I’ll probably be doing that in the near future myself.
Just tested my theory & it seems to hold. The setting lives in the DB, so go to your HA folder, kill the HA service, then remove the DB (home-assistant_v2.db) and restart the service.
As an FYI, the lovelace config/yaml is kept in your HA folder under .storage folder. It’s a file called lovelace with no extension. So removing the DB to reset and/or manually editing lovelace config/yaml is all still very possible while still having the nice UI editing ability.
I am new to HA, though I have been at it for several weeks having gotten Samba, DuckDNS and WiFi working. Now I want to look at the Lovelace front end and begin replacing my ADT security system. I don’t want to move counter to Lovelace future development.
When clicking on “Configure UI”, what does it mean when it asks… are you sure you want to take control? When I take control, I then see all the available cards that I have been reading about and a raw editor.
How does one revert back to NOT “Taking Control” after you had taken control? I am guessing it would be simple for me since I have not actually configured anything after taking control, but not sure.
If I do not “Take Control” of the UI, can I still implement (for example) an IFRAME using windy.com without breaking Lovelace Automatic UI?
Forgive me if I don’t really know the right terminology to use here, since I am new at this.
To take control or not to take control… that is the basic question. Which way is recommended long term to stay in line with HA future development? Then I’ll stick with the recommendation and learn the ways.
Not taking control: HA will manage your UI (Automagically add/remove stuff)
Auto Mode
Taking control: You decide what you see and how you want to see it.
This has two modes
Storage mode (default after taking control)
You can now use the UI editors to manage your UI.
Popular believes say that you cannot add custom cards with this, that is a lie…
You can add custom cards (resources) by using the raw editor in this mode.
The configuration is stored in a json formatted file in .storage/lovelace (be careful if you manually change that)
YAML mode
If you prefer YAML over UI editors you can enable YAML mode and you manage it by editing the ui-lovelace.yaml file in the root of your configuration directory (same as configurtion.yaml)
To enable this you need to add this to your configuration.yaml file:
lovelace:
mode: yaml
After you have added that you need to restart HA for it to take effect.
Yes funny story. Mostly working through/ struggling getting all the neat new things I see people doing here and not paying allot of attention to the front end. Decided last week to start playing with cards by “taking control”. Thought that’s neat but I need to come up with how I’m going to use this so delete all my test cards. A week later put in a new automation and its not showing in the front end. Spend 40 mins trying to figure out what’s the matter. Something wrong with the automation? Is it something to do with the line in customize that I had to put in to get the all automations to show in a separate view? Eventually I remembered and figured out that the new entry would have to be defined manually in a Lovelace file. Eventually found that file and cut it out after looking at the formatting briefly and noping the heck out of there.
No complaints… Just a funny story… And how it is easy for a technological enthusiast with a lack of true understanding to get tripped up
and the