I have struggled with getting my family comfortable with the dashboards I have made in Home Assistant. With quite a few units and several rooms, the user experience easily gets too cluttered and overwhelming for them.
So now, I have spent some time trying to optimize the Dashboard.
I have tried to minimize and standardize, and have made one standard view to rule them all. I am also personalizing this view based on who logs-in, where I am using the build in condition functionality on card level, so each users only sees the cards/lights that are relevant for them. This works just fine.
However, from time to time a user needs to access the cards that by default are hidden from them. Currently I have solved this with a toggle box (See more…) for each section. At first glance this seems to do the trick. However, the toggle are system wide, so pressing the toggle will affect all users, this will confuse them if there are more than one user at the same time.
I have also looked for a way to reset the toggle between user sessions, meaning that when a user sets the toggle as true, it will remain so until someone sets it to false.
All in all, this means that the toggle aren’t quite as helpful as I wanted it to be.
So I am wondering if there are ways to solve this, or there are other way’s of achieving the same thing?
This is a screenshot of a user with default view (Se mer = See more):
I am already using conditional visibility of cards. That works great.
And I do not think collapsible cards quite is what I am after, since I hide rooms (each of my card indicates a room), not elements in a room.
My problem: How to solve it when users needs to access a room that by default are hidden. I am now using a toggle (boolean helper) combined with conditional visibility (if toggle = true then show all cards).
This is not a good solution, since a change in the toggle value will affect all users.
Since we do not have “per-user entities” - I am thinking about this (probably) possible way:
To hide/unhide card(s) - a button is used instead of checkbox (could be with labels “show more / show less”).
Pressing a button calls a script:
– find out which user called a script;
– choose a particular “input_boolean” entity - out of “show_expanded_john”, “show_expanded_jane” etc - dependently on a user;
– toggle this entity.
A card(s) uses a conditional visibility:
– choose a particular “input_boolean” entity - out of “show_expanded_john”, “show_expanded_jane” etc - dependently on a current user;
– if this entity ON → show a card(s).
Similarly - to set a label for that button.
Though I do not think these conditions (templates) are supported currently by stock cards.
