Open teusH opened 2 years ago
I don’t have a solution but can confirm I have had the same issue. As a result cannot implement deepsleep on LoPy4. I had this problem with Chirpstack backend so I suspect the problem is with the Pycom firmware.
On 1 Dec 2021, at 2:16 am, Teus Hagen @.***> wrote:
Use of LoPy4, firmware 1.20.2.rc10 (jan 2021) Issue with sending LoRa datagram to TTN V3 Stack after restore LoRa nvsram.
Migrating LoPy4 from V2 to V3 The Things Network Stack went ok after power off LoPy4, reset LoRa nvsram, power on. First join went OK. Rejoin after power cycle went ok. If no LoRa nvsram dump/restore is used sending to TTN V3 Stack works OK.
The issue: those LoPy4's which use a restore of LoRa nvsram (so no rejoin) for sending the next datagram the LoRaWan package is not received by TTN. So the deepsleep/reuse of LoRa state seems not to work with V3. With TTN V2/deepsleep there was no LoRa state restore problem. V3 is using a strickter LoRa implementation. E.g DevID use. Is this a firmware issue or a use of LoRa state software issue?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/pycom/pycom-micropython-sigfox/issues/582, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIITVH7KKYAERRP7LOMEKDUOTTEXANCNFSM5JCCLJ4A.
Use of LoPy4, firmware 1.20.2.rc10 (jan 2021) Issue with sending LoRa datagram to TTN V3 Stack after restore LoRa nvsram.
Migrating LoPy4 from V2 to V3 The Things Network Stack went ok after power off LoPy4, reset LoRa nvsram, power on. First join went OK. Rejoin after power cycle went ok. If no LoRa nvsram dump/restore is used sending to TTN V3 Stack works OK.
The issue: those LoPy4's which use a restore of LoRa nvsram (so no rejoin) for sending the next datagram the LoRaWan package is not received by TTN. So the deepsleep/reuse of LoRa state seems not to work with V3. With TTN V2/deepsleep there was no LoRa state restore problem. V3 is using a strickter LoRa implementation. E.g DevID use. Is this a firmware issue or a use of LoRa state software issue?