@bucknall @jcaron @jmarcelino Guys, mystery solved. It seems like I have already damaged the sender Pycom by sending packets before attaching the antenna to it (improper use...). Now I used another Pycom acting as the sender and there is <1% packet loss. Lesson learned the hard way. Always read all documentation before playing around with the board :/

See the following post on how to manually flash the firmware: https://forum.pycom.io/topic/517/downgrading-firmware-advanced-users

@Cristi You can definitely do this, however you will need to write a simple protocol to talk to the different devices and associate an ID to each of them. Here's a link to some documentation that will help you get started - https://docs.pycom.io/pycom_esp32/pycom_esp32/tutorial/includes/lora-nano-gateway.html Let me know if you need any more support! Thanks, Alex

For the record, there is now a socket.recvfrom(bufsize) method that will return a (data, port) tuple.

Thanks for the suggestions! Still looking to get some examples how to serialize sensor data with MicroPython for TTN. All examples I found are for Arduino. Maybe @bucknall has some nice examples around?

@bucknall While one LoPy is sending and getting ACK, if I turn ON another LoPy it stops the communication (there is a collision), so, what can I do to avoid that collisions?

@blackansible Try this modification in your nanogateway.py code: https://forum.pycom.io/post/8290

@stef , sensor type Pycon should be avail:

@PiAir Thanks.

@bucknall Thank you so much for your help! I'm ashamed but It was all my fault. The LoRa antenna on one of the devices was not correctly wired, I'm using an extension cable ... I modified the script so to have pong sending back some info: Node A: from network import LoRa import socket import time lora = LoRa(mode=LoRa.LORA, frequency=915000000) s = socket.socket(socket.AF_LORA, socket.SOCK_RAW) s.setblocking(False) while True: rec = [s.recv(64).decode()] if "Ping" in rec[0].split(" "): print(rec[0]) s.send('Pong %s' % rec[0].split(" ")[-1]) time.sleep(5) Node B from network import LoRa import socket import time lora = LoRa(mode=LoRa.LORA, frequency=915000000) s = socket.socket(socket.AF_LORA, socket.SOCK_RAW) s.setblocking(False) x=0 while True: s.send('Ping %s' % x) time.sleep(5) x=x+1 print(s.recv(64).decode()) I can send the code via wifi on the LoPy with no needs of microsd card on the device. If the wifi connection drop or I close it, the LoRa communication keeps goig :) when I reconnect with wifi in the atom shell I can actually see the ping number growing. More post coming soon, but I'll make sure to check the wiring first ... I'm really excited! Thanks!

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")

@GerryS I've raised the priority for the engineering team and they're on the case to fix it. Thanks!

There are MicroPython drivers for epaper displays. E. g. : ayoy/micropython-waveshare-epd, supports 1.54" Waveshare two-color E-Paper Display only : https://github.com/ayoy/micropython-waveshare-epd mcauser/micropython-waveshare-epaper, for many display sizes : https://github.com/mcauser/micropython-waveshare-epaper https://forum.micropython.org/viewtopic.php?f=14&t=3393

@jeromemaquoi really better if you show some sample what do. As you can read here detail was provided by chat but better is write on the forum and ask question with sample and exact error message.

@livius Node should talk about each hour (or maybe less, but I don't think I'll go lower than 10 minutes) do to a keep alive and update informations or "right away" if there's a trigger trigged (alarm). I'm pretty sure the hardware can do it, I was less sure about the MicroPython (I saw there was some limitation if we compare to the Python3). I'll order some for testing I guess ! :)

Hi @Eric24, I might be incorrect on this but I believe that when you wake from deep sleep, the device should start up with the radios turned off. Regardless, you should be able to configure the radios to remain off at power on by tweaking and building the firmware yourself. I'll make this suggestion to have an option to disable radios baked into our official Firmware itself.

@jmarcelino Thank you.

@Andrea-Filippini You are welcome :-)

@bucknall I was wondering the same. I found that the necessary changes are on this line: { MODEM_LORA, REG_LR_PAYLOADMAXLENGTH, 0x40 },\ As 0x40 is 64 and is this that is limiting the payload size.