MKR1010 wifi drops out, wont reconnect - tried forced reconnect- no client

Official Hardware MKR Family MKR WiFi 1010
1

Hello,
I fought issues with the MKR1000 loosing wifi connectivity for several months a few years back. Eventually a new firmware version fixed its wifi issue.

 I then read about how much better the MKR1010 was supposed to be and thus changed to using it.

I have now been unable to keep the MKR1010 connected. It drops out at varying times from a few days to as much as 20 or so days. ( using 1.4.8 firmware)
I read every post online I could about this issue and tried all the solutions found thus far. None I have found thus far have worked.

Later I read where because the MKR1010 was so bad at drop outs that it is best to test the connection at the application level and force a reconnect when the client is no longer being established.
I implemented this concept. When it has not established a client connection for more that 2 hours my code performs a:
client.stop();
WiFi.disconnect();
WiFi.end();

I detect wifi.status goes to zero and I then issue a wifi.begin() once again.
It appears to connect and wifi.status goes to 3. I then issue a
server.begin().

At the router I can see the MKR1010 is connected and shows online... however I still cannot establish a client connection?

Has anyone fought this issue and had better luck? If so can you please help me with what I am missing? I admit that I am no ethernet wiz.

2

try an experiment. next time the MKR doesn't respond. try restart the router, not the MKR

3

Hello Juraj,
Thank you for your suggestion. I will do that next time a drop out occurs.
A while back I did tests by running the MKR1010 on battery power so that I could move it out of router RF range to force a reconnect. If I recall correctly I was able to get it to reconnect doing that. I know that is different from your suggestion, but just another bit of information.

4

what I experience with many devices even with not dyi is that they still run and communicate as clients with other devices and cloud and just the listening ports of the device are not reachable. as if the router in the AP forgot about them.

the esp8266 community sort of solved it for esp8266with ESP8266WiFiGratuitous

5

Thanks Juraj,
I read about the gratuitous.h you pointed out and the concept of the router forgetting about the client. I did not understand exactly what gratuitous.h is doing to keep the connection alive. Can that same concept be implemented in the MKR Wifinina code?
I recently added a client that is sending a "watchdog" request to the MKR server once every hour. I wonder if reducing that time to less than the lease time ( 1hr) on the router would keep the connection alive?

6

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.