I’ve noticed that my wifi has sometimes connection issues and drops down, or I’m updating the firmware and have to reboot the router. If this happens, the RPi3B+ I use for running the ruuvicollector won’t reconnect unless I just power off and on.
Is there some script that could be added to the standard installation to detect if the network is down and force reconnection as needed?
The RPi seems to have lots of difficulties keeping the network connection open. Putty reports network closed error quite often and it’s a bit sluggish typing things on the terminal.
Could it be that the Wifi module is actually dying? Today I had one network disconnect in the RPi and it didn’t reconnect until I powered it off and on. I’m unable to do a sudo apt update to start updating packages, it seems to just timeout even if I’ve tried different servers in the config file.
All the other wireless device seem to work fine. It’s been connected to my 2.4GHz all the time I’ve used it. I actually thought it supported only that and not 5GHz. The router doesn’t show any errors in it’s logs.
pi@ruuvicollector:~ $ sudo apt update
Err:1 http://archive.raspberrypi.org/debian buster InRelease
Connection failed [IP: 93.93.135.117 80]
Err:2 http://mirror.ox.ac.uk/sites/archive.raspbian.org/archive/raspbian buster InRelease
Connection failed [IP: 163.1.221.67 80]
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://mirror.ox.ac.uk/sites/archive.raspbian.org/archive/raspbian/dists/buster/InRelease Connection failed [IP: 163.1.221.67 80]
W: Failed to fetch http://archive.raspberrypi.org/debian/dists/buster/InRelease Connection failed [IP: 93.93.135.117 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.
I was now able to switch to 5GHz with raspi-config, and everything seems to work much better. Maybe the box is a bit flaky or something, if my 2.4GHz network didn’t work properly, I would have noticed it as most of my gear is using that.
Good you get it working. Most likely at 2.4GHz there are lot of other APs and current version WLAN standard 5, will get congested and behave like you described. At WLAN standard 6 this issue has been corrected.