Hi,
I’ve played around with openHAB for a while and concluded I like it more than home assistant. The only thing that kept my from switching was the loss of historical data.
After surgery I have a bit of time on my hands and dove into the issue and came up with a script that does it. Not fast, probably not pretty either, but it does the migration for me.
Interesting topic. With the homeassistent binding, mqtt, zwavejs and probably more, it is increasingly easy to switch between either system.
For (historic) data there is no out-of-the-box migration service. I wonder if we can create some kind of script that feeds data to the REST-api or otherwise so that it is persistence service independent.
I think you could pull data from hass via an API as well. My approach is one of multiple ways to do it, I choose this way for it seems easiest to me (having the HASS data dumped in files gave the option to look at it and decide what/how to import. That proved useful, energy readings takes another column from the table than basically all others (power, temp etc)
I’m also still adding to openHAB and as how i’ve written my script I can just update the hass-backup with the latest version and re-run it when i’ve added something.
Following your line of thought, since people switch in both directions, it seems like a joined project between openHAB and home assistant for a data migration tool could be beneficial to both.
nice, dumping hass to files first is probably the sanest path. being able to eyeball energy vs normal columns before import is exactly why people get burned on blind api pushes.
if youre willing to drop the script (even messy) this thread would help a lot of folks stuck on history. curious how painful the influx measurement/tag mapping got on the openhab side.
Thnx!: The script is linked in the original message
Much of it works, but Need some puzzling though. Power consumption graphs look the same, but the values are off. Where hass was a perfect match with my invoices, openHAB shows different totals.
Not sure where the issue lies as of now. The readings openHAB did itself seems wrong too.