Winford

I don't think we necessarily need to add this to the release matrix, we should just support the option and refer this to the build instructions as a special circumstance.

I did not add an example yet, my plan was to write a demonstration of “roaming” for atomvm_examples. It is a little difficult to use until #1181 is merged, that...

I wish your second example had a stacktrace! You can see the scan result did come back with no networks found… this can happen with default scans (the dwell time...

My plan precisely! The PRs I have already submitted will provide all the necessary low level functionality, but I would like to create a higher level network_manager module that can...

As far as “dwell” time for the scan, I have found between 300-500ms will find all of the available networks, with the default (120ms) I do notice networks being frequently...

> it's the IO.inspect call that crashes, will look into it - used to throwing anything at IO.inspect.. That does sound like a bug, from my limmited understanding of Elixir...

> {0,[{none,[{rssi,undefined},{authmode,undefined},{channel,undefined}]}]} You did point me to a problem here, I started testing more boards and realized that even with maximum dwell time no network are being found. I cherry-picked...

When I split up the working branch I was testing new network features on I mistakenly submitted this PR first, but in order to use the scan function PR #1181...

> {0,[{none,[{rssi,undefined},{authmode,undefined},{channel,undefined}]}]} I did find a bug that would cause the results to be empty if only a single network was found, during most of my testing I had multiple...

I have pushed a [test branch](https://github.com/UncleGrumpy/AtomVM/tree/wifi-scan-test) that has these changes rebased on top of PR #1181, if anyone wants to test the example. The rebase is particularly ugly and easy...