Creating a user for each device is just plain dumb

If you set your phone to one dashboard and your wall tablet to another, they’ll now both revert to the default dashboard. If you want your wall tablet to use a different dashboard than your other devices, we recommend giving it a separate user profile

This is a very dumb idea, and I’m stating it mildly. So now the plan is that users have defaults that fit hardware, but every user can own only one bit of hardware. What is next? Light bulbs have a default brightness after a power failure, but if you want to set two bulbs to different values, do you need to create two users?

The way to do this correctly is to have a DEVICE PROFILE. The size of the screen goes with the device, not with the user. One profile per device. You can have user profiles, but you do not put things in the user profile that change depending on the device that the user happens to be using.

2 Likes

Feature requests will only be seen here:

I would not call this ‘dumb’ but just being a view on how to do things.
Not too long ago each device could differ, when I looked at HA on my iPad I had a different view vs. my laptop or my phone…which tbh I did not like…so I am very much happy with the current approach but I understand your view too, just donot call it ‘dumb’. I personally like the profile-alike approach and at present this is the user-id…things will improve over time but there are choices to be made and only that much time to spend.

That is your opinion and you’re fully entitled to it.

No one is saying that.

Strawman arguments don’t belong here, or anywhere else for that matter. Please stick to the argument you have an issue with.

If you haven’t realised yet, I happen to agree with the direction HA is going; recommending separate users per device. If one of your devices gets compromised or acts funny, you can simply delete the user or lock it down to local access only.

Want to restrict views & dashboards to only a subset of users? The Visibility tab on each dashboard card allows you to hide/show them based on the user currently logged in. No more admin access required for a tablet which sits in your house to display primarily weather data.

Sure, it requires more one-time effort on your behalf, but the pros definitely exceed the cons, in my honest opinion. 15 minutes of setup gets you granularity of which devices should have which visibility. Given that RBAC has been a long time coming, I feel this is a step in the right direction.

2 Likes

It is not an user profile per device, but an user profile per use case.
You could probably use the same user profile on all your in-house general purpose screens as long as they are doing the same thing.

1 Like

So we have three virtual users:

  1. Mary-who-looka-at360x480-screens,
  2. JimBob-who-likes-4K_monitors,
  3. Ann_with-her-640x1014-screen

None of those three people exist, you just made them up as a workaround.

The web design community solved this problem years ago with what they call responsive web design (RWD). What you do is when designing their display, you embed rules that say how many columns of tiles to use based on the width of the physical display, or maybe you say “center this within the available space”.

Could you imagine if “dogfood-r-us.com” had to create a user for every possible size screen? That would be a nonstarter. This is why the problem was solved a long time ago.