From what I’ve see while creating SQL backups of the sqlite db, the longterm stats for energy work cumulative, so permanently growing from hour to hour. The energy dashboard then calculates the deltas for the individual bars. In your example, the second data entry is lower than the previous, therefore creating a delta gives you the negative bar. I guess you have to recalculate your data before you import it, making sure that your data is cumulative as well.
Which by the way makes me wonder how to import old data into a fresh installation which started at 0 for a power meter entitiy. At least for one hour, where old meets new data, you would have a massive negative bar…
Probably only works when you define a seprate “dummy entitiy” to the old data, dump the old data in, and then have a “switchover day” from which on only the new entities data is added
But the logic there would have to be an interesting one. Let’s say you setup a new system on a Monday, and your (new) energy meter entity starts it’s thing, and the statistics get recorded. When you now on the tuesday re-import old energy readings from the time before into the same new entity, the import job would not only have to get the right old data in, but would also have to adjust all the sum values for the new entity.
I think the issue is that you cannot really mix statistics import with sensor states. I tried to import statistics but also set the sensor value, which messed up the statistics. Now, I never touch the sensor and only import statistics, which works great so far.
I would say there is probably a way to do that, but you would need to somehow forbid the statistics module to load new sensor data.
I guess a much cleaner way would be to import historical data into the sensor and let the statistics module do its thing. That would however mean, you might need to re-do the whole statistics, for example if current values already exist and you want to patch in missing values.
@reox have you create any ghost/fake sensor for imported staistics? I see that home-assistent is throwing a warning if I’ll have no sensor but only stats.
I have a sensor, but I never set a state there, thus it always shows “unknown”. That works fine for me - with the disadvantage, that you do not see the current total value.
We just turned december and my last imported gaz consumption was on November 24th, so I have 6 days that are going to count towards consumption in december, which is very annoying as it will make comparing november and december consumption with the previous year invalid.
My gaz distributor did a maintenance/upgrade of his website and while the web grabbing method still worked, the data on the site was not updated over the period - it was just updated today, december 1st.
I noticed that when I added my water meter to the energy dashboard - a function that was recently added - all historical data is available in the energy dashboard - it goes back to june:
So importing historical data was possible for add a water meter to the dashboard.
It should be possible to add meter values to the database at a given date, not just for “now”. That would allow importing long term historical data, or cope with the unavailability of data from the energy provider for whatever reason.
I just wanted to add my wish for making import and export CSV specifically for energy history, available on the GUI. There’s quite a few edge cases where someone may want to either start from scratch but simply retain energy history, or move energy history around different installs easily.
I know it’s do-able via APIs, SQL, whatever, but adding CSV import and export via gui would be real nice. I’ve already had three experiences in 18 months of losing history and having to recover, so for those less able it would also be quite reassuring to have the data tangibly accessible and recoverable.
On the import it could possibly have import (sum) and import (replace) for example. Or mapping fields to existing or new datasets. It could get complex!
I’m interested in this topic too and I have some code that you may find useful.
“Historical Sensors” it’s a helper module to build sensors with historical data. It has the necessary code to import data but the UI for uploading and importing CSV files is still missing. Once it’s figured out how to present the UI it should be trivial.
The ‘delorian’ integration it’s just a test demo for the module, there is no integration ‘per-se’ in my project
The delorian integration depends on homeassistant-historical-sensor module so you have to install the module in the venv of homeassistant running pipenv install -e . or whatever suits you.
Anyway, I have made some changes to make delorian pull homeassistant-historical-sensor from github.
As interesting as this is, i’d LOVE to get a detailed writeup on how to use this websocket API call, so i can write a method to interact with it. I don’t see any documentation on what it expects, examples of usage, anything.
