Closed jcwren closed 4 years ago
You're not the only one to notice. See for example https://www.thethingsnetwork.org/forum/t/the-workbench-part-3/21125/323 (about an hour ago).
My devices get these downlink messages (on port 0, empty payload) as well.
Most likely the real issue is the one described in this thread: https://www.thethingsnetwork.org/forum/t/recent-change-in-adr-handling-in-tnn-and-lmic-generate-downlink-loop/24164
The good news is that the problem seems to have been addressed by the LMIC code this library is based on (MCCI Catena LMIC). I've integrated the latest LMIC code and pushed it to a separate branch: https://github.com/manuelbl/ttn-esp32/tree/lmic-master
I will integrate it into the master branch once an official release is available on https://github.com/mcci-catena/arduino-lmic.
This seems to be a step backwards, as I can no longer join the network at all. Unless I missed a step...
Using your directory structure, per the Wiki:
cd components/ttn-esp32
git checkout lmic-master
cd ../..
make clean
make
make flash
Doesn't look like the hello-world
example changed, so no API differences.
Ignore that. It took an excessive number of retries, but finally did join. It does seem to join faster on the master
branch than on the lmic-master
branch, for some reason.
I have several different LoRaWAN stacks running on various devices, such as the ST Micro LRWAN stack, whatever's in the Microchip RN2903, and the LMIC stack. The LMIC stack is running on a Heltec V1 board configured for the US915 band plan. It's talking to the The Things Network server, but the server is sending a downlink message on every uplink, unlike the other stacks. Now I suspect this is a LMIC thing, but I'm starting here, wondering if this has been seen before. It occurs almost every time, although there's the occasional packet that doesn't.
Any ideas what I'm looking at here? As I say the data is showing up decoded in the TTN console, so the DevEUI, App EUI and App Key are all correct.
Bad:
Good: