Stuck setting up home assistant voice preview

[wraith shale]

Hi everyone,

i just setup my home assistant voice preview satellite. after initial bluetooth configuration, it was added to the esphome section. Then on first setup (and when you click the button "set up voice assistant" on the device, i get stuck.

The sattelite lights its rings for a few seconds when it tries to connect, then it goes dark again and HA will show this screen.
The device itself works.

Would love any input to debug this.

[opaque pollen]

do you have some kind of interesting network setup with vlans etc...?
do you use a self signed certificate on your HA install?

[wraith shale]

while i have vlan, the HA container and the voice satellite are in the same one. after BLE setup i was asked for the nodes IP, so i entered that. i made sure its a fixed ip. the device works. i can turn on and off things.

[opaque pollen]

you got it working? or do you just mean you can change settings on it in the esphome integration?

[wraith shale]

the device works. i can turn on and off things by saying "ok nabu". i also can control the volume from HA itself, i see the correct states updating etc. i just cannot click this "set up voice assistant" button and do whatever is behind it.

[opaque pollen]

does it respond when you get it to do something?

if you are sending commands through it then its at least partially already set up

also my earlier question:
are you running https locally? specifically do you use a self signed cert?

[wraith shale]

it chimes after the wakeword. flashes its leds. accepts the voice input, does the command. does not say anything.

[wraith shale]

i use the ip locally but have a domain setup with signed https

[opaque pollen]

so most of the communication to HA is done by a connection that's established by HA with the API. however playing the sound sound of the responce requires the VPE be able to connect to the HA to access it. the link is generated HA side and sent by the api to the VPE which then tries to stream it. the generates link is based on settings in the network settings. this can cause fromlems with a cert.
go to: settings - system - network and see if there are any coimplaints in there. specifically in the home assistant url section

the url in there is how the link is generated for the device to stream. that link needs to work from the VPE

[tropic oasis]

That wizard contains nothing that you can't do manually. Check your pipeline, especially TTS part. Probably you have it wrong, or maybe you have https HA URL in host settings (it gives troubles on ESP side too).

[wraith shale]

thanks michael, the network setting worked. i didnt even know this setting exists. its an old HA instance and most of my stuff is still in yaml. The Setting was still set to automatic, which grabbed the docker containers ip. i changed that and everything is fine now. Thanks!

i get voice responses now and the setup guide works

[opaque pollen]

I spoke to Frenck about this and he mentioned that the recommended settings is to use "host" networking for container installs which should have prevented this issue. however its a good point that it doesn't really tell you how to solve the issue.

the plan is more to raise awareness of the problems that cause this issue as opposed to explaining them when the setup just fails.

A PR has been put in to raise a repair issue if the docker networking setup is in a non-recommended state - https://github.com/home-assistant/core/pull/142259

[wraith shale]

while that is true, running something as host is not always (and i would even say in most cases) applicable. my home-assistant and other containers run isolated in their own docker network and only get accessed through a proxy (traefik in my case). i'd say this is pretty common when selfhosting using docker.