The difference is, yāall keep doing it every release. You canāt act like you havenāt. Just look at every blog post, any minute frontend change brings out the same people.
So yeah, Iām going to call you out.
It would be one thing if you said your complaint and moved on, but yāall canāt do that. Ya have to make multiple posts about the one feature.
I had two. One with a late āagree, dumb ideaā after lots of others have written it and one was only about, that I think that you are canceling others with your multiple reply to others, who donāt like it either, that āthousendsā of others requested the new behavior. For me this canceling of other opinions is not, what a mod/admin should do. My opinion. And this time, there were really a lot of long using users mentioning the same.
In other release threads and this forum in general I had no complaint anymore now for a longer time. Because of this Monty Pythons Jehovah behavior here nowadays. Another proof, that you are not balancing anymore but only biting around if someone is writing anything, Really not a good direction.
More than one post is one post too many. Itās not canceling ideas. Iām making sure you and others who canāt take a hint, move on. You donāt like the feature, make a single post about it and move on. Itās not complicated. Donāt create a circle jerk.
This worked great, thank you.
Appreciate it has already been said, but for the purposes of adding to the feedback, this doesnāt appear to be well thought out for the existing users that relied on it. Totally understand why some may prefer a default dashboard for their user account across every device, but this could have been an optional override - it wasnāt a broken, legacy or redundant feature that warranted removal. Hopefully thereās room for both in a future release.
please check this if you want your device-specific default dashboards back.
FYI I have opened an issue on the Frontend repo asking whether they will accept a PR in relation to this - I saw your other post about how it could be resolved so it prompted me to ask them, I figure best get a feel first for the kind of decision this change was (i.e. pray I do not alter the deal further). On the surface I feel both the new and old functionality can comfortably coexist.
My thought would be to expand on it a bit so that the global default is an override (or vice-versa) toggle. Iām not a great developer but letās see how it goes, very open to assistance.
After closer look, it appears theyāve re-purposed existing ādefault dashboard selection controlā to serve as user-default selection. So it might be slightly more complicated than it looked at the first glance to marry old and new approaches together, but still totally possible.
In general, as most of the people agree here, having systemDefault > userDefault > deviceDefault hierarchy where each next level (when defined) takes precedence over previous levels should be way to go.
Yep sounds good, I hadnāt put enough thought into it yet but that makes more sense and is a better approach. Have updated the issue to reflect, hopefully can get things moving.
Thanks for the fix in the meantime, appreciate it.
Havenāt found anything yet, tried with removing all the HACS plugins but didnāt solved. Have wrote a message in Discord now: Discord
Snow is Awesome!
Make this triggerable with an automation and add others like rain, falling leaves, wind (how do you display something you canāt see? )
Very nice to see on a kiosk dashboard as a visual representation of the weather.
The permissions topic is also important for me. Especially the usage of dashboards and menus should be handled by permissions. To setup permissions on an entity level seems to me very complicated.
Most cases I consider mean, that restricted users should not be allowed to configure things. They should get predefined dashboards.
I understand, if it comes to speech, this may not be sufficient.
Is the plan to provide a simple GUI to setup permissions?
Layered security on HomeAssistant is but a distant dream.
Please add buttons to the top bar in the automation editor for switching between YAML and UI modes, and for running the actions! (like the existing āTracesā and āEdit automationā buttons)
Thanks!
Iām not seeing how to set a default dashboard per-user. Where is that setting? Itās not in āUsersā as far as I can tell.
Has anyone had issues with the TP-Link Router integration with latest update? I get a failed to setup. Logger: homeassistant.config_entries
Source: config_entries.py:761
First occurred: 4:17:46 PM (2 occurrences)
Last logged: 4:36:48 PM
Error setting up entry http://192.168.68.1 for tplink_router
Traceback (most recent call last):
File ā/usr/src/homeassistant/homeassistant/config_entries.pyā, line 761, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File ā/config/custom_components/tplink_router/init.pyā, line 54, in async_setup_entry
firmware, status, lte_status = await hass.async_add_executor_job(TPLinkRouterCoordinator.request, client, callback)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
asyncio.exceptions.CancelledError
I am happy to see a lot of you is commenting on the same. Itās a real quality of life drop that the date picker is not pinned to the top anymore, itās pretty bad when you have to scroll down/up/down/up etc when you want to cycle through the days, especially if you need to weed out the days where some device have been reporting wrong usage and youāre looking for the right date/time to change statistics on them. Please put the date picker back on top.
Have a look in the beta release notes of next release.
Please add the option to hide the Built-In Dashboards from regular users This is especially important for the security dashboard, where any user could otherwise see the cameras and alarm sensor statuses.
