Another thing that I have observed was that the watchdog itself is STOPPED when the RESTART limit is reached and it does not start running again, unless the LK4 reboots or the user press the SAVE button in the web interface(i.e resets the restart counter).
In the current scenario, even if you fix the disconnection issue, the LK4 does not protect the device any more, the watchdog stays off.
This is not optimal.
It should run the ping continuously forever when the watchdog is enabled and only the RESTART should stop at the desired limit(if any).
The ping running continuously would automatically protect the connected device again, when the issue of the disconnection is fixed. On the first successful ping, the restart counter should be reset to zero and continue as normal.
In the current scenario, even if you fix the disconnection issue, the LK4 does not protect the device any more, the watchdog stays off.
This is not optimal.
It should run the ping continuously forever when the watchdog is enabled and only the RESTART should stop at the desired limit(if any).
The ping running continuously would automatically protect the connected device again, when the issue of the disconnection is fixed. On the first successful ping, the restart counter should be reset to zero and continue as normal.