Hey guys - I found somewhat similar, but not the same topics - so maybe someone here is smarter than me and can help:
I have two dashboards, one mobile, one for a wall-mounted tablet.
I’d like to have the mobile dashboard on several devices, but here comes the catch:
I want on a device that is at my home, some cards to be display and others not.
But if I’m at home, I’d like the other devices to not be affected.
Basically device is home = on this device a card is visible
Other device not at home = card invisible (at the same time)
What I don’t want, is to maintain as many different dashboards as there are devices.
I want one dashboard, being able to show or hide the cards just on the specific device, based upon it is at home or not.
Haha - I know this section - I use it also.
But, when I use it, it will make the specific card invisible for all of the devices.
But I want to separate between them.
You could do this if your create a separate user for each device. Then you can use that in the visibility condition (only show for user X AND when device Y device in home).
Please keep in mind this is not a security measure. There are always ways to access the entities even if they are hidden in the dashboard.
Just imagine, my GF and I use the same dashboard on her / my mobile.
I’m out - so why shall I see the buttons for certain mood-lighting?
She on the other hand might wants to activate them.
But as per my understanding - the only thing that happens: The dashboard will look “is device X at home” and then either show it or not - but not based on users and their position.
We’ve mentioned multiple times here, you can have a condition for a user, and you can have multiple conditions.
For example:
User X and X state is away
Or
User Y and Y state is away
So the card would only show if either of those two sets of conditions are true. So if you open dashboard and you are home, neither of the conditions are true, so you won’t see the card
I think the code runs on the server, but that is an implementation detail that doesn’t affect the outcome. Just because the conditions are evaluated on the server side doesn’t mean the visibility is then set to be the same for all users. That’s the whole point of the “user” condition. It enables or hides the card for the specific users.