So I get my code right, I assume the strategy for handling the logic in our program is to have a number of small functions, as short as possible, to handle different events in the program so that there are as many opportunities for Blynk functions to run in between our events as possible. If, instead, these logic functions are in loop(), Blynk is locked out and errors like timeouts etc. can occur.
If there are any other hints for ensuring constant Blink connectivity, please let me know. Thanks.
There are some nice pointers regarding checking for connection and reconnecting etc. Most of it is automatic with Blynk.run() but some features can be tweaked.
Do you have Serial Monitor running with your device and if so what sort of issues does it highlight?
Thanks, @Costas. The error messages sent me off in the wrong direction. I took a step back and looked at the code flow again and I solved it this evening. Just about to write a post with my observations.
при попытке скомпилировать и прошить вылазиет вот такой лог:
C:\xxx\libraries\Blynk\examples\BoardsAndShields\ESP8266_Standalone\ESP8266_Standalone.ino:6:21: fatal error: TimeLib.h: No such file or directory
#include <TimeLib.h>
^
compilation terminated.
exit status 1
Ошибка компиляции для платы NodeMCU 0.9 (ESP-12 Module).
Помогите пожалуйста разобраться