Concurrent BLYNK_WRITE's

@CampHamp Perhaps you are running into the anti-flooding protection that was introduced into 0.5.0

It basically helps keep those that don’t use proper timing and logic from flooding and causing disconnections.

I had ran into some governor like loop issues with some of my very fast processing projects (only possible due to internal network and Local Server) and supposedly the bypass command that seemed to help is

#define BLYNK_MSG_LIMIT 0

You can try that, but it will not guaranty that your use of blocking processes will not continue to cause issues as more features are added into the library.