Hi,
I have been trying to understand the mechanism for connecting/disconnecting/reset for a board running nodeMCU API to establish why it sometimes hangs.
Using a nodeMCU board (#5), print statements in the sketch and looking at the debug file, most things now make sense.
However, there is one area that doesn't.
If I drop the Wifi connection the debug log shows, after a "5 K" (Board #5, keep alive command" has been issued, the following expected response:-
"Connection failed running reset". So far, so good.
However, even after 10mins the nodeMCU status in HS3 for Board 5 still shows "Connected". This can't be right.
It is only by rebooting HS3 that the correct status is displayed.
I would be interested to know what is wrong.
Cheers
Stewart
I have been trying to understand the mechanism for connecting/disconnecting/reset for a board running nodeMCU API to establish why it sometimes hangs.
Using a nodeMCU board (#5), print statements in the sketch and looking at the debug file, most things now make sense.
However, there is one area that doesn't.
If I drop the Wifi connection the debug log shows, after a "5 K" (Board #5, keep alive command" has been issued, the following expected response:-
"Connection failed running reset". So far, so good.
However, even after 10mins the nodeMCU status in HS3 for Board 5 still shows "Connected". This can't be right.
It is only by rebooting HS3 that the correct status is displayed.
I would be interested to know what is wrong.
Cheers
Stewart
Comment