Skip to content
Discussion options

You must be logged in to vote

Unfortunately I have no experience of Blynk but I assume it is useless without a WiFi connection. Looking at your code I think there is a hazard whereby you might create more than one concurrent instance of the same task; this will probably cause chaos.

The way I would design something like this is to have a maintainer task which runs continuously whose job it is to create and maintain a WiFi connection (connections can drop out). When a connection is established, it starts Blynk and once Blynk is running, tasks that use it are started. If the WiFi connection is lost, maintainer cancels the Blynk-dependent tasks then cancels the Blynk task.

However this (and any solution) comes with a hug…

Replies: 4 comments 1 reply

Comment options

You must be logged in to vote
1 reply
@andypnz
Comment options

Answer selected by andypnz
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants