Im having an issue with my ESP32 Proxys, They work perfectly fine when its connected to my Kitchen Access point, however when I move the Proxy to where I'd like it to live which is across the house it connects to another access point. When that happens the device goes offline and stops polling devices. I am on a ubiquiti system if that makes a difference
#ESP Home Bluetooth Proxy
1 messages · Page 1 of 1 (latest)
Are you using unique ssids for each ap or is it the same?
I have 4 APs that are broadcasting the samething, the one im trying to connect it to is Smart-Home
could the "-" be causing an issue?
I could make a new SSID for just the ESP devices that tag the same Vlan as my IOT devices
How does your system work? on ubiquiti you can pin a client to an ap but is your "smart-home" ap for all your smart home devices? Because if its all on a unified network with aps as extenders thats an easier fix than a partitioned network
Basically is smart-home working as a range extender or a unique ap
So all 4 of my APs broadcast a Main network and the IOT network, they are all unique ap with different broadcasting channels
On your unifi network find your esp32 and somewhere in settings it lets you lock the ap. "preffered ap" or "lock ap" or smth
Lock it to the one you want
When I Lock it to the Kitchen one Its too far from it to get a good signal, Also the other problem I'm having is when I set it up on my computer it works but when I power cycle it it doesnt want to connect to the network and gives an authentication error
I thought the issue was it migrating away from the kitchen ap, is it a signal issue?
When I migrate away from the kitchen ap it stops communicating with HAOS but when I lock it back onto the the kitchen ap in unifi it resolves itself
My bad, i thought you wanted it locked to the kitchen AP. Im not sure, sorry. maybe format it and set it up initially to another AP and see if HAOS picks it up. Like remove it from ESPhome, reconfigure it to another AP, and go to add devices and see if its there
Ive tried that aswell, I can get it configered when Its connected to my computer but when I powercycle it this is what I get
I have to go back in and tell it what the SSID and PWD is for it to work again
double check the pwd in your secrets.yaml
or in the config if you have it set that way
they are correct
It works when I connect to it with the usb to uart bridge
once I disconnect it from my computer and connect it to a wall plug it gives that error above
I have no clue, sorry. Im not sure what would cause that difference if its the same configs
Ill try a different ESP32 device I have it could be bad
@willow nimbus Turning on fast_connect helped
I've got 3 esp32 boards present in my ESPHome dashboard. All 3 are configured as bluetooth proxies, with identical configs (except static IP and names).
Only 2 of these proxies are visible in my Devices and in the Bluetooth integration.
My googling hasn't been very successful and I'm not sure where to look for more clues as to why this discrepancy exists. Would love suggestions.
Aw heck. Thought this was a general topic thread for esp32 proxies.
Apologies for the attempted hijack.
Yes.
try uploading to the IP with esphome builder
It is present in the builder.
But missing in the Bluetooth integration
7db414 is AWOL.
Same situation in bermuda
What I did was I went to the esphome.io and upload a new config from there once it was online again I pushed the config to the device from ESPhome builder
Yeah. I did that.
Originally provisioned from EspHome web, but once they were on wifi and in the builder, I altered and pushed config from there. Setting static IP and such.