If you configured the mqtt sensors via yaml, just add a unique_id to the yaml.
2 Likes
Unfortunately, yes. Which is why this release should be pulled IMO until the patch release is available.
For anyone looking to launch assist from lovelace:
tap_action:
action: fire-dom-event
browser_mod:
service: browser_mod.sequence
data:
sequence:
- service: browser_mod.navigate
data:
path: "?conversation=1"
- service: browser_mod.refresh
5 Likes
Thanks for the hint! I Will test this.
And what about entities created through yaml for example utility_meter entities? Is there a solution ?
None of the browsers are going to allow insecure access to mics, cameras, etc.
1 Like
Are they showing up in the list of exposed entities linked from the Alexa card?
If so, try to select all of them and expose them again.
utility meter also supports unique_id
1 Like
I had the same experience everything previously exposed to Alexa via Nabu Casa were removed and had to be re-added after the update. This should be added to the Breaking Changes list!
2 Likes
That should even not happen in the first place.
This must not be added to breaking changes, that 2023.5.1 version must be removed until this issue is fixed.
itâs not a breaking change because itâs not intended. It has been confirmed to be a bug (and one that did not show up in beta testing) and will be fixed as part of the .1 update
3 Likes
Same here, wife was not amused.
Took me some effort to get everything back into Google Assistant
I removed Version 2023.4.1 from QNAP Container Station Home Assistant, installed latest version 2023.5.1 and was trying to solve 5 hours the issue with onboarding page stuck. Finally I went back to Version 2023.4.1. and everything works like a charm. Something wrong is with this Release.
I think this came up once before, but has any thought been given to including known bugs at the same level as breaking changes, in the update blog?
Itâs frustrating that people do their due diligence, carefully reviewing breaking changes before installing, only to be hit by a known bug which wasnât listed there.
6 Likes
The Alexa Media Player integration might need updating or reconfiguring. Echos donât appear as media_player entities in Home Assistant without using that custom integration.
I much prefer being able to sort and select multiple entities at once with the new method. The previous card layout was not good for sorting or selecting large numbers of exposed entities. Having to manually re-expose everything is obviously not great and wasnât an intent, but at least with the new method it is much easier to search/filter and select if needed.
Did you try rebooting the system after your restore?
As far as I can tell from working with some other folks, with Google Assistant there might have been an issue with Google not seeing the exposed entities, but if you go to the Google Assistant card on the Voice Assistants page and click on the number of âexposed entitiesâ at the bottom, youâll see your list of entities, and can select all using the âselect allâ box and then re-expose them again and everything is fine.
With Alexa, the list is unfortunately empty and not as easy. So there is a need to clear the filtering of exposed Alexa entities in the top righthand corner, then e.g. search light., select entities, expose them, repeat with switch. , etc
We are talking local connection, so it should be possible.
Same, rolled back.
Unfortunately itâs a browser limitation 
secure context is needed to record microphone in browser.
We will adapt the message to better explain that point.
Secure context can be https, localhost or 127.0.0.1 but not local ip address.
2 Likes
Yes, per options provided by each browser, if available.
Snap! On a mission to fix everything this evening. Rolling back isnât working.
The most important thing after reading the breaking changes is to follow this Release Blog Post.
Number 5 (over 1 day old) warns about that issue and yet some install the release.
Why?
1 Like