Database changes have been occurring to optimize the databases, this results in the tables changing. When the tables change, you’ll have to update your SQL queries if you’re using the SQL sensor to look into the database.
The tables in the database are not documented and they shouldn’t be documented. If you happen to use the SQL sensor to look at your own database, that’s an ‘at your own risk’ scenario as it’s not officially supported. If this occurs again in the future (99% sure more changes are coming to optimize the performance next release), you should create a post when your SQL sensors break. Tag the release, and post what’s not working. Someone who has the know-how to look at the database will help you update your Query.
Great, everything still working after the update.
Now, how can I modifiy the colors of the entities of my picture-elements card and ONLY in the picture-elements card ?
I use to type this but it’s not working anymore.
I changed to ‘–rgb-state-binary-sensor-color’ because the ‘’–paper-item-icon-active-color’ was not valid anymore after the last update and now again my picture-elements card has wrong colors.
Well, I will create my icons to be free to use my colors for the picture-element cards.
When getting the notification that it updates the database, do not reboot. I closed that notification, but how do I know when its done if I already closed it? I dont want to reboot too early and get db error. Im running an external mysql server
The new helper Groups or “Grouping sensors”, are this a new replacement for normal groups and light groups?
Can then be used in automations? like if sensors in group has motion, or turn lights in group to red?
Now i’m wondering which db to choose, or should i say: what’s benefit (or downside) of using mariadb on Synology or sqlite on HA…? To be honest, i mostly went to synology mariadb out of curiosity (wondering if i can do it) and because my regular backups (via samba backup) were too big because db was always included - this could be avoided, though, i guess…
Yes, I have cleared the cache and refreshed the page. It just sits there at the HA icon. Now whether this is java related because that appears the last thing the Safari inspector shows, I have no idea.
Well, I’m in the same boat as you. There’s no harm in keeping the old maria DB version, it’s just slower. That’s what I plan on doing until I can switch to another system outside synology.
If you keep the database size < 2GiB, you likely won’t hit any issues as all significant issues are performance problems that result in long query run time and everything backing up while the migration is running. These problems aren’t new, just compounded by the migration happening, so if you haven’t had an issue before (which would present as slow data queries), you aren’t likely to have one now.
While overload risk exists for any system, the best thing you can do is address the known risk factors to minimize that risk. The significant risk is a large database, a slow CPU, and a slow disk, which results in all the queries falling behind and your instance falling over because it can’t keep up. Suppose that risk is acceptable (and that’s a perfectly reasonable position to take), and you choose not to upgrade MariaDB. In that case, you’ll have a good idea of where to start looking if something goes wrong, which is the goal of highlighting the versions in the breaking change/repair issue.
That won’t solve the problem of MariaDB 10.3.x reaching EOL on 25 May 2023 so you’ll still need to figure out a migration path before than.
Is it possible to use ‘assist’ with an external microphone that is connected to the HA itself, the current reality that the possibility to give commands is only through a browser is very annoying,
If you access through an internal address whose traffic is not secure, the browser does not allow you to activate a microphone,