Update to 2023.05. removes exposed entities to Alexa and Google

[ChristophCaina]

The problem

I've already setup Voice Control for Alexa throught the NabuCasa options.
After installing 2023.05. I noticed, that all entities, which I've setup for being available for alexa were removed.

HA does start with exposing entities to its own Assist - but these are not the entities I've activated for Alexa / Amazon Echo... so I had to redo the whole setup... (remove the entities I don't want to expose (for Assistant) and add the entities I want to expose to Alexa...

At least, this needs to be mentioned as a breaking change!

What version of Home Assistant Core has the issue?

core-2023.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Assist / Nabu Casa Cloud

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

All entites that have been exposed to Amazon throught the Nabu Casa Cloud are no longer available - and needs to be enabled again in the new VoiceControl setup page

Auto-Exposing entities for HA Assist did not match my previous setup for Alexa / Amazon Voice Control

[smarthomefamilyverrips]

Same for Google Assistant!

[lexiismadd]

I'm having the same issue too

[emontnemery]

The existing settings for Alexa and Google assistant are supposed to be migrated the first time Home Assistant starts after upgrading to 2023.5.

To help debug this issue, please share the following files from HA storage, ideally both before and after upgrade to 2023.5.0:

• core.entity_registry
• cloud - This has some sensitive data, DO NOT upload the full file to github, only share the content of these keys:
  • alexa_default_expose
  • alexa_entity_configs
  • alexa_enabled
  • alexa_settings_version
  • google_default_expose
  • google_entity_configs
  • google_enabled
  • google_settings_version
• homeassistant.exposed_entities

If you don't want to share the file on github, please contact me on discord: emontnemery#6618

[ChristophCaina]

Hi @emontnemery,
unfortunately, I already reconfigured everything... don't know, if the files would still help?

If not, I might be able to setup another test installation and expose some entities to alexa and try to reproduce this case...
But I am not sure, when I will be able to do so... maybe, someone else affected from this case could provide the required information in the mean time?

[austwhite]

This is not just Alexa. Same issue with Google Home also. No entites exposed to Google Home and when I tried to re-link to Google Home, I just got an error stating no compatible devices were available.
It was all working in in 2023.4.6 and rolling back to 2023.4.6 does solve the issue, but then of course I lose the new Home Assistant voice functionality

[emontnemery]

@austwhite OK, could you help by sharing the files here: #92459 (comment)

[austwhite]

I'll share them, but I also started to manually reconfigure some devices :).
All the devices were there, but just 0 of them exposed.
How is the best way to upload them without the sensitive data, or to make sure they get just to you ?

[emontnemery]

You can contact me on discord: emontnemery#6618

[emontnemery]

For those of you who have this issue, have you configured the cloud integration through configuration.yaml or have you been using the UI to expose entities also before upgrading to 2023.5.0?

[austwhite]

I was using the UI to expose entities before upgrading

[smarthomefamilyverrips]

@emontnemery, UI through home assistant cloud section

[emontnemery]

Another thing. This screenshot shows a few entities exposed to assist, alexa and google:

Can you confirm if the list showed entities as exposed to alexa and google, but alexa and google did not see the entities or if the list showed no entities exposed to alexa and google?

[austwhite]

@emontnemery
I definitely saw that list, but none of the devices in the list were exposed until I selected them (using the check box) and then clicked Expose. After that, the icons appeared and then I could see the entities in Google Home again.
As a note, all entites were exposed to Home Assistant Assist, just not to Google Home (in my case)

[emontnemery]

This potentially fixes this issue: #92499
Users who've already updated to 2023.5.0 won't be helped by it though

[smarthomefamilyverrips]

So the potential fix #92499 will be available from 2023.5.1 then @emontnemery ?

[emontnemery]

@smarthomefamilyverrips yes. You would need to restore a backup of 2023.4.x, and then upgrade again though for the migration of settings to run again

[kahancock]

For those of you who have this issue, have you configured the cloud integration through configuration.yaml or have you been using the UI to expose entities also before upgrading to 2023.5.0?

Same as others. Configured via UI; not configuration.yaml.

[ChristophCaina]

yes, also configured via the UI -> "Cloud" -> "Alexa" and then selected the entities I wanted to expose

[tda2806]

Manually configured MQTT sensors in configuration.yaml are marked as "unsupported" for both Google and Alexa, previously these sensors were passed without issue.

Example configuration entry

mqtt:
sensor:
- name: "Bathroom Temperature"
state_topic: zigbee2mqtt/Bathroom Sensor
unique_id: 0x00124b00290fb657_temperature_zigbee2mqtt
unit_of_measurement: "°C"
value_template: '{{ (value_json.temperature | float +0.13) | round(1)}}'

[Saballard1]

Morning all, I updated HA yesterday and now I have the same issue with Alexa, is there and fix?

[ChristophCaina]

should be fixed with 2023.05.01 - but you would need to do a rollback to 2023.04.06 first - and then install 2023.05.01 directly

[Saballard1]

Thank you, I'm trying to do a restore of 04.06 but it's restoring for about 20 minutes now, i'll give it some more time, sorry i'm pretty new to HA. Thank you again for your follow up. [image: image.png]

…

On Fri, May 5, 2023 at 7:33 AM Christoph ***@***.***> wrote: should be fixed with 2023.05.01 - but you would need to do a rollback to 2023.04.06 first - and then install 2023.05.01 directly — Reply to this email directly, view it on GitHub <#92459 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AY6P3YIFRPIMHL4MOO3MK2LXET6SFANCNFSM6AAAAAAXVJXHNE> . You are receiving this because you commented.Message ID: ***@***.***>

-- Scott A Ballard 248-979-1246

[Saballard1]

I used Nabu Casa to do the restore, and it has been over 35 minutes and NC is still not connecting to HA after i selected to restored to 04.06, should i have not used NC for the restore? Thank you for any follow up.

[Angelos59]

I upgraded to 5.0 back to 4.x then to 5.1 and then 5.2, the entities are exposed to Alexa but the media controls for music still don't work. Volume works but pause and skip do not. I circumvented with a script but it should be fixed or remove the controls from the media player. Tis worked in 4.x and not 5.0, 5.1 0r 5.2. Thanks, you guys do great work and things are complex. The media controls are very useful.

[austwhite]

@Angelos59
Sounds like a different issue and should be raised with the Issues on Alexa Media Player.
This issue was only about exposed entities and is fixed now

[Angelos59]

thank you

…

On Sat, May 6, 2023 at 6:16 PM Brendan White ***@***.***> wrote: @Angelos59 <https://github.com/Angelos59> Sounds like a different issue and should be raised with the Issues on Alexa Media Player. This issue was only about exposed entities and is fixed now — Reply to this email directly, view it on GitHub <#92459 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AU2UVIRGEHKZRIVHDXSIGOLXE3EUZANCNFSM6AAAAAAXVJXHNE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Angelos Spetseris 508 769 7093