I know that, but the average user wouldn’t and might spend some time researching a nonexistent issue.
You have to do a little research to set up the MariaDB in the first place, so I believe you’re looking for an issue where there really is none
P.S. I believe that every user who is able to install and set up HA is able to know or find out if he is using something or not - clearly HA is not some OOTB solution (yet).
Check in the configuration.yaml file if there is a SQL line with a connection string to MySQL / MariaDB. If that’s the case check your version with:
mariadb --version
This will output the version being used. Keep in mind that an sudo apt-get update && sudo apt-get upgrade will not update your MariaDB version. You will have to remove and reinstall.
For some people that are using the core version (so am I) and running Raspbian with an old rustc version, you need to update this to a newer version to compile bcrypt en cryptography.
In my case removing the old version and installing it again did fix the issue.
- Remove old Rustc and Cargo:
$ sudo remove rustc cargo
- Login as the HomeAssistant user and reinstall Rustc:
$ curl https://sh.rustup.rs -sSf | sh
After that logout and sign-in again as the homeassistant user and use pip to upgrade homeassistant like you normally would do.
What happened to frontend precision overriding?
Removed for the time being due to unseen problems that could arise impacting other functionality.
What is the community version?
core version, sorry my mistake
yip, I get no updates
check for updates, it’s released for sure.
No fix for Enphase D7 firmware?
Although Hebrew is listed under supported languages for Assist, looks like it only understand English.
Anyone figured out if Assist is supposed to work with other languages?
yip, tried to force check and nothing, front end also says no updates
I’ve been running MariaDB on my Synology NAS for some considerable time now with no issues. Looking at the package on the NAS it’s version 10.3.29 - the latest version available for the Synology NAS I’m using. It’s not one of the versions listed. Should it still work?
These things take time. stop hammering the server and it will probably happen faster.
Many of us like updates and trying new stuff, but hammering at it is counter-productive.Relax, have a cup of tea instead of those strong coffees
haha, you got me spot on drinking coffee but I am not hammering. I tried force update once only.
Yep, but you and many others probably.
Such is distributed rollout. It’ll happen
For those using Xiaomi-BLE sensors, this release also adds support for the Xiaomi BLE door, opening and motion sensors.
Older versions of MariaDB will still work but may hit scale problems once you have > 1GiB of data or low ram (YMMV, it can happen at smaller or larger numbers depending on how fast your disk is). For best performance you want to be running MariaDB 10.6.9 or later (addon version 2.5.2 or later).
If you have a lot of data in the database the older versions may take multiple minutes or hours to answer history queries or purge the database.
The big risk is that you have a long running history query or purge still running in the background when doing the update to 2023.2.0 since there is a database migration that can fail if the long running query has the database locked.
You can check the https://dev.mysql.com/doc/refman/8.0/en/show-processlist.html before updating to make sure there are no long running queries if you are running an older version before updating to make sure you won’t hit the issue during updating (that will not prevent it from happening during production later, but the consequences are much lower if it happens after the migration).
For the iotwatt breaking change, I’m using the Accumulated sensor for each circuit in the Energy dashboard. When I’ll change the entities in the Energy dashboard with newly created integrators, will it breaks/deletes historical data?