@brocaar thank you for an opportunity to have an opensource Lora gateway, network and app servers. This is really cool to be able to get a fully functional Lora setup by yourself with a such detailed documentation. I am making my own POC with your product and Globalsat devices on AWS and when my POC will be ready I will gladly add my step-by-step how to for a fully AWS native setup (EC2, RDS, Elasticache, Cloudwatch, IOT etc). But right now I am facing some issue which I cannot understand (yet!) from a Lora AppServer.
When I troubleshoot radio traffic which is captured by my gateway from my class A end device (GlobalSat LT-100) I can see proper uplink data frames captured and forwarded to my Lora Network Server and Lora AppServer:
If I get PHYPayload from the frames and use lora-packet decoder with valid NwkSKey and AppSKey I can see expected data payload (
PHYPayload=405F376D10000C0002C330DC1ADE48B4A93A214356A85C8A) which gives me proper decrypted end data:
So based on that I assume that end device sends proper payloads which are properly encrypted and transmitted.
Unfortunately when I check relevant MQTT topics or Live LoraWAN Frames / Live Device Data in Lora AppServer GUI I can see something weird under Data:
AllhAhF/6gH4T0s=. How this data had been calculated by AppServer? What should I do to get expected encrypted data that had been sent by the end device (
Thank you in advance.