buoyant flame
Hello, i am new to HA and i buy the HA voice PE. I want to start / configure this device.
Unfortunately, I'm getting an error message. Can someone help me?
Here's the message translated into English:
The voice assistant cannot connect to Home Assistant.
To play audio, the voice assistant device must connect to Home Assistant to retrieve the files. Our test shows that the device is unable to reach the Home Assistant server.
thin pier
Hello, i am new to HA and i buy the HA voice PE. I want to start / configure thi...
is your HA server and your VPE on the same netowrk/subnet/vlan?
do you have any other fancy network setups or firewalls that may be causing a connection issue?
buoyant flame
is your HA server and your VPE on the same netowrk/subnet/vlan?
do you have any ...
Yes, my Home Assistant server and the Voice Preview Edition (VPE) device are on the same network/subnet. There are no VLANs or special network setups. I have a manual SSL certificate configured, but the local URL is currently set to "Automatic," which causes a conflict because the internal URL does not match the certificate. There are no firewall rules that should block access.
thin pier
Yes, my Home Assistant server and the Voice Preview Edition (VPE) device are on ...
i recommend that you plug into pc and reinstall the firmware using the procedure here - https://voice-pe.home-assistant.io/guides/firmware-reinstall/
this will also allow you to add your wifi creds during the process so you wont need to use the bluetooth provisioning.
once its reinstalled and connected you will hopefully be able to add directly from home assistant UI
buoyant flame
i recommend that you plug into pc and reinstall the firmware using the procedure...
Okay, I did that. But unfortunately, it didn't help.
thin pier
Okay, I did that. But unfortunately, it didn't help.
track down the VPE's ip address using your routers (or whatever your dhcp server is) dhcp table. make sure its pingable and then try adding it manually by adding it to the ESPHome integration
buoyant flame
track down the VPE's ip address using your routers (or whatever your dhcp server...
Ping works. Unfortunately, adding it manually via the esphome integration didn't work. A factory reset (holding it down for 20 seconds) didn't help either.
thin pier
Ping works. Unfortunately, adding it manually via the esphome integration didn't...
do you have a terminal addon instaleld on HA? can you ping it from there?
buoyant flame
do you have a terminal addon instaleld on HA? can you ping it from there?
yes
buoyant flame
do you have a terminal addon instaleld on HA? can you ping it from there?
these are my network settings
thin pier
okay, plug into pc and connect to it using this page - https://web.esphome.io/ and view the logs
see if there is any errors or anything there. when its starting up and/or when you try to connect to it
thin pier
it looks like its showing connected. does it show in the device list of the esphome integration at all?
buoyant flame
yes
buoyant flame
it looks like its showing connected. does it show in the device list of the esph...
I use a self-signed SSL certificate for my HA. Do you think this could be a problem? And are the network settings I sent you above correct?
thin pier
it wont be the cert and in any case it looks like its connected fine. although there may be no voice pipeline set up because the voice assistant onboarding seemed to fail
do you have whisper/piper addons installed? (usually the onboarding would do this but i dont know how much it actually did)
buoyant flame
do you have whisper/piper addons installed? (usually the onboarding would do thi...
these are all my addons if that's what you mean
thin pier
these are all my addons if that's what you mean
okay it looks like the unboarding didnt install whisper and piper. you should install them
install, start and ensure set to "start on boot"
buoyant flame
👍 ok i try it
thin pier
once you have them you can create a voice assistant pipeline so they can be used
buoyant flame
once you have them you can create a voice assistant pipeline so they can be used
like this?
thin pier
bingo you now have the pieces installed now you need to ensure you have a voice pipeline
go to settings -> voice assistants
how does that look?
buoyant flame
I would do it this way. Is that right?
thin pier
yup that looks good. if thats set as the prefered pipeline then the voice PE should now be able to access and use it
buoyant flame
I did it that way, but unfortunately it doesn't work. I just reset the HA Voice PE again, but it didn't work. 😦
thin pier
try manually setting the pipeline in the voice PE device page
what happens when you try to use. either by calling the wakeword or by pressing the button?
buoyant flame
try manually setting the pipeline in the voice PE device page
Okay, I did that, but to no avail. I just restarted.
buoyant flame
what happens when you try to use. either by calling the wakeword or by pressing ...
Nothing. I can see in the logs that my request arrived, but it doesn't respond. The LED does change, however, when I speak with "hey nabu."
thin pier
so the device seems to be receiving the command and sending to HA but you are not getting a responce?
buoyant flame
Yes, exactly. I don't have any voice output. Here are the logs. I said "hello," okay, nabu.
thin pier
ok its receiving the command and generating a responce
on the pipeline page hit the 3 dots and open "debug" and look at the log of the call
should see something like this
thin pier
it looks like the piper part is the issue
in addons go to piper and look to seee if anything is wrong in its log
thin pier
try restarting the addon on that page and then restarting the wyoming integration connection to it
so the addon is freshly started and freshly reconnected to
then try the voice command again and see if there if there is any difference in the pipeline debug
buoyant flame
and the log from the piper addon:
[23:18:40] INFO: Service exited with code 256 (by signal 15)
s6-rc: info: service piper successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service piper: starting
s6-rc: info: service piper successfully started
s6-rc: info: service discovery: starting
INFO:main:Ready
[23:18:47] INFO: Successfully send discovery information to Home Assistant.
s6-rc: info: service discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
thin pier
can you try setting a different voice in the pipeline maybe?
it does seem that the problem at the moment is piper but i am not sure why
thin pier
ok lets try calling piper manually for a TTS
in dev tools go to the actions tab
select the action tts.speak
something like this
buoyant flame
check.
thin pier
piper as the target and media player as the vpe
then hit perform action and see what happens
buoyant flame
Die Aktion tts.speak konnte nicht ausgeführt werden. Unable to determine Home Assistant URL to send to device. Configure internal and external URL in general settings.
buoyant flame
so its unable to tell the vpe how to access the audio stream
Okay, then at least we know why it doesn't work. Do you know what could be causing this?
thin pier
go back to your network settings
thin pier
these are my network settings
theres an error here
switch on the automatic in the local network section of home assistant URL
you could also manually put it in if you want/need to based on your settings
this might also be why the auto onboarding setup failed i guess
buoyant flame
"You have configured an HTTPS certificate in Home Assistant. This means your internal URL must be set to a domain covered by the certificate."
thin pier
put in there what you use to access home assistant in your browser locally
if that fails then it might indeed be your cert not set up correctly
buoyant flame
thin pier
so your not using the domain set in the cert at all?
thin pier
a certificate usually has a domain ascociated with it but you are connecting directly by ip
buoyant flame
I only use the certificate locally. Which domain should I use? I always access my Home Assistant via IP address.
thin pier
if your only accessing HA locally then i would ditch the cert and just connect via http
i dont know enough about certs and how they work with home assistaant to really troubleshoot. but we did get everything set up for the voice to work once that issue is solved.
if you want to keep the cert then you might be better off starting a new thread in #1284966540617449515 and asking specifically about that.
someone with more knowledge about that kind of configuration might be able to get involved
buoyant flame
Okay, all right. I'll open a new thread there and ask. Thank you very much for your help and support!
thin pier
no worries. i am sorry i couldn't get you over the line but if nothing else we found the true problem
