Add capability to include multi-scraped sensor in statistics graph
See original GitHub issueIs your feature request related to a problem? Please describe.
Currently, scraped sensors are not considered measurements
by HA and therefore long-term data are not collected. This means that one cannot make long-term plots on the new statistics graph card. I scrape a whole bunch of numerical data into HA and it would be great to be able to look at long-term trends.
Describe the solution you’d like It would be great if it were possible to set a property for a sensor such that HA would collect statistics on it, according to the spec here.
Describe alternatives you’ve considered Extending the database is not really an option beyond some 10s of days and is completely unnecessary for most cases.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Statistics Graph Card - Home Assistant
The Statistics Graph card allows you to display a graph of statistics data for each of the entities listed. Statistics are gathered every...
Read more >GitHub - danieldotnl/ha-multiscrape
Home Assistant custom component for scraping (html, xml or json) multiple values (from a single HTTP request) with a separate sensor/attribute for each...
Read more >adding values from template sensor to statistics graph - Reddit
I'm trying to add the value from a template sensor ( that reads the temperature value from a smart TRV) to a graph...
Read more >Configuring performance metrics and display options in ... - IBM
Use the Monitoring > Statistics page to monitor the performance of system ... You can select the required charts and monitor the performance...
Read more >Home Assistant How To - get more Statistics from sensors
Getting more statistics from your existing sensors and binary sensors is very easy with Home Assistant built-in component - Statistics.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, I’m already looking into this after yesterday’s 2021.8 release
No, adding it to your config.yaml shouldn’t be necessary. I believe the statistics are calculated hourly, so you should wait at least an hour before it’s populated.
But great to hear that it works for you now. I’ll close the issue.