I just went to upgrade as well and noticed the same thing.
Mine is 10.3.32-1040 build.
I guess we are in limbo for now until theres a rollback or Synology upgrade the package
2 Likes
Since the Update my deConz-Stick doesnāt Work. My Zigbee-Network is down!
3 Likes
Any way to check on status of Db update/upgrade Been 2 hrs all my charts are broken everything is flatline and missing data points/ MiriaDB, 2.5.2, 52GB DB
Very smooth upgrade for me, no issue identified yet. Thanks team 
Check the MySQL/MariaDB process list
https://dev.mysql.com/doc/refman/8.0/en/show-processlist.html
Thatās quite a large DB for MariaDB (SQLite should finish in under an hour even with a 100GB one for most systems). If you donāt have a fast disk it could take a few hours.
If you canāt upgrade to MariaDB 10.6.9 or later right away, you keep your database size small (under 2 GiB ā¦ ymmv), and you havenāt had a problem with slow purges or queries before you might not hit any of the known performance issues.
MariaDB 10.3 reaches end of life on the 25 May 2023 MariaDB 10.3.38 Release Notes - MariaDB Knowledge Base so youāll likely need to find a solution to upgrade before than unless your vendor has agreed to continue to provide third party security updates (itās also likely that newer versions of Home Assistant will not support 10.3 after it reaches end of life)
The 10.6 series is a good upgrade target choice since it is the LTS version of MariaDB
1 Like
It has been described in the last version that we could change rounding of sensor? How to make it, for exemple from 22,12kWh to 22,1kWh for my shellyem without to create a new sensor?
so right now, it seems not be possible to ask for the state of an entityā¦
Butā¦ I think thatās just a question of timeā¦ weāre still in the beginning of the year of the voice and things will still develop 
1 Like
Several issues after the upgrade. Many statistics charts will no longer show any data, system upgrade took about two hours last night (on the latest MariaDB), and especially the Unifi integration (I have not touched that in a long time) started flooding the logs after the upgrade. I will need to dig into this later today.
3 Likes
Any idea why my only sql sensor stopped working after the upgrade? The standard SQLite database here. Running the query in the SQLite Web addon returns an empty result as well, although it used to work before. History shows data is there for the entity I am querying, but it looks it cannot be retrieved anymore via the query. Havenāt noticed any possibly related breaking change.
Why the heck canāt I use two languages in the system (assist)? Iām pretty sure they have been working on this and my use case is this: HA is set to english, but I would like to use assist in Czech. Any ideas how to do that? Maybe not supported, yet?
2 Likes
Same here, i have user in English also and i want greek as language in assistā¦
Iām in exactly the same position, though I took a bullet and upgraded to 2023.2. DB schema update generated tons of timeout errors in log file, but I think DBwas finally get converted and is working reasonably well. For example If I want to see full history of ~50 entities in history view for whole month (but Iām using history explorer card for this, not the standard hostory dasbord) it takes ~45 seconds to load. Prior to update loading the same view took ~30 seconds. So Iād say 50% performance hit that I can accept, as for most of the views I do not look at so much history and not for so many entities, so difference is not noticeable.
Pirge might be different story, yet need to observe if any issues.
Side effect; overnight size of my DB jumped from ~4.5 GB to 6.5 GB, but I guess this is because of schema conversion and perhaps some obsolete tables yet need to be cleaned, so it should gradually go down over next month.
BUT, big concern here is that indeed, thouse using MariaDB on Synology are stuck to version provided by Synology. It is not just something that we can upgrade on our own and Synology is not very frequently updating such packages. The latest available package forMariaDB comes from March 2022ā¦
Even if would like to abandon the official package and go for some docker based solution (versions available up to 10.11 rc), how can we migrate data between databeses? HA never offered any solution to suppoert such migration and even if we are skileld enough to setup different DB, we might miss skills required to perform such migration.
2 Likes
I have this error during update from 2023.1.6 (Home Assistant Core) :
error: failed to select a version for the requirement `ahash = "^0.8"`
candidate versions found which didn't match: 0.8.0, 0.7.6, 0.7.5, ...
Edit : it worked after uppgrading rustc and cargo using
rustup update
Same here. Assist couldnāt understand anything
Iām also couldnāt find a way to make Assist understand a language other than English
Anyone knows how to make it work with other languages?
EDIT: I now see that if I set the language from english to my target language it does work, but I want to keep the system in English, so how can we set the desired language to be different than the UI language?
Well, new db format messed up my min/max temp sensors. I have SQL sensors for showing MIN and MAX temperature for TODAY (thatās from midnight, not last 24 hours!). I have sqlās as this:
SELECT ROUND(MIN(CAST(state as FLOAT)),1) as state FROM states WHERE entity_id = 'sensor.senca_zunaj' AND last_updated > CURRENT_DATE AND state not like 'unavailable' AND state not like 'unknown';
Now it shows unknown, since ālast_updatedā is no longer populated. Do you guys have any solution? Statistics, Min/maxā¦ sensors doesnāt help here, since, as said, iād like to show min and max temp from midnight to this moment (for TODAY only).
New ālast_updated_tsā time format is unknown to meā¦ just a bunch of numbersā¦?
thx!
Hi. Iām using a quite grand-fathered MariaDB 10.3.36 on Raspbian Buster.
Any idea if that one would be an issue? Thx.