After resetting frame counters, payload is shown on gateway traffic but not in application

I really doubt that will help. Resetting the node would make it execute a new OTAA join, but why would that help…? (Update: it likely will help; see next posts.)

Indeed, I very much wonder about that as well.

For TTN: yes maybe; see next post. For your node: no. The node does not know you changed that setting.

Yes. (But the uplink counter known to TTN will already have adjusted itself (see next posts). It’s only the downlink counter that might be troublesome for ADR, as the value known to TTN will be lower than the one known in the node. But I’d assume all that does not affect your current problems. Doing a new OTAA Join will fix all counters as well.)

Maybe the following will do the job; see also https://www.thethingsnetwork.org/docs/network/cli/api.html#ttnctl-devices-set

But: I’ve never tested that. (And the post above is about DevAddr that starts with 00.)

So, do you have any other devices to test the above?

Hmmm, that is not “Exactly like that!” when comparing to my screenshot? But it seems the additional “bridge” is due to different type of gateways; my screenshot was for a TTN Gateway and indeed for a Kerlink I see two more lines, referring to some “bridge”. So that’s probably not related to any problems either.

(As an aside: my note about posting screenshots for terminal output surely also applies to posting the DevAddr and all please don’t post screenshots for data that someone might need to copy; would you really expect the team to re-type the DevAddr, gateway ID and all from a screenshot…? But well, they already said they cannot investigate any further :frowning: )