Sure I will. do it… The device and libraries are updated regulary, there is some fuctions or utlities in the Sketesh are old like this part of Reboot in case of loss communication …but the rest is very recent…
Regards
You’ve been running this code for 3+ years
You’ve been updating it regularly
You’ve used the Node-Red Blynk contrib for the first time today
You’ve trusted it many times
Can’t you see how these statements conflict and contradict eachother?
I’ve spent a lot of time managing software version control, doing unit testing, tracing bugs, doing release management and doing software quality control in a mission-critical business system. Trust me, none of what you’ve said convinces me that your codebase isn’t playing a factor in this issue.
However, the best way to prove that it’s a “Blynk bug” is to do what I suggested earlier and submit a reproducible bug report.
Until then, this is the last I’ll say on the matter.
Pete.
Hi Pete, this morning everything worked again without doing anything …all the 3 devices are working as before … still don’t understand why the devices was connected to Blynk but the Blynk-write was not triggered…
The 3 devices are working and there were no reboot happened because they were always connected…
I will try to riproduce the BUG and post here to understand if it was a BUG or something else…
Regards
Bek