Hello everyone,
A few years ago I setup a small DIY device with an ESP32 and rainmaker to toggle a light switch. Fast forward a week ago when I changed my wifi credentials and went about to fix the setup; I reset the network configuration and repeated the provisioning procedure. Unfortunately that failed every time I tried at the "Confirming Node association" step. On the device monitor I saw that it couldn't connect to the MQTT server (unfortunately I lost the log output while working on it) due to some authentication error.
I fiddled a bit and then fell back to running the `gpio` example of the repository's `master` branch. That worked immediately, so I went back to my program (which referred to `esp-rainmaker` as it was about 4 years ago) and to my surprise that worked too, even after an `erase_flash`.
Is it possible a parameter on the old configuration was outdated and I fixed it by flashing the example? What could it be that it survived a flash erase?
Old ESP32 module somehow expired?
-
ahsrabrifat
- Posts: 201
- Joined: Sat Jan 18, 2025 2:31 pm
Re: Old ESP32 module somehow expired?
A flash erase does not erase the NVS (non-volatile storage) partition, which may contain old or corrupted provisioning or MQTT credentials. Flashing the newer example likely formatted or reset the NVS partition.
Re: Old ESP32 module somehow expired?
hi, i also encountered this problem, failed to "Confirming Node association" step. how you fixed it?
Re: Old ESP32 module somehow expired?
Was this issue seen sometime during the downtime on 21st April or much later? Does the node not connect to MQTT at all even after retries? Can you share the node ids?
Who is online
Users browsing this forum: No registered users and 2 guests
