I’m trying to finish the setup of the new voice assistant box, the device seems all there and ok but i get this error when I try to finish the setup. I’ve seen a few posts on reddit, etc with people having the same issue. I’ve followed everything I can find but not working. Most pointed to setting, network and to “fix” the local network section. Nothing works and I cannot find any errors in the logs. I do have cloudflare setup for external, i have a letsencrypt wildcard cert installed and I connect local with https no problem. If i put an ip in this section like some suggest i get an error because certs don’t apply to ip’s. No idea at this point what to look at.
Well, reading more it seems that home assistant voice cannot communicate with home asssistant on https. Don’t understand why, seems stupid but removing my cert and going back to http allowed it to finish setting up. If i want https guess I have to use a reverse proxy and leave http open for direct connect.
In the HA UI->Settings->System->Network there is a section: “Home Assistant URL”.
It is my understanding that the second entry labelled " Local network" is the URL handed to the VPE for it to reach HA. This URL can be https, and it does work (at least in my case).
You mentioned above that you tried this and it didn’t work. My guess is that is a DNS resolve problem?? In other words, when the VPE tries to reach your HA via that https URL, is it asking an in-the-home DNS server to resolve the local IP Address? Of course this would be the same question regarding how your in-home devices are able to connect to your HA successfully
[Edit] On the other hand, I’m less sure about a wildcard certificate. Maybe related to this Discord Thread?? not sure??
I’m using pihole for my dns, everything is resolvable from my lan and IOT network. I have a valid letsencrypt cert, it is a wildcard but i’ve never encountered a single problem with any tool using that. Simply removing my cert and making home assistant use http fixed it…
Adding this here in case it helps anyone running Home Assistant in a Docker container. I had this issue, and fixed it by changing the URL in HA UI->Settings->System->Network.
Instead of the automatic “Home Assistant URL”, which was defaulting to the Docker VLAN one with the default 8123 port, I changed it to the host IP address with the host bound port, which is 30103, the port TrueNAS Scale binds to the internal 8123 port in docker. Basically I changed it to the address I access the WebUI through.
Makes sense now that I think of it, since the HA container has no way of knowing which host IP and port its internal port is bound to. Easy to avoid if you bind 8123:8132 during deployment, instead of 30103:8123 as TrueNAS did for me.
Well, this is really unfortunate. I spent a good deal of time today attempting to get this to work only to realize that, for whatever reason, the PE doesn’t support local certificates. I have a bunch of other ESPHome devices that have no issues resolving HA via my proper, local, cert. My HA address is resolvable everywhere on my network and I have no issues bridging media devices across VLANs in my implementation - so it seems really odd that PE can’t connect to a valid HTTPS endpoint. I bought a few of these and they are, ultimately, bricks to me as I’m not going to undo proper security configuration on my local network to have some voice assistant hardware.
Curious why this isn’t called out anywhere in the docs, given this seems to be a rather restrictive oversight.