core icon indicating copy to clipboard operation
core copied to clipboard

Problems with Voice Preview Edition after update to 2025.5.0

Open MarcoEnd opened this issue 7 months ago • 4 comments

The problem

Voice PE reacts correctly to the wakeword but when I say a command very often the LED ring is blinking (twice) red and the command is not being excuted. I have noticed that if pronounce very clear and slowly the command is sometimnes recognized but in most of the cases the LED blinks already after the first word of the command. I am facing this issue after the update to 2025.5.0 before it was working fine.

What version of Home Assistant Core has the issue?

2025.5.1

What was the last working version of Home Assistant Core?

2025.4.x

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ESPHoma - Voice Assitant PE

Link to integration documentation on our website

https://www.home-assistant.io/integrations/esphome/

Diagnostics information

home-assistant_esphome_2025-05-10T16-53-26.197Z.log

Example YAML snippet


Anything in the logs that might be useful for us?

The debug information from the voice assistant:

stage: done
run:
  pipeline: 01gzjrcbzyjffj6v88wfp59z4c
  language: de
  conversation_id: 01JTXH2AD5CP7BCYQ42TPBT9XC
  tts_output:
    token: IafJzGkweC3qd-WmecsGSg.flac
    url: /api/tts_proxy/IafJzGkweC3qd-WmecsGSg.flac
    mime_type: audio/flac
events:
  - type: run-start
    data:
      pipeline: 01gzjrcbzyjffj6v88wfp59z4c
      language: de
      conversation_id: 01JTXH2AD5CP7BCYQ42TPBT9XC
      tts_output:
        token: IafJzGkweC3qd-WmecsGSg.flac
        url: /api/tts_proxy/IafJzGkweC3qd-WmecsGSg.flac
        mime_type: audio/flac
    timestamp: "2025-05-10T16:44:19.256735+00:00"
  - type: stt-start
    data:
      engine: stt.home_assistant_cloud
      metadata:
        language: de-DE
        format: wav
        codec: pcm
        bit_rate: 16
        sample_rate: 16000
        channel: 1
    timestamp: "2025-05-10T16:44:19.258112+00:00"
  - type: error
    data:
      code: stt-stream-failed
      message: Unexpected error during speech-to-text
    timestamp: "2025-05-10T16:44:20.812826+00:00"
  - type: run-end
    data: null
    timestamp: "2025-05-10T16:44:20.813806+00:00"
stt:
  engine: stt.home_assistant_cloud
  metadata:
    language: de-DE
    format: wav
    codec: pcm
    bit_rate: 16
    sample_rate: 16000
    channel: 1
  done: false
error:
  code: stt-stream-failed
  message: Unexpected error during speech-to-text

Additional information

No response

MarcoEnd avatar May 10 '25 17:05 MarcoEnd

Hey there @ottowinter, @jesserockz, @kbx81, @bdraco, mind taking a look at this issue as it has been labeled with an integration (esphome) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of esphome can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign esphome Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


esphome documentation esphome source (message by IssueLinks)

home-assistant[bot] avatar May 10 '25 17:05 home-assistant[bot]

I confirm. I see this in esphome log:

Image

bigboban avatar May 11 '25 07:05 bigboban

Some interesting note - i have second assistant on M5 stack echo and it works fine.

bigboban avatar May 11 '25 07:05 bigboban

Hello came here after having some problems with a Voice PE as well and searching around as well as contacting support.

I get I think a similar error, from the system log:

Logger: homeassistant.components.esphome.manager
Source: components/esphome/manager.py:391
integration: ESPHome ([documentation](https://www.home-assistant.io/integrations/esphome), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+esphome%22))
First occurred: 15:25:36 (4 occurrences)
Last logged: 15:26:36

Home Assistant Voice: [W][micro_wake_word:375]: Wake word detection is already running
Home Assistant Voice: [E][component:082]: Component voice_kit is marked FAILED
Home Assistant Voice: [W][component:237]: Component esp32_ble took a long time for an operation (209 ms).
Home Assistant Voice: [W][component:238]: Components should block for at most 30 ms.

Logger: homeassistant.components.cloud.stt
Source: components/cloud/stt.py:119
integration: Home Assistant Cloud ([documentation](https://www.home-assistant.io/integrations/cloud), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+cloud%22))
First occurred: May 11, 2025 at 18:07:16 (13 occurrences)
Last logged: 15:19:38

Voice error: Error processing en-US speech: 400 Invalid HTTP request.

However, different from OP my Voice PE does NOT react to the wake word, it appears to be deaf now, I only get the STT error in the logs only by manually triggering the assistant with the button on the Voice PE. What is similar to @bigboban is that I also have a second assistant, also a Voice PE, connected to HA, and that one continues to work as before, only the one of them appears to be broken.

Let me know if I can collect/send any additional logs or do any tests, if helpful

clayhands avatar May 12 '25 22:05 clayhands

I still have this problem. Does anyone find a solution?"

brianajensen2 avatar Jun 21 '25 19:06 brianajensen2

I have to change the text to speech engine from Google to Google Translate and it works again.

inertia666 avatar Jun 26 '25 06:06 inertia666

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.