2023.12: A beautiful new login page, new design for the thermostat card, numeric input feature for tile cards, options for the default dashboard, history dashboard showing long-term statistics, and...
I took their recommendation and removed “purge_keep_days: xx” from my config. For the one thing that I’m interested in keeping data for an extended time, it defaulted to 10 days and deleted all of my old data.
Looking into it further, I had to edit that particular sensor and add “state_class: xx” (measurement, total, or total_increasing) as described here to get long term statistics working.
Time will tell, but hopefully I can start collecting more data. I’m bummed I lost my nice long term graph, but in the end maybe this will be better.
Edit: Now I’m on a tear going through all of my custom sensors and making sure they have a state_class associated with them. I’m learning that in some cases, I can configure them through the UI as a helper instead of in YAML.
I’ve been using Grafana and InfluxDB to maintain device history as it can store everything for as long as you want. You might look into it if this new change doesn’t give you what you’re looking for.
Thanks, yeah I actually have InfluxDB set up and it contains history for the sensor that I “lost” so that’s nice. I don’t have Grafana set up, and InfluxDB seems to limit me on what I can graph. It says “Large response truncated to first 58k rows”.
I’ll look into adding Grafana. Does it pull from InfluxDB?
It might be worth keeping purge_keep_days configured to less than the default 10 days to keep the database size small and speed up backups etc, especially in setups running on low power hosts like a Pi and with large amounts of sensors.
HA is configured to log everything into MariaDB (which does not get backed up) so my backups are only 84MB including most add-ons. I use the “Home Assistant Google Drive Backup” add-on and tell it what to back up and what to ignore.
I took their recommendation and removed “purge_keep_days: xx” from my config. For the one thing that I’m interested in keeping data for an extended time, it defaulted to 10 days and deleted all of my old data.
Looking into it further, I had to edit that particular sensor and add “state_class: xx” (measurement, total, or total_increasing) as described here to get long term statistics working.
Time will tell, but hopefully I can start collecting more data. I’m bummed I lost my nice long term graph, but in the end maybe this will be better.
Edit: Now I’m on a tear going through all of my custom sensors and making sure they have a state_class associated with them. I’m learning that in some cases, I can configure them through the UI as a helper instead of in YAML.
I’ve been using Grafana and InfluxDB to maintain device history as it can store everything for as long as you want. You might look into it if this new change doesn’t give you what you’re looking for.
Thanks, yeah I actually have InfluxDB set up and it contains history for the sensor that I “lost” so that’s nice. I don’t have Grafana set up, and InfluxDB seems to limit me on what I can graph. It says “Large response truncated to first 58k rows”.
I’ll look into adding Grafana. Does it pull from InfluxDB?
Yes. And you should do something such as averaging if you want to fetch all the data I.e. to graph it. Grafana does it automatically iirc
It might be worth keeping purge_keep_days configured to less than the default 10 days to keep the database size small and speed up backups etc, especially in setups running on low power hosts like a Pi and with large amounts of sensors.
HA is configured to log everything into MariaDB (which does not get backed up) so my backups are only 84MB including most add-ons. I use the “Home Assistant Google Drive Backup” add-on and tell it what to back up and what to ignore.