In this github ticket the op has the same issue you list (error is slightly different) but they ended up having to change thier config to specify the correct board type. In thier case a D1 mini. So when they edited the configuration for the correct board. It fired up.
Shot in the dark but it’s the only one I can find that’s remotely close.
I try with another smartphone and I have the same issue than with my internet box.
With internet box I try all the combination of settings but nothing works
But with my Galaxy samsung, the first try is the good one. I don’t understand what is the rootcause, that’s very strange !
I fix my problem, I reset my internet box with the factory configuration.
I configure it with ethernet cable,split two wifi network. One for 2.4GHz and another for 5GHz.
The two one are visible from any device now. I don’t know why but my 2.4GHz wifi was ghost, visible but not operationnal. I make a diagnostic and all were good, so I don’t understand but I am not a fan of HMI configuration boxes, that make what it wants to do.
Good to hear that splitting your wi-fi to separate 2.4GHz and 5GHz networks fixed your problem
How many devices are connecting on 5GHz and how many on 2.4GHz ?
Wi-fi Access Points usually support only a fairly low number of devices - with popular home grade WAPs that number could be only 15 wireless devices. By moving your smartphones and other devices to 5GHz you have freed up some slots for devices using the older slower 2.4GHz bandwidth … but you will hit the limit again one day.
I am glad that you’ve fixed your issue… but unfortunately I don’t see what’s different between you solution and everything I have tested.
I am with a Ubiquiti Dream Router, a SSID for 2.4Ghz only and on only one AP (on channel 6) on an IOT vlan.
These are the settings that are on… (should be close to default): Proxy ARP, BSS Transition, UAPSD, Multicast Enhancement.
I even created a brand new 2.4 ssid only for esp32 but nothing changed.
One interesting thing: with the latest versions of ESPHome, it’s looping on the same errors… but with 2023.6.3 , after a while it connects … and stays on it
Had the same symptoms. (AVM Fritzbox, WROOM DevKit)
It seems to be the signal power. changing the “output_power:” parameter did not cut it.
I have plugged in the ESP directly into a Router USB port and have put it right onto the plastic router case.
immediate success.
FWIW I’ve just spent the past couple of hours trying to troubleshoot several lost ESPHome devices on my HA installation. I tried everything I could think of, including making up a brand new ESP32 box and RS485 interface chip to try and get things going on my battery inverter interface, to no avail.
I eventually worked out that the ESPHome devices were connecting to the router (by doing a port scan) but several (all ESP32-C3 devices) that were apparently connecting to Home Assistant (as in they were shown as online in ESPHome) weren’t actually connected (I could not get logs from them).
After a lot of head scratching I tried the suggestion from @MaximeBe and had a look at the main router settings. Lo and behold it had stepped up to channel 13 for some reason. I set it manually to run on channel 1 and everything came back online and connected.
It does seem that there are issues with the higher frequency channels and at least some ESP devices. In my case the ESP8266 devices were working OK on channel 13, it was only the ESP32-C3 devices that weren’t.
For those with similar odd disconnection issues I suggest doing a command line ping to the device IP. This seems to be a foolproof way of seeing if it’s really connected and far more reliable than using the ESPHome “online” status flag within HA. When I was having connectivity issues a ping check always timed out, as soon as I changed the router channel I got very quick pings from each ESP device.
Not sure why all the scanning tools I used falsely showed these ESP devices to be connected when in reality they weren’t. Only clue was that Angry IP Scanner was showing very long ping times (around 2500ms) when the devices weren’t working. When they are working the ping times are typically around 5ms to 30ms.
For anyone else who has this problem I had a similar issue. My SSID has a “-” in it but I put a “—”
Possibly a problem unique to my own situation due to some copying and pasting but I thought I’d share in case it helps someone’s troubleshooting
This ^^^^ after weeks and weeks of searching and trying to figure out why some is my ESP devices would not connect via the Captive Portal This was the Reason The Freaking Underscore in my Wifi Name. Thank You, Thank You, Thank You
Apparently dahs and underscores are a problem.
Odd thing is if i flash it as something else, using ESPhome.io i can tell it the SSID and it works Fine.
