Hi @Kenneth, thank you for taking the time to look that up and add it as an idea!

@jardar I had the same question today. (Funny coincidence.) I found this by searching the forum: "The only optimisation at the moment is enabling WLAN Power Saving in STA mode (basically the WiFi radio only 'wakes up' at the beacon interval set by your gateway) so you'll see current go down to about 50mA and then 100+ mA at the wake intervals. This is done by re-initilizating WLAN with power_save=True option. However it's not perfect yet, it may caused network timeouts for some people so it became disabled again by default." (Source)

@dhk111 As you found 4 clients is the maximum number of clients for the LoPy or WiPy in AP mode. This is a limit set by the microcontroller core libraries/framework we use (ESP-IDF) so probably not going to increase anytime soon.

@letsgo If you have a home router & access point, the easiest is to have both LoPys connected to that. For that, follow the instructions at https://docs.pycom.io/chapter/tutorials/all/wlan.html, section: Connecting to a router. if you want to connect them directly, one of them has to run as access point (AP), the other as station (STA). Since the devices run as AP by default, you just have to reconfigure one of them the way, told above.

There might be something in the code to change it but that would require compiling the firmware etc so its probably easiest to stick with the python library

Thank you. :)

I would like to eventually do this as well. has anyone figured this out. how to allow fipy to act as wlan station and forward all data outbound via LTE?

@andrethemac thanks for the advice, you saved me a lot of wasted time. I was able to use the Windows Pycom Upgrade Tool without any problems. It seems the Linux command line tool does not work. Can someone form Pycom confirm they have tested this? If so I will raise something in GitHub as it looks like a bug.

@pierrot10 Yes, you can use a FTDI cable, or a RasPi. YOu need to connect Tx, Rx and GND. Verify that the output voltage of the adaper is set to 3.3V, since ESP32 input are not 5V tolerant.

Hi, Thanks for the feedback, I will definitely make this information clearer with our upcoming documentation refresh.

Found the issue. It was actually caused by gc.collect() run time going from 6mS to 48mS. This was being run inside a timer tic ISR (I know, that's a no-no). The ISR was taking longer to run than the timer tic period. I assume the UART Int is a lower priority than the timer so it was never being processed. Is gc.collect() taking so long because of the extra memory or is this a bug?

I was looking for alternatives to the ESP32, but I have discovered that Pycom is also based on ESP32. There is a problem with ESP32 connecting to WiFi using WPA2 Enterprise. It seems that you are having the same problem. Reference: https://github.com/espressif/arduino-esp32/issues/1381

@livius Thanks for the Chrono snippet. I'm always glad to find these nicely packaged design patterns.