ESP8266 Community Forum

- Sun Apr 22, 2018 10:35 pm #75550 I bought four NodeMCU 1.0 from a local electronics store.

I upload the exact same code to all 4, and they all run the FastLED animations properly, but 2 of them won't connect to my ESP32 AP. The AP is not overloaded, as I try them one at a time. Also, the same code connects just fine on D1 Minis and HUZZAH's I have laying around.

I'm not familiar with debugging ESP8266 connection issues, any pointers I should be aware of? Anything particular to NodeMCU?

Thank you!

Arduino IDE 1.8.3
ESP8266 Boards 2.3.0 (updated to 2.4.1, same problem)

- Mon Apr 23, 2018 2:59 am #75554

Anything particular to NodeMCU?

In theory no: it uses the same ESP-12 as the Huzza.

Assumption is the mother of all f*ckups. At least: that's what I'm assuming.

- Mon Apr 23, 2018 3:11 am #75555 The standard way of debugging any type of issue like this would be to put Serial.print statements at critical pieces of the code and in particular include any returns back from calls.

Sometimes one can also turn on extra debugging statements in libraries by changing some of the #defines in those.

To get more specific advice you need to include the code you are using.

- Mon Apr 23, 2018 3:12 am #75556 if they are from a local store they might as well be "returns".
Once someone used deepsleep with wake_no_rf, this setting persists even power off and sketches not using deepsleep will have no access to wifi (=> return to store) unless flashed with "erase all" option.