Open danielskowronski opened 4 months ago
Having the overview dashboard as a default dashboard is a technical limitation and legacy support for now. I agree with you, we should be able to remove it and set every other dashboard as default.
Also, the current UX sucks.
I agree, this screen is not right. Some aspect of the dashboard are not editable (icon, name) but some others are (area, hide energy card, etc...). You can even take control of it to fully customize it. We currently have 2 pages to access dashboard settings (one in settings panel and another from the dashboard itself) and it's very confusing.
It's also in the roadmap to improve the default dashboard (multiple views per room, etc...)
For now, as a quick fix : you can "take control" of the overview dashboard from and configure it manually. It's not perfect but it should at least fix your daily issue.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The default dashboard is still magical.
@dstengele What do you consider as "magical"? I answered by explaning how to take control of the default dashboard with latest release.
It is planned to improve the default dashboard. We are currently working on the foundation in the latest releases by adding some elements :
The final goal is to have a great default dashboard while allowing user to customize it. But we first have to build the foundations.
@piitaya And the workaround is fine and works for me (and probably most other people), so thank you for that. :) I just think that this issue should not yet be closed since the default dashboard still is kind of special. I think it would be most logical to just have a basic default dashboard that automatically shows "standard data" like temperature, humidity, thermostat, camera etc. of each available room, kind of like the Home apps do it on iOS, while not being able to be edited at all. This way, the default dashboard can be used for a general overview without needing to customize it. And if one wants to do it themselves, they can use the existing functionality of setting another dashboard as default and thereby hiding the normal default dashboard. I think much of the confusion comes from this half-customizability.
Checklist
Describe the issue you are experiencing
The "Default Dashboard" is a resource that user cannot control with restrictiveness amount changing from version to version (on 2024.6.4 it's the worst so far, which manifests with "The default dashboard, Overview, cannot be edited from the UI. You can hide it by setting another dashboard as default."). That fact alone wouldn't be so painful (after all, we have Map and Energy dashboards), but because it's a default dashboard globally, you must change it on every device you add and from time to time, re-set it as those devices tend to forget sidebar settings. Additionally, it's "magical" because HA updates randomly decide to revert it to the default view showing everything.
I'm deeply grateful for the open-source software and I'd be very reluctant to migrate; however, IMHO, this is unacceptable behaviour, similar to what Microsoft does with shovelling random changes on Windows because:
I know there are plenty of similar issues raised (e.g. https://github.com/home-assistant/frontend/issues/18626, https://github.com/home-assistant/frontend/issues/11069), but they are all about specific aspects of the main issue, as opposed to hardcoded nature of "Default Dashboard"
Describe the behavior you expected
I see those two as an ideal solution - preferably having both implemented, but just one would be sufficient to ease the pain:
Those are alternative approaches, listed from most to least desirable ones:
Steps to reproduce the issue
What version of Home Assistant Core has the issue?
core-2024.6.4
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue with?
No response
Which operating system are you using to run this browser?
No response
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
A few of use-cases that are completely broken by this behaviour:
Full list of similar issues: