Timeline for Blynk, but continue program if Blynk connection fails
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 5, 2021 at 20:52 | vote | accept | Petrus | ||
| Apr 28, 2021 at 6:56 | comment | added | Juraj♦ | docs.blynk.cc/#blynk-firmware-configuration-blynkconfig and the ESP8266_Standalone_Manual_IP example for Blynk library | |
| Apr 28, 2021 at 3:34 | answer | added | khoih-prog | timeline score: 0 | |
| Apr 27, 2021 at 23:54 | comment | added | jsotola | this may help gist.github.com/mercdev/… | |
| Apr 27, 2021 at 20:41 | comment | added | Petrus | @JRobert, thank you for your comment! At first I thought perhaps just moving the Blynk code completely out of the void setup() into the main loop, at the very end, but even then I'll get stuck if wifi fails for some reason. I'm sure I'm missing something - not being very well experienced with anything more than the basic Blynk. Hard to imagine this is not a major issue when it comes to programs that need to execute important tasks regardless whether wifi is working or not... | |
| Apr 27, 2021 at 20:25 | comment | added | JRobert | This has been a weakness with Blynk right along. The connect functions block and nothing else can execute until they return. In addition, some of the transmit-data functions block if your internet connection goes down or is carrying too much traffic for Blynk's traffic to complete in a timely way (how long is 'timely'?). I don't know a way around it other than possibly to make your own watchdog timer (one that can have a much longer timeout than 8 sec), and code your system to run without Blynk if it was restarted because of Blynk. | |
| Apr 27, 2021 at 20:17 | review | First posts | |||
| Apr 27, 2021 at 21:22 | |||||
| Apr 27, 2021 at 20:09 | history | asked | Petrus | CC BY-SA 4.0 |