Home Assistant still seems to use UDP connection for voice assistant in 2024.5.2

[Jojonintendo]

The problem

Hi. Latest Home Assistant version 2024.5.2, in conjunction with ESPHome 2024.4.2, was supposed to use the API connection instead of UDP for voice assistant.

On the ESPHome side I see signs that indicate this is the case:

[D][api.connection:1210]: Home Assistant 2024.5.2 (192.168.1.117): Connected successfully

On the HASS side however, the assist seems to stay on all the time after the first try, and finally shows this in the logs:

2024-05-08 09:51:48.164 WARNING (MainThread) [homeassistant.components.esphome.manager] Voice assistant UDP server was not stopped

In the attached logs you'll see that HASS doesn't appear to indicate anything relevant, except for the line above. On the ESPHome logs you'll see two attempts at voice assistant, with a HASS restart in between.

This is with the wake-word detection disabled in HASS.

All the services are containers on the same machine, they all connect fine (Node Red, Mosquitto, Z2M, piper, whisper, etc).

I'll be glad to provide any additional log if needed, thanks so much for your time.

hass.txt
ESPHome.txt

What version of Home Assistant Core has the issue?

core-2024.5.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Voice Assist via ESPHome

Link to integration documentation on our website

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

Diagnostics information

home-assistant_esphome_2024-05-08T08-16-30.742Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

`2024-05-08 09:51:48.164 WARNING (MainThread) [homeassistant.components.esphome.manager] Voice assistant UDP server was not stopped`

Additional information

No response

[home-assistant]

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)}}

[issue-triage-workflows]

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.

[jesserockz]

This is actually just a log line that I forgot to change when adding the api audio. It is not an indication that it is still using UDP.