@jcaron Thanks a lot for your help. However, I just found out that my gateway wasn't on the latest version of the firmware. Upgrading to v6.46.4 solved my problem. It seems like due to some reason TTN chooses to use RX1 for my LoPy and RX2 for my LSN50s. I'm guessing there was some kind of issue with the RX2 in the previous version of the firmware.

@mbivans It seems to me that your problem was cause by PyBytes. You cango back to V1.20.2rc6, and once you have the REPL open, issue the commands: import pycom pycom.pybytes_on_boot(False) That setting survives reboot and power cycling, and will result in performing the expected and documented behavior.

Okay I've made a new function in the modwlan.c in the LoPy firmware that returns a tuple containing mac and ipv4 address for each connected devices. Here the GitHub PR link : https://github.com/pycom/pycom-micropython-sigfox/pull/415 It may be useful for some people ! ;-)

I continue without understand what is happening. I did a lot of tests. I changed the tx_retries, I changed the send frequency interval and the problem continues.

Imho you problem originates in the use of "read(20)". You could try to send b'33.5|xxxxx|xxx|xxx \n' or after writing r on the lopy you add a uart1.write(chr(13)). On the Raspi you read rec with rec=ser.readline(). So if one or more chars go missing you don't lose your intended string formatting for the other data.

@jcaron Thanks for clarifying. Seems that LTE NB-1 is what i want. Then i can just use NTP like if i was on regular WiFi right? Or do i get access to that only with CAT-1? Seems that this is the easiest and solution, and not too expensive if i buy a M2M card (Machine to machine subscriptions)

Hi I have data generated by a Raspberry and that I must distribute via a lopy (with a lora network) So I have to connect lopy to the rpi via USB, can someone among you help me

Dear @martijnthe, we have been able to successfully get the boot time of our Terkin-Datalogger [1] from about 25 seconds down to about 3 seconds by freezing the modules like outlined by @robert-hh. The code base including all third-party modules is around 10 kLOC and we have released the result as builds called Annapurna [2]. With kind regards, Andreas. [1] https://github.com/hiveeyes/terkin-datalogger [2] https://community.hiveeyes.org/t/annapurna-firmware-for-pycom-esp32/2754

@jcaron Thank you so much. It is fully my mistake, i forgot to remove that 10 and i am thinking it is sending 5 packets per sec. Now everything fine, Thanks a lot once again :) :)