Lovelace: blanc "Raw config editor"

I just tried using Lovelace when it was introduced into the updates a couple of days back. I like it, however it still looks quite complicated to me.

I’ve mentioned that the “Raw config editor” was displaying all the card in “yaml” style before. But since I liked to check something now, I mentioned that I just get a blanc screen.
All the cards and all the settings are still there however, but again a blanc screen once I open the raw config editor.
I’ve updated Hassio to the latest version today, and I’ve also tried restarting.

I’m not sure if it’s ok, but I even can’t find a “lovelace yaml file”. Can’t see such thing in the “config” map.

Annybody knows whats wrong here?

Edit:
Tried some restarts, with no luck, Next tried a complete schutdown, and reconnected the power.
First tried another option in the upper right corner, named “Unused entities” first. Really didn’t know what to do with this.
But when I tried “Raw config editor” then, the text was back. So I;m not sure if this was because of the power cut or the “Unused entities” option.

And still no “lovelace yaml” file to be found…

It’s in the .storage folder

Note the . Makes it hidden

1 Like

Do you use any custom cards? The custom-compact-header card had this issue in an old release.

Also try F12 (Chrome) in Browser and then right-click on the refresh icon and select empty cache and hard reload.

1 Like

Ah yes! Found it there, thanks for your help! :smile:

Maybe strange to ask, but is it also backuped there when making a snapshot?

Because I was playing around with lovelace when just rolled out a few days back, I messed a lot of things up and reverted back to a snapshot. But this messed up lovelace UI was still vissable after that. So just wondering :slight_smile:

1 Like

No custom cards, only the 24 presets given in Lovelace itself (well only using a few simple ones of them a.t.m.).
This UI is quite new to me (just as everything of Hassio :stuck_out_tongue: ) so just got into it recently.

Didn’t knew that F12 workaround, will try it. Thanks! :+1: