Skip to content

Tell user why "No state history found" on more-info #3633

@SeanPM5

Description

@SeanPM5

Home Assistant release with the issue:
0.98.3

Description of problem:
Don't know if this idea is feasible or worth the effort involved. But the current more-info dialogs simply say "No state history found" regardless of the reason why.

This is OK but can be a little more user friendly by providing more context:

nostatehistory

The wording on these would need to be tweaked, but just a few ideas:

"No state history because history: not found in configuration.yaml."
"No state history because of history exclude."
"No state history due to recorder excludes."
etc

New users can often have trouble figuring out the history and recorder includes/excludes, and unknowingly have it misconfigured and be left wondering why it's not working. By pointing them in the right direction it can save a lot of troubleshooting and frustration. And even experienced smart people like HA devs can be tripped up by this briefly. So I think that this could be a helpful addition.

Metadata

Metadata

Assignees

Labels

Backend Change RequiredRequires a Backend Core Code ChangeFeature RequestShould be a discussionUXUser experience related bug

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions