Thanks! I found out the hard way. I replaced my SSD then did a fresh install and restore…
5 hrs later, I removed everything in HACS and found the solution. I wish I could see your reply much sooner. But thanks!
I think I might have found (a little) bug.
I have a device (relais board) that post all relais as switches.
I’ve 'converted the ones that are lights to lights and added the light to the correct area.
When I go trough entities it is in the correct area:
now when i look for the exact same device trough the expose panel:
the area is the original location of the ‘before type of a switch change’
Same boat here. I tried re-linking Nabu Casa to Google Assistant and also re-syncing and nothing would show up in Google Home. I did not test beta either. I eventually found the old menu was still showing before Voice Assistants showed up both in the web and companion app. I still had to manually expose things again and then re-setup actions in the Google Home app. It works now though as expected.
Anyone has any solution for ecowit? my HA is on a VM so i rolled back to 2023.4 and removed the ecowit Hacs integration then i installed again the update and the official ecowit addon.
Now i get this error
Logger: homeassistant.config_entries
Source: components/ecowitt/__init__.py:30
First occurred: 7:42:54 PM (1 occurrences)
Last logged: 7:42:54 PM
Error setting up entry Ecowitt on port 4199 for ecowitt
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/ecowitt/__init__.py", line 30, in async_setup_entry
hass, DOMAIN, entry.title, entry.data[CONF_WEBHOOK_ID], handle_webhook
KeyError: 'webhook_id'
Thx for the help. Tried this but it did not helped …
Wish I would have read this before upgrading to 2023.5. How was this missed? I assume a restore will not solve this since they are all now removed from Google Home. Ugh
Agree, After reading beta releases I was really looking forward testing piper. Getting rid of my cloud based tts is something I’m looking for a long time. However for German piper is not usable, …
If you have a complex HA configuration and used HA for a long time, you should know to NEVER install a .0 release, unless you have time and an environment (i.e. a patient family) to debug things. I generally wait a month or so and get to the final dot release for that month before updating. At that point things are generally pretty stable, or at least the potholes mapped out.
3 Likes
So I was able to get mine working… again. I wish there was a clean way to migrate integrations, but that’s what I get for HACS.
I have a verified Ecowitt HACS integration. This is how I did it.
-Using HA file editor, go to “/config/custom_components/ecowitt/”
-Download “__init__.py”
-Edit line 21 to " async_get as async_get_entity_registry,"
-Save file.
-In HA file editor, upload file, overwrite existing one.
-Reboot.
-Update to 2023.5
-Profit.
Good luck all!
7 Likes
Just submit a text command as if you were talking to google home (nest) speaker. Once you configure it you’ll have a service google_assistant_sdk.send_text_command
Details in the documentation:
https://www.home-assistant.io/integrations/google_assistant_sdk/#services
Yeah, but the Google assistant assistant integration doesn’t use the zone trait for vacuums, it was never implemented… So I can’t use a command to clean a room, since GA doesnr know what Todo…
Vacuum integration only exposes like start,stop …
You just have to be sure you are clearing you cache. On firefox I use a cache clearing extension because it holds on to things even when press crtl+f5. I had the same issues for a while before I cleared it out.
Mine showed up, without any obvious action from me. Maybe give it time?
Why can’t i add entities created through MQTT to voice Assistant? they show message that they don’t have “unique id”. Is that possible to configure it to have unique id?
The point is to link Roborock to Google Home, without HA in the middle. Once you have it you can send a command from HA to Google Assistant like you were talking to the google home speaker. This assumes that:
- you can control Roborock from google assistant
- google assistant allows you to start cleaning a zone/room
As I don’t have Roborock I can’t confirm above 2 assumptions
Ok, yeah makes sense, but I don’t want to expose roborock/Xiaomi directly…
The zone trait is avaible in GA , someone just needs to start developing it :+)
Just to help people finding the same trouble…
After this update my RfxTrx integration failed to communicate with the RFXCom USB receiver.
Unplugging, HA restart, server restart, nothing worked.
Removing the integration and adding it again did the trick.
Besides that a seamless update, good job with an installation as big and complex, as i have 
All my entities wich were populated to alexa via Nabucasa cloud are removed …
I heavily renamed them in alexa know everything is lost and I have to rebuild everything -,-
1 Like
No need to. Infinty knows.
He asked for help from the developers to update his custom components. I only saw one helping him and that is not so long ago.
Giving volunteer contributors only 4 weeks to recode and release a significant change is not a very friendly way to engage the community. If it was just a matter of changing a few code lines then I could understand it. But this is a matter of giving people 4 weeks of warning for a change where you basically have to rewrite all the code. There should have been at least a 3 month warning. And a bit of help when the developer asked for it.
I had to uninstall the excellent component I used for my venetian blinds and replace it with something I like less.
I cannot understand why this removal of the old code had to happen in 4 weeks. Why the rush? It is not an extra effort to wait. Especially when you know a developer of several (4 or 5) front end custom components have asked for help and time. We all lose on this behavior.
14 Likes