I am not sure if this will require a new feature request to accomplish or if there is a way to do it in hte frontend YAML files. My desire is to stay with the standard frontend rather than a custom frontend.
I currently use Views to logically group cards for areas of my house. I have a “navigation” glance card that lets the user select which room they want to control and the UI navigates to that view. Each view has a copy of the navigation card on it, so all views can navigate easily to all other views without having to scroll across the top bar. The challenge is maintaining the “navigation” card is a pain since there are multiple copies of it. Each time I make a change, I have to recopy the card to all views. I would be nice if there was a way to link a card on a view to a card in another view such that I only have to maintain the card in one location.
Similar to this, with the advent of user and dashboards, I would like to setup dashboards for each user so they only see the areas that they should. I would like to be able to either link to either cards or views in other dashboards to avoid having to maintain in multiple locations similar to the view challenge above.
An alternative might be to use dashboards for each room and do all navigation on the left hand menu. This way I could limit what dashboards are shown on the left hand menu for each user in their profile. I am not sure if this method of navigation will be acceptable to my other half. Any thoughts or comments would be welcome.
I know that you said no custom, but with the custom button card, you could define one template that you use everywhere. The navigation card on each view would then just be three lines that are the same everywhere.
If you’re using the ui mode you may have to define a new template for each dashboard, but you may need to do that per user anyways given your desired user based functions (although those could be templated too…).
Thanks @lonebaggie, my primary use case for control is on a phone which is why the view menu falls short (11 views requires scrolling across the screen to get to the ones on the right hand side). That is why I use a glance card for navigation with tap action to go to the desired view. It works well, biggest challenge is maintenance on the navigation glance card gets tiresome since I have to change it on every view.
Thanks, I will take a look. I was trying to avoid the custom cards just due to the rate of improvements in HA and Lovelace and having to take on additional work with breaking fixes, but this may still be the best way to go.
You can hide the view menu. I have 27 views . If you split each screen into a separate yaml . You can call them from the glance card and hide them in the menu
To go even further in the duration that you don’t want, you could use the browser mod integration to make a popup.
I mention this because the popup consists of cards, and on mobile the cards look essentially like a view. You then navigate back to “home” by just pressing the x in the upper left corner, so there’s no replication of the navigation feature, it would only exist in the only view.
How did you do that? I think that is all I need for my 9 views. I am limited in my skills and understanding on how I would go about the other recommendations in this thread and I assume what you did would be the easiest for me.
I just solved this in a different way. first we need to install kiosk mode from HACS
for a whole page that appears in multiple dashboards:
create a dashboard that do not appear in the side view, with one page that has all the cards…
than in each dashboard that the page should appear, add a page set it to panel mode, add a single card with iframe that links to the single page dashboard with “?kiosk” at the end of the url. just browse to the page copy the url from browser abd add “?kiosk” similar to:
“http(s)://domain or ip:8123/lovelace-(dashboardname)/(page-name)?kiosk”.
for a one card that appears in multiple dashboards:
same steps just the dashboard will have one card. then the iframe in the host dashboard needs hight adjustment … only downside (kinda) the is an extra border around that card …
Maybe it’s an offtopic question, but as it could solve my problem i’m going to aks it anyways:
Is it possible to include a yaml file of a single card the way you showed with inlcuding the views?
Can you please elaborate a bit more on what you mean by “yaml mode only” in relation to Dashboards?
For my usecase, I would like to keep the same badges across multiple dashboards/views, so being able to use badges: !include "badges.yaml" or even for cards cards: !include "cards.yaml" would help a lot to declutter my dashboards.
