After adding the lines to configuration.yaml to convert to YAML mode, I thought all of my cards would convert over. Instead, they’re all in a red error state. How do I get them back since it seems switching to YAML mode is a global setting?
After switching to YAML mode and restarting, I expected to see a ui-lovelace.yaml file that I could start editing, but it’s not in the config folder. Is it somewhere else?
Never perform substantial work on Home Assistant without making a full snapshot (backup). This way if you hose it, you can simply restore the snapshot and your Home Assistant will be as if you never touched it. (I speak from experience).
I spent several painful days getting rid of my ui-lovelace.yaml- Why do you want to go backwards? Note that lovelace_gen that you linked to is more than a year old.
I took a recent snapshot, but also haven’t done anything irreversible (so far ).
I have the Tesla Custom Integration. This is about graphically depicting those sensors and switches as shown in the first link above.
I don’t want to go backwards (especially if this would be a global change precluding any further use of UI cards), but I do want the layout and functionality it seems is only achievable via YAML (at least for the Tesla card/panel. If there’s a better approach here in 2022, I’m open to that as well.
Lovelace_gen is definitely not for beginners. You need to have a firm undertanding of yaml, dashboards, and jinja.
The reason everything is red on your system is most likely because when you switch to yaml mode, you need move your resources from ui into yaml. I’m not 100% sure if this is still a requirement, but it was last I remember.
There is nothing “backwards” about yaml configurations.
It’s just a different way of doing things.
If anything using the UI is a more simplistic way of doing things and yaml is more advanced. So that negates your “backwards” comment.
Yes, using yaml mode the resources need to be configured under the “lovelace:” section in the configuration.
Yes, once you enable yaml mode for lovelace the UI is disabled.
But it’s not really that big of a deal. Yaml really isn’t as hard as some try to portray. And you can do the same things in yaml mode (or maybe more?) than you can thru the UI. especially if the card you want doesn’t support the UI editor.
OK, so it’s ui**(dash)**lovelace.yaml and it is required to get lovelace_gen to work (simply as a place to !include the actual .yaml files). That’s two less things I can stop researching
I did previously try that, but didn’t include the "views: " Here’s what I’ve got now in ui-lovelace.yaml:
I’ve kept the # lovelace_gen at the top of Test.yaml, restarted HA, and cleared my browser cache and I’m still getting the token error.
To check my syntax (since I’m still learning), I just created a new UI dashboard, added a Picture Elements card, and opened the Raw configuration editor. The only line I added to it was the type: panel line since that’s how I’d like the Test dashboard to render. It looks like this and it works.
Improve the lovelace yaml parser for Home Assistant (github.com)), but cannot make sense of my next steps.
).
