Tinypilot access-point mode vs non-access-point mode

[jfhext]

yes,

you can configure the network from
192.168.14.1/wifi

It wont automatically fallback to ap mode, however you can switch it back to ap mode using the ir remote.   This is because it will automatically reconnect to boat2 when it comes back up.   Is there some other behavior that would be more useful?

Thanks. I'll give that a try. In my little "NMEA sentence forwarding widget" (running on a NodeMCU), the default is "try to connect to the last known network, but if that fails, then after 10 seconds, come up in access-point mode." This works well, because the tool I'm using to look at the data stream is often my phone, and I just just connect to "NMEABridge" and socat all the data coming out, and I can even do this when the local router isn't turned on (useful for debugging when off the boat, for instance). 

Would that be good behavior for the tiny pilot? I'm not sure, but I think so. Having it hung up trying to connect to a network that's not there doesn't seem like it serves any useful purpose, but presenting the access point when that process gets wedged...at least that lets you do SOMEthing without having to look at the tiny blue screen.