Wi-Fi: Shell Firmware example with nrf7002

[BarnesToby]

Hi There

I have implemented the nrf firmware example "Wi-Fi Shell" on the nrf7002 development kit.
But I noticed a strange behaviour, after a while I cannot ping any server and it disconnects and reconnects from the access point.

It always gives the error reason=4 for the disconnection:
CTRL-EVENT-DISCONNECTED bssid=a4:6c:f1:fd:82:82 reason=4

Now as I understand it, reason 4 means "disconnected due to inactivity".

Is this conclusion correct is there any documentation about the error and how can I fix this problem so that it does not happen again?

Thanks for your Answer

[runsiv]

Hi 

Just a few questions to get started

1. Which version of the SDK are you running?

2. Do the same issue happen if you connect to another network then a access point

3. is the issue the same for all addresses you try to ping?

Regards

Runar

[BarnesToby]

1) I am using nRF Connect SDK v2.4.1 version.
2) I have the same problem with different types of access points (mobile hotspot, router, etc).
3) It does not matter which address I want to ping, it always happens after about a minute of doing nothing on the console.

Regards
Toby

[runsiv]

Thanks for the quick reply. 

I would highly recommend to update to NCS 2.5.x (2.5.2 is the newest ) if possible to do the improvements for the 7002 done on the driver side. 

I will see if I can replicate the behavior on my side as I have not seen this error  with that sample before. 

Regards

Runar

[BarnesToby]

Thank you for your reply. .
I have updated to nRF Connect SDK v2.5.2, which has successfully resolved the issue.  
It would still be interesting what the error meant. Do you have any insight into the meaning of the error?

Regards

Toby

[BarnesToby]

I would like to revise my statement, it just happened again with the new updated sdk, although much later.