#Voice PE "Unable to connect to Home Assistant"

1 messages · Page 1 of 1 (latest)

wet aurora
#

Any idea why I might be seeing this?

Not sure what is relevant, but here is some info:

  • LED light controllable from HA - indicating it is on the network and HA can communicate with it
  • HA is a docker install
  • Voice PE is on subnet without internet access, but for the point of debugging I gave it internet access but didn't fix it
  • Wake word appears to work (voice pe lights up) but doesn't reply to questions

second screenshot was triggered by using the wake word, and asking the device what time it is. However, it never speaks the response. Clicking "Play audio" does make the response play on my computer which I assume means the TTS is working, It doesn't play on the voice pe though

Lastly, sending tts directly to the media player on the device doesn't work either.

image.png image.png image.png
wet aurora
#

i do hear the "chime" when I trigger listening using the wake word so I don't believe it a faulty speaker or anything like that

ivory moth
#

Might need to factory reset, remove from ha, reboot everything and try again

wet aurora
#

Tried that a couple of times

#

Fixed it. Turned out that the device was being given the wrong url for the audio. Set the local network address in HA settings and it is working like a champ now. I've had HA installed for almost 5 years now, a little surprised this is the first time this issue is cropping up but 🤷 . It works so I'm happy

image.png
stark surge
#

Same error. Same resolution.

I think there's a few items I've had issues with that this might resolve... it looks like running it in a container, it has auto-detected an IP, but manually setting it improves the connectivity.

cyan stratus
#

I'm surprised this isn't mentioned in docs.

tranquil narwhal
#

Cc @tidal loom

stiff marlin
cyan stratus
#

it should be http looks like

wet aurora
stiff marlin
#

Great! just wanted to know that https worked. Thanks

tidal loom
#

Hey! https does work, yup.

I don't think its intentional, but it is very plausible that manually introducing the url avoids any error with auto-connect. I think its a good idea to add it to troubleshooting though

tidal loom
stiff marlin
wet aurora
toxic prairie
#

Just got the device today and I'm having the same problem. Also changed the HA url. But the automatic url already had the correct one set. Where do I see the log if it's trying to connect to the correct url? Or any other logs which would help me.

tranquil narwhal