I ordered 2 Voice PE’s and neither one can be added to HA. Both say “Unable to connect” when attempting to connect to my WiFi.
I have a WiFi 7 router and my 2.4, 5, and 6hz bands are all shared via the same network name using MLO. I see the Voice PE device in bluetooth and showing “connected” when I’m doing the setup.
The error doesn’t give any more info. There is no further troubleshooting. Nothing in the HA logs…I do not have Bluetooth support for my HA Yellow. What am I supposed to do…?
I was just having the same problem this afternoon, I switched over to the web browser and for some reason it worked through that on the laptop and not the phone app.
Do you have Bluetooth in HA? I don’t see the Voice appearing as a discovered device on the web GUI, only in my phone.
No I started with the phone it got to connect to wifi, then it appeared in the device page in home assistant. I do have a blue tooth proxy so that might of picked it up.
Mine was not able to connect to my 5Ghz network that has WPA3 and Management Frame Protection enabled.
Putting it into my IoT specific network (2.4Ghz, WPA2, no management frame protection) worked.
I would guess it cannot handle either WPA3 or management frame protection, which sadly even in 2024 many new devices struggle with.
I don´t know if it really was the case but I had similar problems and it worked after I deactivated Pi-Hole, that was running in my network.
But as said, I´m not 100% sure - but worth a try.
Yeah, Bluetooth is the second method of connecting, unfortunately I don’t have Bluetooth support in my HA, so can’t use that.
This is probably the issue then. My MLO network has both WPA3 and Management Frame Protection enabled. I can’t disable all this without completely destroying my home WiFi setup.
Is there anyone from the HA dev team that may know a way around this or am I dead in the water with these devices?
As a test, I created a new “Guest” network that only used 2.4/5GHz and didn’t have Management Frame Protection on it and was able to get the device added successfully through this network so it does seem to be related to WPA3/Management Frame Protection. I will create a bug report on the Voice PE Github.