Replies: 4 comments
-
I forgot to add, in case that helps, the code that I used to test the above scenarios can all be found here: https://github.com/dj-louw/wifi-playground/blob/master/src/main.cpp |
Beta Was this translation helpful? Give feedback.
-
Before your wifi begin() in setup try the following. WiFi.disconnect(true); delay(2000); |
Beta Was this translation helpful? Give feedback.
-
@dj-louw There have been some WiFi reconnect improvements in this project. Have you tried the latest release? Also sounds like possible bad antenna on module 2. Try the WiFi Scan example on both boards and see what kind of signal strength you are getting. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the suggestions, I will try them when I have a chance and report back. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I'm relatively new to microcontroller development and I'm fumbling my way through a couple of projects.
I have run into a very weird issue, and I would appreciate somebody shedding some light on it for me.
Background
High level overview of the problem:
I have 2 nodemcu-32s development boards in front of me. One appears to have no issue connecting to my wifi network at all, but the other one refuses to connect, or takes a very long time to do so, and sometimes connects instantly.
What's even more wacky is that this behaviour depends on the access point I am using. I summarize the behaviour below:
Dev Board 1
Dev Board 2
ARDUINO_EVENT_WIFI_STA_DISCONNECTED
, reason 2, which isWIFI_REASON_AUTH_EXPIRE
I think. I've sometimes also seen event reason 202 (WIFI_REASON_AUTH_FAIL
) be given.ARDUINO_EVENT_WIFI_STA_DISCONNECTED
with reason 201, which as I understand it isWIFI_REASON_NO_AP_FOUND
Based on my massive sample size of 3, it's clear to me the board is not faulty, because it's actually connecting to a network successfully. But why won't it connect to my unifi gear, and more importantly, why is the other board not experiencing this issue?
It's worth pointing out that I had Board 2 running "in production" in my house for almost a year without issue, when all of a sudden it stopped connecting to my network. At first I thought the board died, but then when I investigated further I noticed this strange behaviour.
Could a firmware update in my access points perhaps cause this? Is there some "firmware" or something that I can update on my ESP board itself that might help?
Or is this a hardware problem, and if yes, is it possible to diagnose it further?
Your help in this grave matter will be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions