Yup All of mine are listed there too.
I knew I wasn’t imagining things. I thought there sed to be a tab at the top of (probably) the dashboard page.
HA is always burying things deeper and harder to find.
1 Like
Yeah my observation is that it has almost become a race to the bottom.
There seems to be a bit of an obsession with trying to make HA approachable to ‘everyman’, which I fully understand and support.
Sadly it seems to be at the expense of alienating people like me.
Hey, ho…
1 Like
I don’t even have a dashboards.yaml or any lovelace dashboard coding in my yaml. Just looks like:
## Lovelace section
lovelace:
resource_mode: yaml
resources:
- url: /hacsfiles/battery-state-card/battery-state-card.js
type: module
- url: /local/mini-graph-card-bundle.js?v=0.12.0
type: module
- url: /hacsfiles/lovelace-mushroom/mushroom.js
type: module
I guess this is normal?
if you used mode: yaml before, you were using a file named ui-lovelace.yaml to configure your dashboard. That file still exists and has not been altered.
If you want to continue to use that dashboard, you need to add the yaml to make it appear in the dashboard list in your 2nd image. From there, you can set that dashboard as the default dashboard. Just keep in mind that the URL you used in the past will no longer be the same, it will now have a new URL. You’ll need to close browsers (or click the dashboard on the sidebar) and refresh your bookmarks in whatever browser you’re using.
You’ve said that elsewhere but I’m pretty sure that’s not correct.
the URL for my original dashboard is exactly the same as it was before as “http://192.168.1.11:8123/lovelace/0”. I verified it by logging in in an incognito window as well.
the new overview dashboard is “http://192.168.1.11:8123/home/overview”.
I didn’t need to change any bookmarks/references anywhere.
Your new url is going to be set however you set up your new yaml dashboard. E.g. I used this:
ui-home:
mode: yaml
title: Home
icon: mdi:home
show_in_sidebar: true
filename: ui-home.yaml
so my url is ui-home/home puilled from the slug ui-home and the title home.
No matter how you use it, the lovelace/0 url is what is deprecated and will not work. It should always redirect to the new auto generated dashboard.
That may explain your post in the release thread with the odd behavior FYI
the lovelace/0 url is exactly what is shown on my incognito window and works navigating to and from.
here is my config:
lovelace:
mode: yaml
filename: ui-lovelace.yaml
title: Overview
icon: mdi:view-dashboard
show_in_sidebar: true
Sorry for the double reply…
but no I didn’t do the incognito mode until after that post.
Go to 192.168.1.11:8123 without filling out the rest of the url in a new browser and log in and it should redirect you to your default dashboard url which should be lovelace/overview based on your config.
sidebar: You could be running into these odditites because your dashboard is labeled lovelace:. I did not go that route because the repair during beta was completely different.
Nope. I just did it.
opened a new incognito window, typed “192.168.1.11:8123” with nothing else after it and redirected straight to the above URL in the screenshot.
Interesting. I’d wager there’s an issue then with using the lovelace slug. The lovelace\0 url for me (not using any lovelace slugs) always redirects to the new autogenerated home dashboard, not my default dashboard. Regardless how I log in, HA always redirects me to ui-home/home
Oh I think I see it.
As referenced in the docs to get the exact same functionality as before you do have to create a dashboard called “lovelace:”. Yours is using a different dashboard (ui-home instead of lovelace) but directing to use the same old “ui-lovelace.yaml” as the file. So your dashboard URL is probably different due to that change.
Yeah, because during beta none of that stuff was found yet. So I updated my dash before they fixed things and now I just live with the change. They must have added the lovelace/0 back as a url redirect. It didn’t exist early betas. Good to know though.
However, I do think you should document the oddities you ran into on desktop. That would explain why you saw them and I didn’t.
Document it where?
I think I already put all the info I had into that post in the release thread. If they need any other info then they (whoever they are) can PM me and I can give whatever else they might need.
I meant, create an issue
I only installed Home Assistant this week and added HACS and mini-graph-card. However this update has broken my links to mini-graph-card, I have updated the configuration.yaml to look like this:
lovelace:
resource_mode: yaml
resources:
- url: /local/mini-graph-card-bundle.js?v=0.13.0
type: module
dashboards:
lovelace:
mode: yaml
filename: ui-lovelace.yaml
title: Overview
icon: mdi:view-dashboard
show_in_sidebar: true
But even after reloading and clearing everything I still get
Configuration error
Custom element doesn't exist: mini-graph-card.
I have tried reinstalling mini-graph-card, and looking for ui-lovelace.yaml which I cannot see.
Yeah, I figured that’s what you meant.
Unfortunately I don’t see this as an issue that’s going to get a lot of attention.
I’d hate to spend 15 or 20 minutes (more time) creating an issue that literally just duplicates what’s already in the release thread just to have the issue languish until it gets closed or it auto-closes like the few other issues I’ve created.
I’m not sure it’s worth the effort TBH. If there is interest in looking into it then the info is already there and a PM is always an option.
How did you install the mini-graph-card?
if it’s thru HACS as you noted then the link to the card js file is wrong. it should be:
- url: /hacsfiles/mini-graph-card/mini-graph-card-bundle.js
type: module
all HACS downloaded files are in /hacsfiles/…local is for manually installed resources that you define where they are located.
ui-lovelace.yaml is located in the same directory tree level as configuration.yaml.
1 Like
Amazing. Thanks! I don’t know why it was working before the update and not now, but working now.
1 Like