Hey Sam,
Thank you for the reply. I did that, tried to shutdown the PC running the HA Docker, rebooted it number of time, removed the dongle etc but it is still not working. I’ve saw some other errors in the log …
homeassistant.config_entries.OperationNotAllowed: The config entry SONOFF Zigbee 3.0 USB Dongle Plus V2, s/n: 20220712155050 - ITEAD (zha) with entry_id e0027f242d207babed50b1459f28cf6a cannot be setup because is already loaded in the ConfigEntryState.SETUP_ERROR state
In addition to that it would be interesting to see how we can use the Google Nests around the house and the HA app on our mobiles. Maybe this is common knowledge but I haven’t seen anything - I’m at the beginning of the voice journey.
My HA instance runs on a KVM VM in a rack in the laundry so having a mic on that instance wouldn’t be useful for my use case hence the question on whether we can take advantage of the existing infrastructure.
Having said that what’s possible today is very impressive (saw last week’s voice stream)
Exclude option in history is deprecated is in my log.
How should we exclude then in history?
How much did you pay for it?!
But I feel his pain… I can’t even get an answer how to make a USB mic work with HA
you could try and update the firmware on the sonoff (its pretty easy) - maybe its outdated?
I’ve heard both of the speakers on mine ‘pop’ once, so I am fearing it is broken. Maybe ESPHOME wasn’t ready - I’ve read that using mic/speakers cannot happen simultaneously.
Its not really a big deal as they are fun, the green color is good feedback, but the m5 is not ‘usable’ in real life to me. I’d rather have a cool phone until hotword works
easy lemonade recipe: Rollback your HA to a backup - disable updates, and never come to the forums again 
Seven-and-a-half bucks a month. Not to mention that while I have to fiddle unplanned with HA for hours now I wont be available for my daytime job (my own company).
But that was just a sarcastic hit on the famous Meat Loaf song … but anyway, my system is a desaster after todays update. The second time where everything went south after an update (9.5 to 10 and now todays update). My max frustration level has been reached now.
I don’t like your attitude,
however I might have a solution for you.
this can happen after restoring a backup,
a full restart fixes this issue. not sure how but it happened to me in the past
is anybody experiencing issues with MQTT on this version ?
Perfect update for me again team, huge thank you to all the Devs and beta testers!
I’m not a huge fan of voice, none of the assistants seem to understand Scottish, but I can see this being well used by others.
Absolutely! It has already been partially reverse engineered. It is not on the top of my priority list as I don’t have a dock with those functionalities so it is harder to test, but if you would like the functionality sooner, you can use the services.
The Vacuum: Send Command will allow you to send commands directly to your robot. I plan at some point to have documentation for this - but it is a tall order.
For example the command to empty your dock is : app_start_collect_dust
Then you would select your vacuum as the entity and send the command, and it should work!
Can you please share a meaningful guide. I’m using Debian PC and HA on Docker Container. I think that the Zigbee dongle is - ZBDongle-E (EFR32MG21)
And I don’t like your haircut. So what? You don’t know me and I don’t know you. That’s fine by me, don’t make this personal.
I am frustrated by this updates because I have a lot of time to spent with totally senseless things now to get my system up and working again. Time I won’t get back. I do not have problems with the usual bugs that might come with an update but the last two updates of HA were just too much.
An update of a home automation should never ever break a running system the way todays update did. What I expected was a well tested and smooth update with little or even no manual work at all.
And yes, I have restarted HA already. Twice. No change.
And what you’re running into is a bug that no one found in beta. So relax and vent your frustrations elsewhere. Otherwise, join the beta so we can catch these issues before release.
don’t you?
Ok I didn’t mean to make it personal. I know stuff can be frustrating if it doesn’t work. however, keep in mind the hard work people put in to developing HA and deliver it to you for absolutely no cost at all.
You can of course ask questions, but bashing this work is not done for me.
if you have questions or problems, you can ask them nicely. And if you are depending on HA don’t update at the first day, but wait a couple and check the forum to see if there are any critical issues for you so you might can wait for a fix.
Please don’t continue the personal arguments. Thank you.
I’m using a custom skill (Hasska), and my Alexa YAML configuration seems to be working as it did previously, as it did throughout all 9 betas.
Also, no issues with Alexa Media Player-derived entities or services.
Did you already update debian?
There’s a bug in udev not creating /dev/serial/by-id/ symlinks.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035094