LGT-92 is not working as supposed, and all devices use identical APP EUI A000000000000102

[arjanvanb (Arjan)]

That’s how I understand some people have fixed it, yes. Others claim to not run into any problems with a non-unique AppEUI at all, including @quu_jeff above. (Seeing that some ran into trouble, I’d want to understand or fix that even if things were working now.)

Without access to the gateway traffic in TTN Console, it’s hard to debug. In case this is the first time you added an off-the-shelf device:

• Did you select the proper AppEUI in the device settings too? So: add A000000000000102 to the Application, and make sure to select that option in the Device’s settings.

• You also set the Dragino AppKey and DevEUI for the device in TTN Console, right?

@LukasL

I followed the official PDF tutorial from Dragino and this one from YT: https://www.youtube.com/watch?v=ff6D7hKrWhc

You might want to link to that manual if you want people to validate that. Sorry, I’m not going to watch a video to see if there’s anything wrong in there.

@quu_jeff

Data on the TTN application console disappears quickly. this is by design. Try to view the console within minutes of your test. Otherwise try adding a data integration and using the swagger UI. This will unfortunately add more complications like API authorization and payload translation.

Even more: you’ll need to have the TTN Console website open before the traffic is received. Using the Data Storage integration should not complicate anything, and is often helpful without using Swagger; see Why application data is shown as historical?