@robert-hh Thanks for your reply Robert, and I apologise for being late.

Not sure what the possibilities for this are nowadays, as the email address is also tied to your Pybytes and webshop account using a single-signon. Please send me a private message if you still want your email changed and I'll let you know if it is still possible!

@Asim-Khan uart.read() is non-blocking. If there is no data available, it returns None. And None ist not an object with a buffer protocol. Thus the error message. You have to test before sending, if you have read something from the UART.

@MJ On my Pycom.gpy I imported os, took a look at the directory, then os.remove('FILE NAME') >>> import os >>> os.listdir() ['sys', 'lib', 'cert', 'boot.py', '%1', 'test2.py', 'project.pymakr'] >>> os.remove('test2.py') >>> os.listdir() ['sys', 'lib', 'cert', 'boot.py', '%1', 'project.pymakr'] >>>

I have made the test with scan intervals and scan windows equal to 10 ms. static esp_ble_scan_params_t ble_scan_params = { .scan_type = BLE_SCAN_TYPE_ACTIVE, .own_addr_type = BLE_ADDR_TYPE_PUBLIC, .scan_filter_policy = BLE_SCAN_FILTER_ALLOW_ALL, .scan_interval = 0x10, .scan_window = 0x10 }; The results are better but still not as good as v1.20.3.b0 Beta Firmware was. With the new values, I raised up to 60% of advertisement frames catched. Always with the same conditions and 500 ms as advertisement interval.

@Gonçalo-Ferreira can you clarify exactly which settings you are changing, and what values you are setting them to? Not familiar with Chirpstack settings, but the usual RX window settings are just an offset from end of uplink to start of RX1, and then RX2 happens a second later. The duration of the windows is based on allowed data rates. When you change RX windows settings, the settings are sent to the device in the join accept IIRC, so changing those settings won’t affect the ability of devices using OTAA to receive downlinks. The ideal RX offset is the default, 1 second. Anything longer will require the device to stay on longer and draw more power. Not that the device doesn’t listen for the full max duration of a frame, but just enough to recognise a preamble or thereabouts. So even at SF12 it’s only a fraction of a second, not over a second.

Hi, I would not recommend powering through Vin with a battery and USB at the same time. As the 5V from the USB will start charging your battery connected on Vin. When connecting to the battery terminal, there is a detection circuit that switches the power source of Vin between USB and battery to not put 5V on the battery lines.

@robert-hh Nice! Thank you Robert!

@Benjamin-Mavinga I'm not sure how the wiring could be the same? The TMP36 has 3 pins, the MQ7 has 6, and you need to supply a variable voltage to the MQ7 to change temperature of the heating element and measure the resulting change in conductivity?

@Gijs Yes, You're right. I cleared the cache of the browser, and that changed the layout & content of the page.

I understand @livius confusion. If you installed the micropython firmware from pycom-micropython-sigfox, you'll have to upload micropython files to the device, like the example they mentioned. Though if you want to run C, you do not need to install the pycom firmware. Its possible to just upload C code to the device. Perhaps have a look at the Platformio IDE (platformio.org) to learn more about that (note that this is outside the micropython / pycom scope and I cannot support you any further in that direction)

@Felix-Siegmeier i have recently found a netrc file for upload easy (by ftp). Extract of the netrc file (wich called "NETRC_UPLOAD" on my computer) : machine 192.168.4.1 login micro password python macdef init cd /flash put circuit.mpy put commande.mpy put main.py mkdir lib put lib/logging.mpy And for use this file with ftp (tnftp) use the following command (run for me): ftp -N NETRC_UPLOAD 192.168.4.1 In this way, the upload was done alone (by wifi) in the right path.

Hi, At the moment, we do not have the Pygate certified with the FCC yet, once we get the reports, we will upload them to the documentation page: docs.pycom.io/datasheets/expansionboards/pygate

As I mentioned before, we make use of an adapted version of the Lora-net gateway stack: https://github.com/Lora-net/lora_gateway/tree/master/libloragw, if you look at our open source firmware, you'll find a folder called pygate where most of the driving code is: https://github.com/pycom/pycom-micropython-sigfox/tree/Dev/esp32/pygate. I dont know if such a compatible example exists for a lora repeater.

for anybody else running into this - pretty sure it's about the memory consumption as explained here: https://docs.pycom.io/tutorials/expansionboards/pygate/#setup