Does it work reliably if repeated for hundreds of requests? Properly raised exceptions are acceptable in my opinion.

@stef I've reported the same problems, but in my case I scan continuously, as the LoPy is USB-powered. https://forum.pycom.io/topic/1255/lopy-stops-detecting-ble-advertisements I very much hope it's not a hardware problem.

@Officina I just tried running the device with 3.3 V on Vin, and it works. At the moment, the DC in is at 2.95 V, and still running. According to the data sheet of the regulator, it goes into a bypass mode if the input voltage is too low, and that's what I wanted to confirm. So it looks as if is more safe to run with a low Voltage on Vin.

@MrMarty77 Only ADC1 is supported at the moment, the core ESP32 SDK doesn't support it yet, it may take a while: https://github.com/espressif/esp-idf/pull/466 Fyi, we're a bit hesitant to make ADC2 available because it is also used for pretty important control loops inside the WiFi (and maybe BT, I don't remember) drivers. We want to make sure there's no chance of these and the user ADC calls to interfere with each other.

After doing a lot of extra experimentation, I found the problem to be solvable by moving the WiFi setup code ( so the wlan.init() calls ) to boot.py and by including the mode parameter in the wlan.init() call instead of doing a preliminary call to wlan.mode(). There are some hickups with connecting to the LoPy through the new configuration on Windows, but it seems to work fine on Linux.

while (True): recv_pkg = lora_sock.recv(512) time.sleep(0.2) if(len(recv_pkg) > 13): print(recv_pkg) recv_pkg_len = recv_pkg[12] # unpack the message based on protocol definition dest_addr, src_addr, pkg_len, msg = struct.unpack(_LORA_PKG_FORMAT % recv_pkg_len, recv_pkg) if(dest_addr==SRC_ADDR): ack_pkg = struct.pack(_LORA_ACK_FORMAT, src_addr, SRC_ADDR, 1, 200) lora_sock.send(ack_pkg) else: print("Message lost")

@MarcusKirsch I found the 5V pin (doh!) all good all running.

@Eric24 The debug messages at startup, before the micropython interpreter starts, are not stopped, but this is not a problem for me. No further debug messages are output once the python interpreter is started, unless the system throws an error. The startup debug messages are output at 115kbs. To stop the debug messages, my understanding is that one can compile a custom image with debug messages disabled, but I have not attempted this as they are not hampering my application.

@littlebat thx man!

For the moment , my code is working with ESP-IDF on an ESP32 board , but i need LoRa support . Will try to add the LoRa stack working for the SX1272. By the way , is there a way to know the ESP framework version used by the LoPy ? in Python , got no detection from some of my BT beacons ( same problem using 3 LoPy board) , but it's more like its an ESP IDF problem- link May be it would be solved in futur firmware ?

@Smeedy You must slightly modify this library. Add from machine import Pin and e.g. instead self.clk.init(clk.IN) write self.clk.init(Pin.IN) self.dio.init(self.dio.OUT) write self.dio.init(Pin.OUT) instead self.clk.low() write self.clk.value(0) instead Pin(4) write Pin('P4')

@jmarcelino Unfortunately, the procedure posted here https://github.com/pycom/pycom-micropython-sigfox/issues/5 doesn't work. I' ve followed these steps: Change bootloader (1536 -> 1024) make BOARD=WIPY TARGET=boot make BOARD=WIPY TARGET=app make BOARD=WIPY flash everything work and now with Filezilla I can upload file with size > 1MB After I create a new image edited the frozen file _boot.py with a print("Hello World") make BOARD=WIPY TARGET=boot make BOARD=WIPY TARGET=app with Filezilla I copy appimg.bin in /flash/sys/ reset the board (with the physical button ) firmware doesn't change Instead if I execute: make BOARD=WIPY flash, the firmware changes. So I think that "the updater task" doesn't start on reset. EDIT: I notice that the file appimg.bin uploaded with Filezilla disappears immediately, before reset.

@soren current firmware is 1.6.13.b1 but i never have had problem with line number in error message Do you have line break as LF or CRLF or mixed?

@mmbermudeza You'll need to build the entire Pycom image and for that you need the full ESP-IDF too but it doesn't take very long to build. You don't need any IDEs, just the free compilers. Start with the instructions at https://github.com/pycom/pycom-micropython-sigfox#the-esp32-version to setup your build environment but before the make.... flash step move to these instructions instead: https://github.com/pycom/pycom-micropython-sigfox/blob/master/esp32/README.md I gave some build tips on the other thread so so may be worth a quick read if you get stuck https://forum.pycom.io/topic/1173/no-python-prompt-after-downgrading-firmware/2 thread where Programming is simply over the serial port, just like a firmware upgrade