I had created a device to monitor & record refrigerator temperatures using an Adafruit Feather Huzzah with an attached Adalogger daughter board. Provisioning was successful - I was able to reset the board, attach to it with my smartphone, enter the correct provisioning details, and connect to the internet & Blynk cloud.
I had the board running on an attached LiPo battery (in order to test the runtime). After the battery ran down I connected to USB power as usual, but I was unable to get the provisioning to work again. It simply failed to give me the AP that I was looking for. I ran some sample sketches to verify that the WiFi hardware was working and all passed just fine.
Is there any particular reason that the Edgent provisioning should stop working?
Edgent provisioning data is stored in NVRAM, so is not lost when the power is disconnected.
To allow an Edgent device to be re-provisioned you would need to clear the existing credentials.
This can be done by pressing the hardware button that was assigned in Settings.h for 10 seconds, or if the device is already connected then via the app or dashboard.
Pete.
Thanks, Pete. The issue I seem to have is that the board gets hung up trying to connect to the existing SSID, even though the PW and everything haven’t changed.
I re-wrote the sketch to eliminate Edgent, simply hard-coding the WiFi credentials, and it works perfectly, so something was wonky about the Edgent configuration.
In any case, I doubt that the end user will be changing their WiFi setup anytime soon, so I think I can run with this solution. I’m sorry to give up the OTA capability, but perhaps I can find another way to do that without using Edgent.
As always, I thank you very much for your insight and attention!
You don’t need Edgent to use Blynk.Air OTA…
Pete.
Thank you! I’ve added that to my code - now we’ll see…
That appears to work just fine on my Adafruit Feather Huzzah ESP8266.
Thanks again for your help!