search

blynkkk / blynk-library

Blynk library for IoT boards. Works with Arduino, ESP32, ESP8266, Raspberry Pi, Particle, ARM Mbed, etc.
https://blynk.io
MIT License
3.81k stars 1.38k forks source link

Blynk Edgent Provisioning Issue #575

Closed hms-11 closed 1 year ago

hms-11 commented 1 year ago

Blynk library version: [1.1.0] IDE: [Arduino] IDE version: [2.0.3] Board type: [ESP32] Additional modules: [...]

Scenario, steps to reproduce

[When provisioning a new board with an Edgent based sketch, board will not provision correctly and will give a 701 error code in the serial monitor before going back into AP mode and awaiting configuration. If I attempt to provision on an older phone (Google Pixel 5) the process works correctly, if I use my new phone (Google Pixel 7) the process fails as described. Both phones are running the same version of android and the same version of the Blynk App. See this thread in the Blynk Community for more details: https://community.blynk.cc/t/blynkedgent-based-sketch-cannot-connect-to-wifi/63923 .]

Expected Result

[After supplying correct wifi info, board will reboot, not connect and eventually re-boot again and go back into provisioning mode.]

Actual Result

[Board fails provisioning and returns to AP mode awaiting credentials if using a new Pixel 7, if using my previous phone the process works fine.]

John93-Blynk commented 1 year ago

I would suggest that you go to the Blynk forum and create a new thread there. https://community.blynk.cc/

hms-11 commented 1 year ago

Hey @John93-Blynk, I started over there at the Blynk forum and after Pete and I had exhausted all easily solvable issues we decided I should post an issue. However, that being said, The BlynkAndroidDev user, whom I presume is a developer for Bynks Android app said he was aware of the issue and is planning on releasing a fix today. I'll verify the fix sometime this week and update the issue if it is solved.

Thanks!

doom369 commented 1 year ago

@hms-11 yes, BlynkAndroidDev is Blynk dev, and the possible fix for your issue is on the way. I'll close this ticket as it is not library related. We'll track it through the forum if the fix won't help you. That's for the issue details.