I am having trouble setting up my HA Voice PE in HA. I was able to pair it via bluetooth and connect it to my wifi. When adding it to ESPHome, it gives an error message: "Entity not found". It appears in the list of ESPHome devices and some functionality is present. For instance I can contol the LED ring from HA. It even understands and performs actions, but there is no audio feedback.
#HA Voice PE - Can't set up voice assistant
1 messages · Page 1 of 1 (latest)
have you done a reboot of ha and voicePE? If not working after that, then post logs and we'll take a look.
What logs?
esp logs and maybe supervisor logs. I'm off for today, other will pick it up from here. Good luck!
Here are the esp logs.
And here are the HA logs. I'm running it as a VM on my TrueNAS server.
Nothing strange in here. You can try to refalsh the voicePE using this link: https://esphome.github.io/home-assistant-voice-pe/
Install firmware on Home Assistant Voice PE.
I reflashed it. I was able to get through the bluetooth pairing and connecting to Wifi part of the process. When adding to ESPHome, is errors out and says "Entity Not Found".
It shows up in the list of devices under ESPHome. When I click on "Set up voice assistant", the process does not complete and it gives the same error as before.
I would suspect there's some trouble with your HA installation.
Did you try to reboot server?
The first circled item: that is the firmware installed when I reflashed the device.
selected pre-release? suggest flash with stable 9.0
if problem searching, dont beta..
Second circled item: there is an entity on the device called “Beta firmware”. It’s a toggle, and is currently toggled off.
Did all of that. Same error as before.
How is your network set-up? Set HA to automatic ip and set static ip for HA in your router. Reboot
HA already had a static IP. I use pfSense on my router and have rules set up to allow traffic from ioT devices to HA.
I’ve checked my pfSense firewall logs and it is not blocking the HA Voice PE device from reaching HA, nor is it blocking HA from reaching the device.
mDNS working udp? Firewall ok for dns port 53?
mDNS is working via the Avahi package in pfSense. It is set to broadcast mDNS across all subnets. As for the dns port 53, I'll check that when I get home.
Appreciate all the help you've given so far!
No problem
I checked the firewall rules, and I do not see any that would block DNS on port 53 on any of the LAN interfaces.
I removed the device from HA, reset the firmware to 25.9.0, and added to HA again. When adding it to ESPHome, it auto updates the firmware to 25.10.0. Could this be part of the problem?
to be honest, i dont know... doing the flashing wireless or with usb?
are you somewhere pointing at homeassistant.local in setup? (change to ip address) ipv6 port dns 5353 open? Api port 6053 open? In router disable igmp snooping. These are the options i could imagine being relevant, but i am not a vlan/proxy expert though. Have to pass that to peoples with more brains than me... 😉
In the beginning i had some connection issues too, solved by adding this to voice yaml:
maybe not related to your issue
- "are you somewhere pointing at homeassistant.local in setup?"
- I use a static IP: 192.168.10.9
- "ipv6 port dns 5353 open"
- Not on my WAN side, but that port is used by Avahi on the LAN side.
- "Api port 6053 open?"
- Yes, tested with the IP of the HA Voice PE device.
- "In router disable igmp snooping"
- AFAIK, pfSense doesn't have an option for this. So I assume it's not on.
I'll try adding that bit to the yaml with the gateway for the interface that the HAVPE device is on.
ofcourse change ip's to your needs 😉
To change the yaml for the device, do I need to first "take control" of it in ESPHome?
i believe so, yes. It will get (auto)updates through home assistant/esp though.
Okey-dokey, thanks 🙂