Same problem here. Please keep us posted on a solution for this home assistant specific energy crisis 
Yea, energy cost calculations got messed up for me after migration to MariaDB. It now just accumulates all the sums, instead of all the differences. It’s possible to recalculate the history in the database, but it still continues to calculate wrongly. I posted a more detailed reply here.
Now I’ve just let it be, since I’ve already spent a day or two trying to fix it.
Thank you all for sharing. That’s obviously a no-go for some users willing to migrate, but not accepting the loss of LTS / energy dashboard data. Hope you get it fixed somehow.
Maybe all of you affected can summarize what migration method you used so that @jr3us perhaps can add a disclaimer/warning sign in the original post. Nobody lucky to find these great migration how-tos will be happy finding out the energy dashboard in the end got messed up.
This sounds like the type of data for longterm statistics
‘state_class: total_increasing’
got messed up during copy and maybe altered the type of state class .
do you know if there’s a way to update the state_class? these seem to be hidden entities
For those having issues with wrong energy cost, just run those 4 queries (as already suggested by ihr) and restart HA:
ALTER TABLE `statistics` CHANGE `created` `created` DATETIME(6) NULL DEFAULT NULL, CHANGE `start` `start` DATETIME(6) NULL DEFAULT NULL, CHANGE `mean` `mean` DOUBLE NULL DEFAULT NULL, CHANGE `min` `min` DOUBLE NULL DEFAULT NULL, CHANGE `max` `max` DOUBLE NULL DEFAULT NULL, CHANGE `last_reset` `last_reset` DATETIME(6) NULL DEFAULT NULL, CHANGE `state` `state` DOUBLE NULL DEFAULT NULL, CHANGE `sum` `sum` DOUBLE NULL DEFAULT NULL;
ALTER TABLE `statistics_short_term` CHANGE `created` `created` DATETIME(6) NULL DEFAULT NULL, CHANGE `start` `start` DATETIME(6) NULL DEFAULT NULL, CHANGE `mean` `mean` DOUBLE NULL DEFAULT NULL, CHANGE `min` `min` DOUBLE NULL DEFAULT NULL, CHANGE `max` `max` DOUBLE NULL DEFAULT NULL, CHANGE `last_reset` `last_reset` DATETIME(6) NULL DEFAULT NULL, CHANGE `state` `state` DOUBLE NULL DEFAULT NULL, CHANGE `sum` `sum` DOUBLE NULL DEFAULT NULL;
ALTER TABLE events MODIFY `time_fired` datetime(6), MODIFY `event_data` longtext;
ALTER TABLE states MODIFY `last_updated` datetime(6), MODIFY `last_changed` datetime(6), MODIFY `attributes`longtext;
And in order to fix statistics in your DB, just create a trigger as suggested here (you will need 2 of them - 1 for long term and 1 for short term stats): https://community.home-assistant.io/t/recalculate-statistics-table-sum-to-fix-wrong-energy-data/371334/5
2 Likes
Unfortunately, this did not solve the issue of runaway energy cost calculations.
Edit: Now a few days later, it looks like the cost calculation is ok again!
Got a question on the mariadb migration… I performed all the steps (minus the secure installation — will go back and do this another day).
When I look at Events, I see every entry as NULL NULL
States also shows NULL NULL NULL and Unknown
Will this heal over time as things report in? Or am I missing something here?
PS, my energy stats look fine. (Statistics)
Solution
I took a simpler or lazier approach, and used a well supported library to quickly migrate home assistants sqlite database into MariaDB/MySQL with full history. There is no need to even transfer files - just a couple commands and done!
Prerequisites
- install and activate MariaDB addon
- Install and activate the Terminal & SSH addon
Maria DB Migration Steps
- Stop the recorder service from developer tools
( ‘Developer Tools’ > ‘Services’ > Search for Recorder: Disable > Press the ‘Call service’ ) - Start the Terminal & SSH addon (mariadb should be running as well)
- Run the commands below to install python (already exists on host, super fast)
- Run DB migration
Post-Migration (activation)
- Configure HA to use new mariadb as recorder in configuration.yaml
Commands to migrate
# Install pre-req
apk add python3
apk add py3-pip
pip3 install sqlite3-to-mysql
# OR python3 -m pip install sqlite3-to-mysql
# run migration (CHANGE PASSWORD)
sqlite3mysql \
--sqlite-file /config/home-assistant_v2.db \
--mysql-database homeassistant \
--mysql-host core-mariadb \
--mysql-user homeassistant \
--mysql-password 'YOURPASSWORD'
(optional, include --chunk INTEGER to run the migration in chunks of records. This may help large datasets with lower resources.)
Arguments for script and more info → sqlite3-to-mysql · PyPI
FAQ
-
will it work with HAOS?
Yes. The installed tools only need to exist as long as the commands take, and theTerminal & SSHadd-on works great. -
I got an error from mysql (invalid column, duplicate key, etc) !
Backup mysql, purge all tables, and try again. MariaDB tables should not exist when we start migratration, will be fiully created from sqlite. ONly the database itself should exist.apk add mysql-client mysqldump -h core-mariadb -u homeassistant homeassistant -p > sqlbackup_DATE.sql -
Can I use if database is on another host?
Yes, just change the ‘-h’ (hostname) argument to wherever it lives -
Can I use with phpmysqladmin?
The python tool wants direct access to the MySQL database, just like phpmysql. You need access to the HA instance with ability to run python (hence Terminal addon) -
What about Energy Dashboard (and statistics generally)?
Yep, all there. This migration should be everything in sqlite. (thanks @jusii, @malosaa) -
My Energy costs are all messed up after migrating!
Giving Home Assistant a day to work through should correct this, (thanks @malosaa) -
Are there size limits?
In theory any existing sqlite db can be migrated. only the resources of your machine limit that, but even little NUCs should get it done eventually.
And also…
Tremendous thanks to all the folks below who tested, questioned, and refined this method! We got a winner!
36 Likes
So on which setup did you / can one use this? Will it work on HAOS too (because installing stuff is - if at all - only temporary due to the dockerization which is reset on container recreation etc.)?
1 Like
Yes, that is my setup. ONly needs to be temporary to run the ~45 second migration.
1 Like
Nice. That seems to be the most hassle-free Migration how-to seen so far 
Most important question: what about your energy dashboard…
1 Like
i did try this on my test system getting an error
// update, deleting the database and adding again fixed it
1 Like
So is it possible to use the phpmyadmin in homeassistant with an installed version of mariaDB on an other server ?
and how do i set it up
regards
Yes, as long as HA can connect, just change the -h (host) argument to point to wwhereever that machine is.
can i do this within the gui of phpmyyadmin ?
not possible:
Known issues and limitations
- This add-on needs the core MariaDB add-on version 2.0 or higher.
- This add-on is created to allow management of the official Home assistant MariaDB add-on. It cannot connect to other MySQL or MariaDB servers.
I dont understand why you are concerned with the Phpmysql GUI though, the python script eliminates any need to interact with MySQL/MariaDB, it does all the commands directly to the database, whereever it may live.
Edit: YEP , Sure does!
Can’t say, I disabled my Sense monitor integration months ago cause it was so damn noisy i was sure it would kill my SD.
HOWEVER
I monitor a greenhouse with stats and those are showing up going way back.
Would love for soemone with active energy stats to confirm though!
EDIT (I went further back an indeed its there as others have now confirmed)
I have active energy stats and they reporting good in the energy tab.
just tested it on my test system
2 Likes
