Last update also optimized database. Which broke my sql sensors. It seems that i missed a note in changelog that “last_changed” is (among some others) removed from database, so all my sensors were “null”. Changing to “last_updated” solved my problem.
Supposely sql is now “included in HA”. But does this means that i can only edit my sql sensors from settings —> devices and services —> sql and not anymore from studio code server?
The bug where you can’t actually Leave the Automation editor by clicking Leave is back. Filed a report here
trying the new announce: true on media_player.play_media Media Player - Home Assistant but no such luck just yet.
- service: media_player.play_media
data:
announce: true
entity_id: >
{{state_attr('sensor.media_players_active','players')}}
media_content_id: >
{{states('sensor.radio_station')}}
media_content_type: music
is part of a script to play a radio stream, but when a tts message is thrown at that entity_id, the radio stops, the message is played, and…, that’s it really…
can anyone report differently?
tbh, I am not 100% sure of what this resulted in Remove announce workaround for Sonos by jjlawren · Pull Request #72854 · home-assistant/core · GitHub . was it pulled or not?
Isn’t it the other way round? With this you can play something as an announcement and not say to playing things that announcements are allowed, as you are trying. Didn’t test it, but I’m pretty sure.
The announce parameter is not yet supported by any media_player integrations. The parameter is accepted and won’t throw an error, but it’s effectively ignored for now (with the exception you linked above, which is being reverted). It’s a developer-facing feature which needs more work per-integration before it’s useful.
1 Like
Waiting for a fix for Logbook.
Logbook card: one entity, about 20 state changes, 24 hours - it is opening very slowly (much slower than it was before 2022.6).
That was introduced in the May Release (2022.5).
Take a look at the Breaking Changes section: 2022.5: Streamlining settings - Home Assistant
Do you have an issue open about the logbook ?
Not yet. I am still observing, gathering statistics.
First I suspected that was a DB issue - like “first xxx days DB is self-organizing” etc.
Now, after many HA restarts (as well as the Linux host’s restarts) I see that it is probably an issue.
I will wait for other people, may be someone will experience it too - then I will register it on Github.
Yes, SQL integration was, as you say, indeed introduced in May, but deleting of mentioned entries in “states” table was done yesterday with June update. See all “NULL” entries in the picture. They start at 17:09, when i updated HA to 2022.6
Yes, I have the same logbook issues…
It’s complete empty, and if I wait a while, it’s starts populatin, but very slowly
I was not sure if it is problem with a Logbook in the new HA version or my own internal problems.
Today many people in my country are trying to recover their Internet connection due to Gov efforts for isolating Russian networks from Internet, VPN clients are not working, my Linux host is stuttering, lots of erros in HA logs, … - these things could cause these freezes, I thought. Great time for a science-making.
I was thinking the exact same thing.
it must be like this.
not sure it has been improved, but even old format couldn’t had been reloaded if added for the first time. For example if you had no any mqtt template at all and have added the first one, the reload was not effective.HA restart was needed. But since this, each further modification could be reloaded with reload button.
just thinking loud, if this is not the same issue
Mine when crazy, I get a different value (wrong one) every few seconds, and I think is due the update, it was working before. Any ideas??
Hi
After midnight mine reset and is now working correctly.
Yeah after I sent you the message, I started looking for the reset option for the host, I couldn’t find it, so ended up restarting HA and it seems to be working now. Lot’s of particular readings on logbook but other than that it looks ok now, Thanks.
It is likely this issue if you have both includes and excludes
1 Like
Way to scare someone. Correct me if I am wrong, I think the replies are for the “Version Integration” calls a NUC as a Generic X-86?
If this is so, why didn’t they simply say that?
When Ubuntu support was dropped, I bought a new Intel Nuc i5 just for Home Assistant. The reliability and speed have been amazing. You can imagine how upset I would be if the Nuc were no longer supported. BTW, I saw this “breaking changes” a couple of days after installing 2022.6. No brick.
What the heck is the Version Integration used for? Just to tell you what version you are running? Is this the same information you see in “System Health”?