New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
History-graph: do not make a graph for "unavailable" sensor transparent #14731
Comments
What can be considered as a bug is that we don't show a label. Like I said earlier: unavailable being transparant communicates a correct message, saying it's not a value like on, off, clear, etc. It's not that common an entity doesn't exist, only a first time. Note that your example is of 4 minutes, that's not a regular use case in my opinion.
That isn't consistent indeed. We should keep the same design pattern. |
But many people in Community disagree. Also, since currently you implemented a "color for icon = color for history" way for domains -> are you going to make a transparent icon for unavailable entities too? ))
Unclear, what do you mean?
Not sure what "4 minutes" you are talking about. But if you mean the 1st screenshot - this is a test case which is used for testing (a term we are missing a lot). And this case demonstrates an issue. |
I have to disagree to the following statement:
unfortunately, "Unknown" happene every time, when you have a cloud-based integration and the connection could not be established - or, if the integration could not be loaded, or similar... While I can fully agree with missing information in the Graph -> no data to record at all, the STATE should at least indicate SOME information. Unfortunately, with only a lable, it does not work in all cases, because probably, on several occurances there's not the required space to write the label. |
A label on a transparent bar may be not even noticeable.
|
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. |
up |
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. |
up |
May be closed - as long as |
Checklist
Describe the issue you are experiencing
Since 2022.12.4 a graph for "unavailable" entity is shown of transparent color.
This is confusing:
And when within the selected period the entity is
unavailable
- then no graph is displayed at all:which is super-confusing.
Describe the behavior you expected
Graph for "unavailable" sensor must not be transparent.
Better to use some theme variable like
--history-state-color-unavalailable
.Steps to reproduce the issue
as above
What version of Home Assistant Core has the issue?
2022.12.4
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue with?
Chrome 108.0.5359.99
Which operating system are you using to run this browser?
Win10x64
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: