Dear all,
I have an ODroid N2+ with Home Assistant on it.
I just start with it, so I don’t know much about it, but hope to learn from it, so it will happen that I don’t understand it immediately.
I if I say well, I have a tab … Unnamed View in my dashboard (see image)
Wanted to add a display and something went wrong but I don’t know how to get this away.
Is there anyone who wants to explain to me step by step and as frequently as possible how I can remove this display within HomeAssistant?
Click the 3 dots in the upper right corner. Click Edit Dashboard and you’ll be able to create, edit and delete the views.
I’ve got that same issue ‘UNNAMED VIEW’, and the standard edit wont work.
i’m unable select, edit, or delete it. When selecting the ‘UNNAMED VIEW’ it switches to the first header of that particular dashboard.
Even if i change any other header to the start of that dashboard, the UNNAMED VIEW option header will always select and change to which ether is the first tab of that dash.
hit edit in the upper right. Then in the upper right again pick the raw config editor. Find the block in that raw yaml that describes the view and nuke it.
If you aren’t comfortable, do a select all and copy it to a text editor as a backup. or if you can’t find the view, post then config yaml here and one of us can find it.
I just came back to post a solution and you beat me to it.
Like you said raw editor is key.
To quickly identify the dodgy buggy tab, i just created an easily identifiable tab either side of the problem tab.
For example
One named: XXXXXXXXXX
UNNAMED VIEW
The other: YYYYYYYYYY
Then just deleted the problem code in between.
Checking one of the new tabs code either side prior gave me a better idea of what should and what shouldn’t be left either side of the problem code.
Same here, using home assistant for the first time three weeks ago.
Created my own dashboard, added some cards on the first view and somehow got stuck with an uneditable UNNAMED VIEW.
I found this thread and was able to succesfully delete the view via the raw configuration editor.
I think it’s best to get this fixed as this seems not a single incident.
