Let's Control It

chromo23 wrote: ↑08 Mar 2023, 20:45

TD-er wrote: ↑08 Mar 2023, 20:17 I've even seen the connected log + IP being reported at 1500 msec from boot, so there is still some room for improvement.
However, there is always the risk we may put too much stress on the node, causing poor quality ones to fail.

Don't push the limits too far.. it all looks already really good.

I can also add some setting to delay starting the WiFi, especially for those units.

Anyway, those changes have now been merged.

I've just downloaded release ESP_Easy_mega_20230409_normal_ESP8266_4M1M.bin
and flashed it on a Wemos D1 Mini.

It seems a lot faster at booting-up and/or reconnecting the WiFi in about 5 to 6 secs.
Previous releases, for me on the Wemos, were very slow.

Thanks guys for another great release.

PS: Happy Easter

Good to know users find improvements instead of serious bugs on a new build
Thanks.

tested the new release and Yes, connecting wifi is much faster. Thanks to the (in dutch) "de PAASBULT"

Maybe the first connection is fast, but these assemblies take a very long time to connect if the network disappears for a long time. Last year's version connects in 5-15 seconds, the new build does it in 30-60 seconds. I use it in the car, and therefore I have to stay on the old assembly. Otherwise, when I return home, the connection is unacceptably long.

What exact version are you using?
Also on what platform? (ESP32/ESP8266)

Only ESP_Easy_mega_20220809_normal_ESP32_4M316k is fast reconnect. All the latest releases are checked and all reconnect for a long time. Each new release I look forward to and check, and then come back with tears.

Hmm that's strange as I did a lot of testing on especially the ESP32 regarding WiFi connection times.

Do you have another ESP32 available which you can completely wipe and flash the latest build on it?
Just to be sure there isn't some RF calibration somewhere on the flash that may cause issues when using a more recent SDK/IDF version.

Of course, I will try to test it on another esp32. However, I think the problem is due to some optimization of the rescan time in new firmware.

What kind of access point do you have?
Does it have WiFi mesh enabled?
Or band steering?

If so, there are 2 new options on the tools->Advanced page to help connecting to these kind of APs.
Especially the "Enable SDK WiFi Auto Reconnect" option is for those APs with "Band Steering" enabled.
"Extra Wait WiFi Connect" is for some FritzBox routers.

"WiFi mesh" or "band steering" not used. One OpenWrt hotspot
Model TP-Link TL-WR1043N v5.

I finally took new esp32 with me to ride both together in the car, with the new and old firmware simultaneously. And still disappointing, it connects in about 1-1.5 minutes. While esp in the car can hook the network in 10 seconds if on the old firmware. This is a network with powerful antennas and a signal from -63 to -68 dBm. However, I am timed before connecting to mqtt, not wifi directly. That is, in the "on MQTT#Connected do" rules. I hope this can be fixed in new firmware.