I have Home Assistant in my own language (dutch) but it doesn’t seem to understand anything. Not in dutch, not in English… Useless in this way
For anyone running Debian Bullseye (current stable), you may want to upgrade python from 3.9 and mariadb from 2.5 to 2.6 (see Breaking Changes above).
Disclaimer: YMMV, but I found these two guides helpful and they Work For Me ™, so far…
For mariadb you can use packages from the official repository rather than Debian.
Unfortunately I couldn’t find packages for Python, so that involves building your own, installing alongside the default 3.9 and then making 3.11.1 the default. It should therefore be possible to return to using official packages when Debian provide them.
How To Install MariaDB 10.6 on Debian 11 “bullseye” | Open UNIX Kernel
How to install Python 3.11.1 on Debian 11 bullseye (aruljohn.com)
All that said, I’m not yet seeing 2023.2 as an available upgrade using pip with HA Core 
I have it in my configuration.yaml, because I hate having SQL code in a config dialog. I use the SQL component from HA 2022.4 (last good version) as a custom component to achieve that.
But just for you I’ve created a sensor with that query with the GUI and it works exactly as my configuration.yaml sensor.
Did you fill the “Column” field correctly? Should be “min_temp” if you copied my query.
Ok, now i see that your solution is for HA’s internal sqlite database. Now i switched to HA’s internal db for testing and your sql works. I guess that “DESC” will give me max temperature, while “ASC” will give me min temperature today, correct?
So, i guess one of solutionsis to switch to internal db, especially since synology is know to give out updates pretty late, so i coudl be stuck with critical warning for weeks, months…
There are two things I noticed in this release that I had to back out the changes. The first is with “Safari”. In the past, this has worked fine allowing the browser to display and administer Home Assistant. However, with the latest release and opening the Home Assistant URL, the screen is blank with the Home Assistant Icon. If I run the same workflow on a different browser such as “Fire Fox”, it works as I would have expected. Did the requirements change and “Safari” is no longer supported? The other issue I found was with MQTT. This integration communicates with “Solar Assistant” to render information regarding solar production, inverter and battery status. After the update, the MQTT entities for Solar Assistant could not be found even though both were carrying on a conversation. Looking at the logs I can see MQTT message received but it looks partially processed. With that said, I had to back out of this release to the previous one. Sadly.
After the update, my Fire Tablet 7 with Fully Kiosk shows only a white screen, sometimes with the blue HA icon. Then nothing happens, looks like it hangs. It looks like a similar problem as in the past in older versions: Problem with 0.99 and Fully Kiosk + Fire Tablets?
Fully Kiosk works allright with a different url/webserver.
Cleared the cache etc. in Fully Kiosk. Nothing changed. As I said, the same behaviour as in version 0.99.
EDIT: I tried WallPanel app on my tablet, exactly the same behaviour. With other url, WP works fine.
EDIT: Updating to 2023.2.1 solved the problem. (Update frontend to 20230202.0)
Aaargh… my poor sql knowledge…
i entered “states”, like i usually did. Entering “min_temp” went through, so far looks ok.
Many thanks again! Hopefully this is the end of my problems…
After upgrading, it seems that themes are not loaded anymore.
I downgraded back to 2023.1.7 and themes were working again.
So I upgraded again to 2023.2.0 and themes are broken like the first time, everything is set at the default theme, which means inverted Alarm badge and son on… (green when armed instead of red)
Whatever theme I select, nothing happens.
Is this happening only to me ?
Edit:
In fact, themes are loading OK, but the naming convention has been changed… see Entity state colors theming by piitaya · Pull Request #14831 · home-assistant/frontend · GitHub
So none of my theme configs worked.
In principle, this is good news because we now have official variables.
But this PR is flagged as Breaking, but does not appear in the Breaking changes section of the release notes, which seems to become a recurring problem the last times and cost me a few hours to sort out…
I see the same thing with Safari.
Yeah, I was doing my own digging after noticing that my sql sensor became unavailable. Didn’t know that you don’t use the internal SQLite database, that’s why I replied with my solution.
DESC and ASC should indeed show max and min temps.
That’s the sort of change that I would qualify as “breaking”, although the devs didn’t even bother to mention it. Or maybe they did in some obscure documentation that none of us, the regular users will ever read. I’m quite surprised that there are so few posts mentioning this issue. Anyway, the sql sensor doesn’t seem too popular, just about 2% of the active installations using it.
Safari works here, clear your cache and refresh the page.
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.
- type: state-icon
entity: binary_sensor.house_entry_motion_occupancy
icon: mdi:account
style:
top: 3%
left: 22%
'--paper-item-icon-color': white
'--rgb-state-binary-sensor-color': 255,0,0
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.
That query is specific to database size, and it still works. All other queries are not documented, nor are the tables.
EDIT: That reminds me, I moved my db to a new database name and I have to update that query to reflect that. Thanks!
Should just be
- type: state-icon
entity: binary_sensor.house_entry_motion_occupancy
icon: mdi:account
style:
top: 3%
left: 22%
state-binary_sensor-off-color: white
state-binary_sensor-on-color: red
covered:
2 Likes
In case it helps anyone, I had to use the following to get it to work:
...datetime(last_updated_ts,'unixepoch') >= date('now', 'start of day')...
Different db/sql version I guess.
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
I think it reports it is complete in the log.
1 Like
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?