-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wake word not responding after update #5794
Comments
This is also happening on Korvo1 v5 boards. Also working on 2024.4.2 |
Same exact symptoms here, 2024.5.0 responds only once, reboot allows another response. |
Exactly what I experienced with the Onju PCB replacement for google mini v2 after updating to ESPHome 2024.5.0 (on latest version of HA). Reverted to previous version of ESPHome & they are working again. Only thing I noticed in the logs were several warnings of " i2s_audio.media_player took a long time for an operation" after completing the first & only wakeword. |
Thanks for the feedback. Same warning here.
Can you enlighten me on how to roll back ESPhome?
Cheers
…On May 18, 2024 3:03:39 PM EDT, gregkg ***@***.***> wrote:
Exactly what I experienced with the Onju PCB replacement for google mini v2 after updating to ESPHome 2024.5.0 (on latest version of HA). Reverted to previous version of ESPHome & they are working again. Only thing I noticed in the logs were several warnings of " i2s_audio.media_player took a long time for an operation" after completing the first & only wakeword.
--
Reply to this email directly or view it on GitHub:
#5794 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
I use the ESPHome add on in Home Assistant. Before every update, I create a backup of the add on version I’m currently using. So it's simply a restore of that. |
Today I learned something......
Always did full backups and never considered the partial restore capabilities.
That fixed the issue!
Many thanks for your help.
Cheers,
Bill
…On May 18, 2024 5:58:09 PM EDT, gregkg ***@***.***> wrote:
> Thanks for the feedback. Same warning here. Can you enlighten me on how to roll back ESPhome? Cheers
> […](#)
I use the ESPHome add on in Home Assistant. Before every update, I create a backup of the add onversion I’m currently using. So it simply a restore of that.
--
Reply to this email directly or view it on GitHub:
#5794 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
Same here and same after update to 2024.5.1 |
Thank you Bandit3112011, saved me a job. |
Ya bummer, just go into Backups, select Partial and look for ESPhome update of 2024.4.2 and flash that.
Update the device and you should be good. Other units retain the 2024.5.1 version. Hopefully a future update will fix this. It might be related to the API calls.
Cheers.
…On May 20, 2024 9:43:20 AM EDT, Bandit3112011 ***@***.***> wrote:
Same here and same after update to 2024.5.1
--
Reply to this email directly or view it on GitHub:
#5794 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
Add me to the list , same problem , same symptoms , same solution ... |
Ok pr#6849 solved the problem for me , thanks to @gnumpi |
Can you let us know how you did that? thanks |
You can add this to your config to load the i2s_audio component from the pull request: external_components:
- source: github://pr#6849
components: i2s_audio
refresh: 0s |
So, just to be sure, I update the ESP first add this to my config yaml and it should work? |
Update esphome to 2024.5 , edit your device config, update the device , test And probably remove it before next esphome update if it's merged. |
Thank you |
Mic not as responsive as it should be, used to be able to call Assit from across the room, now I have to be right on it. Quick update- returned to 2024.5.4 and the mic picks up the wake word instantly and responded well, install 2024.5.5 and you have to be right next door to the speaker and mic for it to hear you. |
Hey, that's strange as only the ring buffer size was changed. I will see if this is related anyway. Could you share your config? |
No worries, here is the config from one of them.... `substitutions: esphome: esp32: logger: ota: wifi: captive_portal: globals:
interval:
i2s_audio:
external_components:
media_player:
speaker:- platform: i2s_audioid: onju_outdac_type: externali2s_dout_pin: GPIO12mode: stereomicrophone:
voice_assistant: speaker: onju_outuse_wake_word: true number:
esp32_touch: filter_mode: IIR_16 denoise_grade: BIT8 binary_sensor:
light:
script:
switch:
|
So far I couldn't reproduce your issue with my hardware, which HA version are you running? |
The problem
I have 3 old Google Gen2s that I have converted to Assist, new boards and they have been working perfectly for 3 months now.
This morning I updated the ESPhome to 2024.5.0.
Now they speakers only respond once, If I reboot them they respond to the wake word, then nothing it’s like they are just not listening.
UPDATE - Just re-installed the 2024.4.2 version and everything is working again.
Which version of ESPHome has the issue?
2024.5.0
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2024.5.3
What platform are you using?
ESP8266
Board
No response
Component causing the issue
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: