If bluetooth was not working, than that could be blamed on tight loop without opportunity to release processor (sleep), but that is not the case. Following code takes few minutes to get to green light: import pycom from network import Bluetooth bluetooth = Bluetooth() pycom.heartbeat(False) # disable the heartbeat LED pycom.rgbled(0xff0000) pycom.rgbled(0x00ff00) pycom.rgbled(0x0000ff) It seems that same resource (line?) driving BLE is used for bit banging LED in 1.3... There is change about it in 1.4.0, so maybe this will be fixed.

@daniel about examples - will be good to see sample wire like is for arduino [image: F8J00SLHLZRHA0Q.MEDIUM.jpg?width=614]

@minkley Still struggling to get the firmware upgrade to work on linux. Note, I'm not using an expansion card but a Serial USB cable which powers the device up and allows me to connect to the wifi I'm also able to connect to the serial port with minicom and I get the following python version: >>> print(sys.version) 3.4.0 >>> When I try and update the firmware I get the following error. Namespace(file=None, port='/dev/ttyUSB0', speed=115200, tar='/tmp/tmp.zR12S6HK0s/update.tar.gz') Connecting... Uploading stub... Running stub... Stub running... Changing baud rate to 115200 Changed. Exception: empty file, on line 131 This what I am doing exactly: As root Downloaded and extracted pycom_update_1.0.0.b3.tar.gz cd into pyupgrade run ./update select WiPy 2.0 Disconnect device from USB Put G23 into GND Plug in USB cable Press and hold the the reset button for about 3 seconds Press enter on the update Type in the serial path :-> /dev/ttyUSB0 Deselect high speed Then it fails with the "Exception: empty file on line 131. Just to be sure my EMS32 connectivity is good, whilst connected via minicom, if I plug in G23 to GND hit reset, I see the device is waiting for a download >>> ets Jun 8 2016 00:22:57 rst:0x1 (POWERON_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2)) waiting for download Perhaps someone can point me to the firmware file and a command line script I can use to test the install. I really would like to complete the upgrade and get on with using the device :)

@arneme great to hear that, thanks for the feedback :-)

Hi Happy new year 2017, I think the function to disable and turn off BLE and WiFi is a must it is great to have an overview of the coming releases Thanks

@daniel please add to the list (may be optional list) but to not forget about: Wifi AP+STA encryption of python scripts to protect code https://forum.pycom.io/topic/309/two-questions-to-pycom-protect-code-and-delivery-of-fipy/3

@DongYin look at: https://docs.python.org/3/tutorial/inputoutput.html there are paragraphs about files also look here https://docs.pycom.io/pycom_esp32/library/uos.html os.mkdir create directory

@rskoniec thanks. I'll correct that immediately.

Sorry for the late reply, The quick and simple way of implementing this is to deal with it in your packet string, define an ID field and run it as an include, have your build assign that file uniquely to each of your devices and then just have it as an element in the packet string. Then it's easy enough to unpack the string when you process it and filter by device.

yes @daniel this is amazing that this was so simple like wrong password from some old documentation :) connected two wipy2 together - I (6100) wifi: n:6 1, o:6 0, ap:255 255, sta:6 1, prof:6 I (7074) wifi: state: init -> auth (b0) I (7077) wifi: state: auth -> assoc (0) I (7086) wifi: state: assoc -> run (10) I (7101) wifi: connected with wipy-wlan-6ec2, channel 6 WLAN connection succeeded! MicroPython v1.8.6-251-g2fb950d on 2016-12-16; WiPy with ESP32 Type "help()" for more information. >>> Connected to AP wipy-wlan-6ec2 channel 6I (17086) wifi: pm open, type:0, st: 0, sending null data: 0 sadly that we and you did not find this before It is a pity that the company where I work has already given the money for other purposes. But we "meet" in the next year.

@livius regarding your problem trying to connect 2 WiPy's together, please check my reply in: https://forum.pycom.io/topic/376/interim-update/6 Thanks. Cheers, Daniel

@lmn Hi! ADR will be available in the firmware release we make this Friday. Best wishes Fred

@Fred Thank you for an update with such long waited good news. Keeping fingers crossed for Dev Team! :o)

@Fred said in Week Commencing 28th Nov Update: Hi, I am pleased to say that we did :) I will make a general announcement on the forum. Best wishes Fred Great! :o)