Re:ESP32 WiFi Superstitions
by RockRobotRock on Saturday March 15, 2025 @11:25PM
(#43376757)
Who wants to deal with writing that logic for a hobby project? That doesn't sound fun at all.
Sounds like a "good enough" shitty solution to me, which is kind of the whole point of DIY.
Re:ESP32 WiFi Superstitions
by Vurdentium on Sunday March 16, 2025 @12:20AM
(#43376915)
Deal with what? I would argue that if you're going to the effort of writing a blog post on the topic then you should at least go to the effort of skimming the docs to make sure there isn't already a solution for the common problem you're experiencing.
It's literally one word to change in his WiFi config to get the behaviour he wants. It's already implemented. Who can't "deal" with that?
Re:ESP32 WiFi Superstitions
by RockRobotRock on Sunday March 16, 2025 @12:38AM
(#43376967)
Personally, I don't use multiple APs with overlapping SSIDs, but if I did than I can see how it would be easier to deal with the logic from the AP management side rather than the client. It's also nice to not have to re-connect IoT things if/when you add or change your APs.
Re:ESP32 WiFi Superstitions
by Vurdentium on Sunday March 16, 2025 @01:00AM
(#43377019)
I'm not sure we're understanding each other so just to be clear, my suggestion is to change from this (pseudo) C:
wifi_connection_config_t config = {
.ssid = "my_home_wifi",
.password = "secret123",
/*
implicitly initialised to default:
.method = CONNECT_TO_THE_FIRST_AP_THAT_RESPONDS,
*/
}
to wifi_connection_config_t config = {
.ssid = "my_home_wifi",
.password = "secret123",
/* explicitly initialise: */
.method = CONNECT_TO_THE_AP_WITH_THE_STRONGEST_RSSI,
}
It's that simple.
Re:ESP32 WiFi Superstitions
by RockRobotRock on Sunday March 16, 2025 @07:29AM
(#43378204)
I think I understand you. That functionality doesn't exist in ESP32 Arduino tool chain without more work/more code. Their hobby level perspective is valuable to other hobby level engineers who want a solution.
I know what you mean haha.
Instead of spending x2 the initial effort to fix the root cause, you spend x1 the initial effort to implement jank and then spend x10 the effort down the line maintaining the jank.
If you're going to write a blog about how the ESP32 doesn't connect to the strongest AP so you need to pin it to a specific BSSID in your router settings... Maybe you shouldn't be writing that blog. If you haven't taken at least a moment to check documentation and see that the behaviour you want is already an option that can be selected by changing literally one line in your ESP32's WiFi config. Instead this pseudoscience proliferates.