Maybe an stupid question.
With the use of Hassio there is now a standard lovelace view. But is there a possibility to create a second lovelace yaml to make a real lovelace page for testing and to keep the standard?
So you keep the standard view, and in addition you create a new lovelace page. Will this work with the configuration page? Or do you have to change this always in your config yaml with the line lovelace: so you set the view default or by lovelace?
Yes it’s difficult to explain and I know there are more views possible in Lovelace.
But when you start with HA you have the normal page that’s now is lovelace as default.
So no edits with lovelace.
But I really mean can you create an seperate page with all the lovelace customizing possibilities what you can edit.
And always return to the default view without editing your lovelace page.
sorry I really don’t understand what you’re after.
By default you have a lovelace view that shows all your devices.
Do you want to create a second page with all the devices / a clone of the first page but customise it?
Just leave the first page (default page) as it is. Create a second one and do your testing. If your new creations are wanted on the first (default page), just move the single items to it.
I just insert another view and add the cards I want with the entities I want.
This is all done from hand editing the ui-lovelace.yaml
I guess he’s looking for a way to do it from the front end ?
Can anyone explain to him how that’s done ? (I’ve never even tried it)
Well sorry for the explaining.
But yes that’s sort of an idea to do yes.
But what is the default page yaml? Because for now i don’t have an lovelace yaml. And when i create a second love lace page should I use then in configuration lovelace: with an specified page name?
I think Dennis want to keep the autogenerated default Lovelace page and add new manually built as additional view.
And no - you cannot do that. The minute you take control of the UI you lose the autogenerated Lovelace view.
But the autogenerated quickly becomes a big mess so you do not really want to keep it once you get started. And the Unused Entities is a great tool to pick new things you add and move them into your views.
1 Like
Thanks Kenneth
Indeed I wanted the autogenerated page as default and wanted to use an lovelace page for experiment to test different lovelace futures for building an home screen.
But as I understand that is not possible.
But what is for now the autogenerated default page? This is not an yaml file that I can find.
Lovelace doesn’t write to any yaml files at all. Look in your hidden .storage directory located in your /config directory. There should be a file called lovelace that is JSON formatted