UNO Q WIFI: server slow connecting or not connecting, as well as Applab

Official Hardware UNO Family UNO Q
1

I ran a problem using Python server. Http connects but after a while off no web activities it just stop to accept any http requests. At the same time noticed that the Applab needs a lot of time to connect. Seems to be the same problem.

I set the wlan power save OFF no results.

ping is fine but it wont connect or take too much time to connect.

The best result is to ping regularly the UNO Q to keep it "alive". This works fine.

What is creating this latency?

Thanks for some hint.

2

ICMP staying alive while HTTP and App Lab die after idle usually means power save or an idle TCP path, not a dead radio.

You already turned WLAN power save off. Confirm it on the NetworkManager profile, not only with iw:

nmcli -f NAME,DEVICE,TYPE connection show
nmcli connection show "<your-wifi-connection-name>" | grep -i powersave
sudo nmcli connection modify "<your-wifi-connection-name>" 802-11-wireless.powersave 2
sudo nmcli connection up "<your-wifi-connection-name>"

2 is disable in NetworkManager.

Then check the active state:

nmcli -f 802-11-wireless.powersave connection show "<your-wifi-connection-name>"
iw dev wlan0 get power_save

If App Lab and your Python server still stall after idle with powersave disabled:

  1. Bind the server to 0.0.0.0, not only 127.0.0.1, if clients are remote.
  2. Log accept errors when it “dies” (exception vs hang).
  3. Test the same HTTP client over USB Network Mode / Ethernet if you have it. If only Wi-Fi idle fails, stay on the radio/PS path.
  4. Keepalive ping working is a clue, not a root fix. Prefer NM powersave disable + watching whether new TCP handshakes fail after idle.

Say which OS image / App Lab version you run, and paste nmcli device plus the powersave lines above.

3

nmcli -f 802-11-wireless.powersave connection show "mywifi"
802-11-wireless.powersave: 2 (disable)

App Lab Version

0.10.0

I made these above suggerated changes as well as the python server biding to 0.0.0.0

Removed the stay alive pinging.

Will test it and let you know.

Thank you very much.

4

@theengineerstore tested OK for 24 hours. All works well and do not need any ping stay alive.

Thank you