Yes you can download your code wirelessly, have a look at https://docs.pycom.io/getting-started/programming/ftp But you still need some connection to power your Sipy And yes you can download via RX/TX wire but you need de FDTI 3.3V cable or something similar

@malachib As @reidfo wrote, inspect your boot.py file and all .py files involved in your running project (main.py, etc.). You can also check as below: import pycom pycom.wifi_on_boot() pycom.wifi_ssid() pycom.wifi_pwd()

@thibault The antenna selection does not matter at all, because the W01 has just one antenna port which will used in any case.

@martijnthe Intresting. my guess would have been a weird thread race between your thread and our code that deals with setting up wifi on boot. But if its still happening with that's disabled I'd guess its something else. Ill raise it in tomorrows standup and see if anyone else know's anything about it.

You can use an FTP client (like FileZilla) to see and transfer files on the flash drive of your device via a static wifi (e.g. have your device and laptop connected to your home wifi) or by using your device as an access point (connect your laptop to the device wifi). https://docs.pycom.io/gettingstarted/programming/ftp

I confirm that wlan.antenna(WLAN.EXT_ANT) works with Pycom firmware > 1.18.1.r1.

@joseph I'm afraid I can't give you a timeline. The BT mesh is developed by Espressif, once they release it, we can start working on the implementation. We'll update the forum when we have a development version ready.

@bmarkus And what are the best values for getting that? (on EU zone)

@jcaron Thank you very much for your reply. Turning off WiFi on boot seems to fix the issue. Apparently it was related to the PyCom starting in AP mode for telnet.

Hi @klaus, Currently, you can only configure one WiFi network, and save multiple in the Pybytes console.

@robert-hh Thanks, that is perfect.

@brady-aiello You have to change it on the xxPy device. I usuall switch to station mode in my boot.py script and connect the xxPy device to my home AP.

Hi @joseph, No, not yet. I have spent a few days on it, but no progress. I keep getting Connection refused when trying to connect, so something must be wrong with my server code. Have you tried connecting it to a different device (e.g your computer)?

@Ralph, thanks very much. It now works again.

This is strange behavior. When I assign it a new ssid / pw, it acts as an access point, and I can directly connect to it. When I delete the device, and add it again with an ssid / pw for the local wifi, it connects to that, and subsequently connects to PyBytes.

@jmpratt I don't think so, because the pin is hardwired to the antenna switch internally. This has been a problem for us, too. I would advise against using P12 for anything anyway, because it also selects the boot mode. Therefore it will force the device into safe boot if P12 is for some reason high while it is booting.

@stefan-1212 said in 1 Kilometer Wifi range on the FiPy: After that I also implemented the lr (long range) WiFi protocol supported by the ESP32 in the FiPy firmware What changes did you make?

@clementdecaux Not only is there no USB support directly on the LoPy (I guess you connected to the UART lines), but additionally USB is 5V while the LoPy only supports 3.3V...