Uplinks not showing up in application data when payload is not empty

[arjanvanb (Arjan)]

@Zaack-dev

After downlink reception, not forwarded to app = 402A2E01268103000D0402F7F9C4A264

That includes FOpts = 0x0D, being a DeviceTimeReq which might be causing display issues. Use the MQTT Data API to see if you receive the data. Also:

@cultsdotelecomatgmai

If I change something trivial in the TTN web console application configuration, save, and then change it back and then save again then, sometimes, the uplinks all start to appear on the web console.

Or do not ask for DeviceTimeReq, as you’ve implemented your own protocol for that anyhow. As for synchronising time, see also Time synchronisation of a Node - #28 by arjanvanb.

@Zaack-dev

Prior to downlink reception, forwarded to the app = 402A2E0126800100006287970A73

I’d say that’s an invalid packet, as it defines a payload of 0x62 and uses FPort 0. So, this payload should be a MAC command, but it’s undefined?

In the case of an empty payload, maybe FPort 0 is okay. But even then the specification is open for multiple interpretations, maybe expecting at least one MAC command:

If present, an FPort value of 0 indicates that the FRMPayload contains MAC commands only.