So custom_updater will download the new files just fine, but it won’t update the config file to reflect the new version. So you have two choices, well, three really:
Stop using custom_updater and do everything manually
Use custom_updater and manually change the version strings when a card is updated (Using the “Edit Raw Config” option).
Use yaml mode for lovelace, then everything works as it did before, but you lose the ability to use the GUI lovelace editor
Thanks… Makes sense.
I don’t know yet, whether I should go with one or the other.
I’ve added the yaml config to the configuration.yaml file.
So for now I still operates the ‘old way’.
If I wanted to test the new GUI, could I then just remove the yaml conf line and then test it, and then if I want to go back just add the yaml line in the conf again?
I did try to check if there was some screenshots or videos of the new gui and how it works. But unfortunately I haven’t been able to locate it.
Yes. Just remember when you go back to yaml mode, any changes you make in the ‘new’ .storage will not be reflected in the old yaml file - you will need to manually add them. When you switch from yaml to the new .storage, you can copy and paste the whole old yaml file in again in the raw editor and it will recreate the correct .storage file.
The most practical way is to pick one approach and stick with it. It seems to me that the new config is the future so I’m sticking with storage.
Exactly. I was just nervous that if something went wrong that I wasn’t able to go back, at least during the transition.
Will give it a shot, and then I will just manually edit the version string in my custom components. Just a routine that needs to be added.
Which could be the name of the two images? I renamed them weather-background-above_horizon.png and weather-background-below_horizon.png but they don’t work…