ESP32 unable to reconnect to wifi after reboot with Huawei, Fastgate DN8245f2

Boards
21

I confirm that the issue is fixed in this dev build.

22

Sorry for pulling up sich an old thread, but I experience the same behaviour with an Asus ax58u.
Is this still an issue or are the Test builds already included in 1.7.?

23

Hi @haiq

You should use the latest development version of OpenMQTTGateway, avaialble at

Hopefully this will also work fine with your Asus ax58u.

24

Hi @DigiH and thanks for jumpin in,
Unless I missed something, it does not work. I chose esp32dev-ble a few moments ago and for the previous setups as well. Still no success.
I tried it with two esp32 boards with USB-C and connected them to a AP running openWRT because of some known issues of esp8266 boards with Asus Routers. I tried several power supplies but always the same behaviour: flashing with web-flasher works, without disconnecting from USB, I can set up everything with the webUI. When I disconnect from USB, the board(s) are not able to connect to the wifi again. Even when reconnected to the USB.

I had a look at the serial output but couldnā€™t identify something suspicous. Anything I can do to further investigate that?

25

I assume this is the correct binary for your ESP32, as with you mentioning them having USB-C ports, might they be newer ESP32 boards which would require their own specific builds, e.g. ESP32 C3, feather, lolin ā€¦?

If not, and the esp32dev-ble binary is the correct fit, the issue all started for me and my router when a newer esp32_platform was introduced to the project, so the test builds mentioned above were using the previous older platform. I also logged an issue against it, with others still adding me too to it every now and then

but going back to the older platform is not possible with the current release or development build, as code changes and additions require a newer platform.

Iā€™m also not sure if it is the same DHCP issue that you are seeing, looking at your routerā€™s system log might help in seeing if there are some DHCP issues showing up there, as you state that you do not see any WiFi connection issues when monitoring the serial output, but the thing that still has it working for me with my same old router is to use static network definitions, circumventing the routerā€™s DHCP assignment. This requires defining your own environment for a custom build for your gateways, as described in the note of the docs at

Manual network configuration (IP, netmask, gateway, DNS) requires to define ā€¦

Let us know how you get on.

26

Thanks for the reply.

I set up a esp32dev-ble env with wifi and MQTT settings as build flags. Everything works after flashing but after changing to the power supply the esp32 did not connect to the wifi again. I left it like that for half a day. In the Home Assistant logs I can see, that the esp could connect after 100minutes for 24secs, went back offline and comes back againg after another 7 minutes. Than it stays connected for almost 5 hours. But now its offline again.

Logs of the AP at the time says:

Tue Oct 22 18:25:10 2024 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED ca:29:f7:10:0a:05
Tue Oct 22 18:25:10 2024 daemon.info hostapd: wlan1: STA ca:29:f7:10:0a:05 IEEE 802.11: disassociated due to inactivity
Tue Oct 22 18:25:11 2024 daemon.info hostapd: wlan1: STA ca:29:f7:10:0a:05 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Tue Oct 22 18:27:29 2024 daemon.info hostapd: wlan1: STA ca:29:f7:10:0a:05 IEEE 802.11: authenticated
Tue Oct 22 18:27:29 2024 daemon.info hostapd: wlan1: STA ca:29:f7:10:0a:05 IEEE 802.11: associated (aid 4)
Tue Oct 22 18:27:29 2024 daemon.notice hostapd: wlan1: AP-STA-CONNECTED ca:29:f7:10:0a:05
Tue Oct 22 18:27:29 2024 daemon.info hostapd: wlan1: STA ca:29:f7:10:0a:05 WPA: pairwise key handshake completed (RSN)
Tue Oct 22 18:27:29 2024 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED ca:29:f7:10:0a:05

which seems like normal disconnecting for inactivity procedure, I guess.

Next step in a few days will be to go through the other board-builds @DigiH mentioned. Until then, I will left the esp32 as-is and see if there are further successfull connection attempts.
If there is anything else I can try, let me know :slight_smile:

27

It really depends on which ESP32 you have, randomly trying the other builds with a wrong board is not likely to result in any better behaviour :wink:

Did you just define the manual WiFi and MQTT details, or also, the more important for this issue, network details with '-DNetworkAdvancedSetup=true' etc.?

28

Youā€™re totally right. I did not mention that I had no glue what kind of board it is. I just learned its Nodemcu-32. For OMG there are only esp8266 NodeMCU builds, right?

I set these settings manually (not with example data of course):

'-DESPWifiManualSetup=true'
'-Dwifi_ssid="mynetwork"'
'-Dwifi_password="Cato\\\'sYounger\\\$on"'
'-DMQTT_USER="mqttusername"'
'-DMQTT_PASS="mqttpassword"'
'-DMQTT_SERVER="mqttserver.local"'
'-Dgw_password="12345678"'
'-DNetworkAdvancedSetup=true' 
'-DNET_IP="192.168.1.99"'
'-DNET_MASK="255.255.255.0"'
'-DNET_GW="192.168.1.1"'
'-DNET_DNS="1.1.1.1"'
29

Sounds like a standard ESP32 dev kit, so the esp32dev-ble binary should have been right.

And these also all look fine to me, so unfortunately Iā€™m at a loss now as to what might be causing the connection issue for you, as the above

'-DNetworkAdvancedSetup=true' 
'-DNET_IP="192.168.1.99"'
'-DNET_MASK="255.255.255.0"'
'-DNET_GW="192.168.1.1"'
'-DNET_DNS="1.1.1.1"'

did the trick for my router for fixing the reconnection issue.

30

Had same problems.I found out that my router was setup for 2.4GHz/5Ghz Wifi. ESP32 supports 2.4GHz and by configuring Wifi as 2.4GHz only solved my problem. I also use WPA2 security