Core: History for multiple days

[w1ll1am23]

This is a feature request. Also I was wanting some ideas on how to go about doing this. I would like the ability to configure the amount of history each component displays in the frontend.

The reason I would like this feature, is because I have a sensor that reports a state change once per day. This results in a graph that looks like the below. I would like to have up to a year of data on this sensor.

I have briefly looked at the history component and was able to return a couple days of history to the frontend. However the days overlay each other because it is based on time. I am also not sure how to get the config variable from a particular sensor when in the history.py code?

Would this be useful for anyone else? Some more examples?

[sfam]

I would also like to see some improvements in graphs:

• graphs are too small in the info dialog (on desktop).
• in history, sensors are grouped for the same unit_of_measurement... the temperature scale of my water heater is very different of my outside temperature, making the graphs useless.
• 24h time series is not always the best view for a sensor... maybe adding some buttons on top to show most common views: 1h, 12h. 24h, 1 week, 1 month, 1 year.
• history takes some time to load (when DB grows significantly in my RPi2)... it would be nice to choose what sensors to see in history by default, and dynamically load others on request.
• would be nice to choose the recorder/history DB engine (add platforms for recorder/history component and make sqlite3 the default)

I know some are not trivial to implement, but please considered these in next related developments.

Thanks

[Bart274]

I would also like to weigh in on this subject:

• I would also love to see more days in the graphs
• the graphs are too big when opening the info view of a sensor when holding your iphone in landscape, you can't see the other attributes anymore

Op 15 feb. 2016 om 17:28 heeft sfam [email protected] het volgende geschreven:

I would also like to see some improvements in graphs:

graphs are too small in the info dialog (on desktop).
in history, sensors are grouped for the same unit_of_measurement... the temperature scale of my water heater is very different of my outside temperature, making the graphs useless.
24h time series is not always the best view for a sensor... maybe adding some buttons on top to show most common views: 1h, 12h. 24h, 1 week, 1 month, 1 year.
history takes some time to load (when DB grows significantly in my RPi2)... it would be nice to choose what sensors to see in history by default, and dynamically load others on request.
would be nice to choose the history DB engine (add platforms for history component and make sqlite3 the default)
I know some are not trivial to implement, but please considered these in next related developments.

Thanks

—
Reply to this email directly or view it on GitHub.

[atpage]

I would like to see this feature too. Until then, it does seem easy to dump the data from home-assistant.db and plot it on your own. For instance

select datetime(created, 'unixepoch', 'localtime') as time, state from states where entity_id='sensor.YOUR_SENSOR_HERE' order by time;

[w1ll1am23]

Going to go ahead and close this since it isn't a bug. Opened a feature request in the forum. https://community.home-assistant.io/t/configurable-history-graphs-display-days-weeks-months-of-data/7301