On Mon, 7 Dec 2020, Michael Balzer wrote:
If you don't mind frequent disconnects in poor Wifi situations, a simple solution now is to attach a "wifi reconnect" command call to the "network.wifi.sta.bad" event. I added that command on the Wifi rework some months ago.
I tested this today with the three APs in my home but ran into trouble. It looks like the event was emitted again at the end of the reconnection process so another reconnect was performed and it kept looping. See the attached log. I have not investigated this carefully.
For a better, general solution, we could e.g. count the "network.wifi.sta.bad" events on the same network (or better: check the event frequency) and disconnect when reaching some (tunable) threshold. The next automatic scan then connects to the best network available. Getting stuck in the "bad signal" state for too long would also need to trigger a disconnect.
I'll look at this further to see whether a smooth transition from one AP to another on the same network is possible. -- Steve