Does FanPico reconnect to wifi after disconnections?

[lowjoel]

Does a disconnection (e.g. restarted router) which disconnects from wifi trigger a reassociation at a later time, or must I always manually restart the FanPico? I seem to be losing FanPico randomly from the network and I wonder if that's a possible cause (or maybe I need to leave it plugged into my computer for the debug output for longer)

[tjko]

@lowjoel, seems like a bug, shouldn't need to restart FanPico. At least for me, FanPico seems to transparently switch to another AP when one reboots.
Are you using latest firmware? (it uses updated Pico-SDK that has WiFi improvements/fixes)

Debug output would help, it might give some clue what is happening.

[lowjoel]

At that point, SYS:WIFI:REJOIN succeeds almost immediately (within 10s)

[tjko]

Which version of firmware was the above logs from?

There is beta firmware here (https://github.com/tjko/fanpico/actions/runs/16386142573) that adds more logging and logs the network events at higher priority so can leave logging at NOTICE level (SYS:LOG NOTICE), that should leave out "noise" from fan speeds changing, but still capture any network related events.

Are you able to log the messages from Fanpico to a file? Since if it take long time for issue to happen it might help to be able to look the logs later... On Linux (and Mac) tio is nice tool to log output from FanPico

On Linux I've been logging messages from a fanpico using:

tio -t --timestamp-format is8601 -l /dev/ttyACM0

(this opens log file in current directory and records all output from fanpico in additon showing it on the terminal window as well)

[tjko]

This is what I saw when WiFi network was "down" when FanPico booted and after network came up it connected within 10 seconds:

[     2.050683][0] WiFi Status: Joining 
[     3.105986][0] WiFi Status: Network Fail 
[    13.113624][0] wifi_rejoin()
[    13.116881][0] Attempt rejoining to WiFi network: testap
[    23.117646][0] wifi_rejoin()
[    23.120973][0] Attempt rejoining to WiFi network: testap
[    34.120924][0] wifi_rejoin()
[    34.124167][0] Attempt rejoining to WiFi network: testap
[    44.124954][0] wifi_rejoin()
[    44.128210][0] Attempt rejoining to WiFi network: testap
[    45.129488][0] WiFi Status: Joining 
[    46.904977][0] WiFi Status: No IP 
[    46.908744][0] Network Link: UP
[    48.701377][0] WiFi Status: Link Up 

[lowjoel]

The logs I got was from 1.7.5. I'll flash your beta build.

Unfortunately there isn't a computer nearby to get the logs into a file. I'll try to think of how to set one up if possible, but no guarantees (need to figure out a device placed into rack and power it permanently).

Alternatively, could you get a debug build that can print the last few transitions every 5 mins, so that when it does refuse to join, it'll just print the last few messages? Or maybe I should try to figure out how to wire up the logs to a small memory buffer that allows us to dump the last few messages after plugging in my laptop.

[tjko]

@lowjoel , I think I found the issue. I had tested other failure scenarios like "Link Fail" and "Auth Fail", but not the one you see "Link Down". Automatic rejoin was not happening if link was first working and then went to "Link Down" state. This should now be fixed, there is update firmware with the fix here: https://github.com/tjko/fanpico/actions/runs/16397101403

Btw, if you still see issues there is new command SYS:WIFI:INFO? that gives more information about the network status.