Okay, thanks I closed mine with a comment to this one.
Strange thing is I googled yesterday and didn’t find any related to HA.
How much we must wait before the database migration is completed? I am running on a RPi 4 and after 30 minutes i still have the " Home Assistant si sta avviando, non tutto sarà disponibile fino ad avvio completo.RIMUOVI" warning…
No I’ve been running esphome dev without HA dev
Really ??? Are you running HAOS on an RPi ?
Depends on the size of your database. Even on my x86 system it took fair amount of time so i assume Raspberry can take even hours.
My database is 255MB, not so great…
Thank you Adrian!
Any idea when 3.7 will be available in Home Assistant OS?
I appreciate your respone!
KR
Albert
HA OS is i believe running > 3.8 already
you can check by going to Configuration -> Info then system health should show what its running
What flavour of home assistant are you running?
This is not related to the update. If noticed that a week or so ago that tado seems to take a while to propagate data into ha.
Not sure if it’s to limit load on the API?
Homeassistant OS5.13
Supervisor-2021.03.9
Core-2021.4.1
Is is I believe the Homeassistant OS version with addons
HA Core on RPi 4, 3 weeks history, MariaDB on external USB drive.
Hi - thank you - you are correct.
I’m running Python Version 3.8.7 already on HA.
That means ESPHome runs with its own 3.6.9 and I (apparently) need to wait for the upgrade of ESPHome 
Correct so far?
kind regards
Albert
1 Like
@maurizio53
I am on RPi 3, approx 1.3Gb MariaDB on NAS, another - approx 1.5 Gb InfluxDB on RPi’s SSD, installed update at 9:15 and still waiting (it is 13:45 now) apparently system gradually waking up, Samba, mqtt server etc. work but HA is not accessible yet
Update:
After another 3 hrs still in process, from time to time some automation fires, last one, so far, was doorbell from 11:45 announced with 3 hrs delay. HA still not accessible
Update II:
After 22 hrs still in process, from time to time some automation fires, last one, so scary, was TV on at 2:45. HA still not accessible.
why are we still seeing this Invalid date issue on the last updated? wasn’t this fixed in the latest HA? Cant remember the exact PR but thought to have seen this fly by?
am i the only one who misses the custom integrations count them in analytics?
Dwains Dashboard, Alarmo, Scheduler etc.
well your already running >3.8 python, so the issue is with the addon which was updated in the last day, maybe log a support issue with the addon repository
I use an older Intel Atom Quad Core system, the database (~36 GB) ist stored on MariaDB on an SSD. The DB migration took about 16 hours…
To the people suggesting that database sizes can be limited by proper setup of the recorder component to prevent huge databases…
recorder:
db_url: !secret ext_db_url
purge_keep_days: 31
include:
domains:
- sensor
- binary_sensor
- switch
- device_tracker
- climate
- input_boolean
- input_number
- input_datetime
- light
- timer
- media_player
- person
- group
- automation
- utility_meter
- alert
That has been my setup from the start, I think 31 days is fair, I’m not keeping several months worth of data,
+----------------+-----------+
| Table | Size (MB) |
+----------------+-----------+
| states | 2951.06 |
| events | 1524.94 |
| recorder_runs | 0.03 |
| schema_changes | 0.02 |
+----------------+-----------+
It doesn’t exactly make the database that small. and it took about 2 hours to migrate, on a virtual server with a Xenon processor.
I already have HA accessible, but not fully… It’s more than one hour and half…