Things like that have never shown in configuration check because it’s valid Yaml.
I’m also confused. The release blog states, API becomes local but links to an integration page with a cloud API. Please people a more clear explanation helps. I would love to use a local API instead of a cloud API, where to find the info about it?
No need for a bug. See above. It will be via reload of the mqtt integration. But is not implemented. Discussed a lot during beta time.
The user’s YAML example contains information for setting the fan’s device. According to the documentation, that’s still only possible via MQTT Discovery. Not sure what currently happens if it’s included in the fan’s YAML configuration (it’s ignored and the entity is created or the entity isn’t created). 
1 Like
the last update impact one of my dashboards
i looks like there is a memory leak somewhere, because i seen my chrome waste up to 9gb just with homeassistant open
i know i’m using custom cards here but before the update was fine and the Dashboard is been working since last year
Agree that there needs to be way to update key, password, login, etc …
Odd UX to have to delete to change?!?
2 Likes
yes, and the reload for Manual (Yaml) MQTT was taken out, but follow Fix reload of MQTT yaml config by emontnemery · Pull Request #72901 · home-assistant/core · GitHub
1 Like
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