Closed dirrgang closed 8 months ago
Hey there @frenck, mind taking a look at this issue as it has been labeled with an integration (adguard
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
adguard documentation adguard source (message by IssueLinks)
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 problem
In reference to #98880 and #98577. I meant to comment on the issues themselves, but they are locked.
The reason I had created the original PR was because I wanted to make a UI card that shows statistics of AdGuard, such as this:
Without a
state_class
attribute, the sensors don't store any statistical data, therefore the statistics card cannot be used. (The screenshot was taken on my instance that has the state_class overwritten viacustomize.yaml
.I'm aware that the statistics are moving windows, but rather than moving the
state_classe
s entirely, perhapsstate_class: measurement
could be used instead?What version of Home Assistant Core has the issue?
core-2023.8.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
adguard
Link to integration documentation on our website
https://www.home-assistant.io/integrations/adguard
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response