Blynk: Two devices, one auth. How to tell which is disconnecting

[structure7]

So there's three bad things that can happen:

1. Overflow or some kind of error causes ESP reset.
2. Network dropout causes Blynk disconnect.
3. ESP error causes Blynk disconnect.

What I know:

• The app clearly knows a disconnect happened because it report it!
• The above has something to do with a "heartbeat" that Blynk monitors... I believe local server folks can tweak interval settings for this. Is this something I can tap into?
• This might be my gold (for now): http://docs.blynk.cc/#blynk-firmware-connection-management

The idea: Monitor each occurrence of Blynk disconnecting, for whatever the reason. Ideally, report this to a vPin like the uptime monitoring seconds are. THIS SHOULD HELP TROUBLESHOOT PROBLEMS.

Side notes:

• I learned that Blynk.disconnect() is a thing. Might need to see if that's something I'd like to play with for some reason.

[structure7]

What I came up with:

bool blynkFlag;
int blynkDisconnectCount; 

void setup (){
   timer.setInterval(250L, disconnectWatcher);     // Watches for a disconnect event
   timer.setInterval(5000L, disconnectReporter);   // Reports disconnects to the app every 5 seconds
}

void disconnectWatcher() {
  if (Blynk.connected() == false && blynkFlag == false) {
    ++blynkDisconnectCount;
    blynkFlag = true;
  }
  else if (Blynk.connected() == true && blynkFlag == true) {
    blynkFlag = false;
  }
}

void disconnectReporter() {
  Blynk.virtualWrite(V10, blynkDisconnectCount);
}

\\ Optionally... in a run once type deal
Blynk.setProperty(V10, "label", String(hour()) + ":" + minute() + " " + month() + "/" + day());  // Or whatever prints current time/date

[structure7]

I can see there's some value in being able to differentiate between a blynk or WiFi "event." Not sure how I can do that but worth looking into.