Conversation response stopped working on voice PE devices

Configuration Voice Assistant
1

I have two voice PE devices. I use voice extensively, and make heavy use of set_conversation_response in my automations. It’s been working fine, but all of a sudden yesterday, I’m no longer hearing anything from conversation response actions. The same automations work fine on my Wyoming satellites.

One very odd thing though is that this code (from developer tools) works fine (although not every time):

action: tts.cloud_say
data:
  cache: false
  entity_id: media_player.home_assistant_voice_bedroom_media_player
  message: Hi there and good morning, dave.

But this code (a test automation) is triggered, but I hear no response:

alias: Response Test
description: ""
triggers:
  - trigger: conversation
    command: Testing
conditions: []
actions:
  - action: tts.cloud_say
    metadata: {}
    data:
      cache: false
      entity_id: media_player.home_assistant_voice_bedroom_media_player
      message: This is a test of the voice response script.
mode: single

Since I didn’t change anything on my end, I don’t know where to go next. I’ve rebooted both HA and the voice PE devices with no luck.

2

Update: this appears to be (frustratingly) intermittent. As I was doing more testing, it’s working fine again now. Maybe an HA cloud issue?

3

And now it’s broken again.

4

Same here, except for the fact that it has never worked once for me.

5

I’ve seen the issue reported in another thread, but it doesn’t yet seemed to have made its way to a bug report. I’m going to try to figure out how to file one, because in its current state, it’s not really usable for me. :disappointed_relieved:

6

I now have this same issue today with VPE device not responding. The pipeline seems to think it is responding but the audio is never played from the device, It seems like maybe it is whenever it uses a cached response that it fails.

Does anyone have any ideas on how to fix this? It is hard to use a voice assistant without responses :slight_smile:

1 Like
7

Out of curiosity, did you recently update? I recently lost voice response too, but I have been playing around with local pipelines and thought that I may have broken something. I recently tried going back to GPT/Cloud and the issue persists, so not I am wondering if it was the update that I recently did that broke it. My voice debug is acting like it worked perfectly and my local logs show everything as working correctly.

Edit: Mine started working mysteriously after a couple of hours. shrugs

8

I did also update! However; I too have found that mine is also now working again.

I’m honestly not sure what the issue was, the only thing I changed was the power source, that may have fixed it of could be coinsidence.

9

Both of mine are still in the condition where I occasionally hear a voice response, but most of the time I don’t.

10

I’ve seen some corrolation between wifi signal strength and this issue recurring.

Potencially on this device responses are somehow more sensitive to wifi issues than requests. I added a voice PE device to an additional room where 2.4ghz traffic was congested, 9/10 requests got no response, after resolving the congestion (changing channel on the AP ) voice responses arrive on the device much more frequently.

This is just my experience but I would love to know if anyone else is able to replicate this.

11

I have two that have been updated.

Both are less than 1 meter away from an access point.
One is “native” and one is ESP Builder controlled firmware.

Both have stopped responding.
I’ve changed all the voice settings I can think of and even factory reset one.

Very frustrating as I am really really eager to try the new conversation and prompt modes in voice!

12

Im now experiencing this too, in debug it thinks it responded but no sound was heard.
I have it in the same room as my AP so unlikely in my case that its a wifi issue. It was working fine a few days ago. The only change for me is the latest update to HA

13

I am seeing this too. Mv Voice assistant PE stops responding after automations use TTS to make announcements. If I check the PE it says Voice assistant can’t connect to Home assistant. A restart fixes it until the automation runs again