Allow all admin of home assistant to choose the default dashboard for all users. This would be similar to the set default theme. This would be great for migrating to dashboards, etc.
There are a bunch of settings currently lumped into the āuser profileā page that donāt belong there. This is definitely one of them.
Default dashboard is currently a per-browser client setting, not a per-user setting.
This allows different dashboards to be set for devices like wall panels vs mobiles.
I guess with continued improvement to the frontend (sections) this may become less of a need. Also a user could be created for the wall panel.
But that wouldnāt really solve this problem. the admin would still have to physically have access to the device to switch the default dashboard. not a problem on a wall panel but on a mobile device that might be practically impossible.
example -
I wanted to give my mother who lived in texas access to a dashboard with limited functionality to only provide an indication if I was home or not, access to my work calendar and a ābuzz meā function in case Iām not at my phone if she needed me in an emergency. I donāt live in texas so I have no access to her device to set her default dashboard from the device.
But I could do that with the old Compact Custom Header integration but that no longer works.
What Iām surprised about is the dev who wrote CCH works (or worked) for NC so I would have thought it would have been trivial for them to add all that functionality to core. But instead it was completely abandoned.
I meant if this FR was actioned. Then a way would still be needed to assign a dashboard to a device like a wall panel. That was my solution.
I voted for this, because it shouldnāt be as hard as it is. You can however take control of the real default dashboard to make it what you want. Regardless if it is yaml or gui built. If you want to keep a autogenerated dashboard too, you can create that separately. So it is possible to have the dashboard of your dreams as the global default, without losing anything. But having an option to set it would be a lot easier.
A per-user (persistent) default would be a vreat addition, the current one is quite useless to me, because it is regularly needed to flush the front end cache. This also clears the current default, which makes it annoying. As said, if you have a user default, then a device specific setting is less needed, because you can create a use to log in on that device.
Iāve spent 2 days trying to figure out how to set a default dashboard to a custom wall panel user I made. Having ādefault dashboardā be stored in a specific browser cache is not a great solution unfortunately.
I was doing all my testing on my main computer which obviously isnāt the same thing as the wall panel. Then after switching to using the wall panel, it would just get reset all the time. And I have two panels⦠And I have made users for other residents that I wanted to have custom controls for them, and, and, and⦠like another dozen issues would be solved if there was simple a āDefault load this dashboard for this userā¦ā option