Hello!
I’m having a problem simulating downlink messages in the TTN Console.
I configure my downlink message as above (01 02 03 content) and then, when I go to check it in the Live Data dashboard, a different (apparently random) bytes content appears (DF E2 23):
If I resend this message, I get different payloads every time…
Does anybody know what could be wrong here?
Suggests that what is being shown in the console is the payload as encrypted for transmission. The node’s LoRaWAN stack should decrypt the received payload before handing it off to whatever part of the firmware is supposed to consume it.
The frame count is part of the encryptor initialization so the same payload will not yield the same cyphertext twice.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.