V3 uplink message format

https://www.thethingsnetwork.org/docs/applications/mqtt/api/index.html specifies the v2 uplink message format. i searched for a v3 uplink message format specification but could not find any. could you please provide a link to such a spec.?

many thanks in advance.

Start here: https://www.thethingsnetwork.org/docs/

thanks for your answer.

i found Major Changes In The Things Stack | The Things Stack for LoRaWAN but a quick look at a real upload message confuses me me a little bit, because_

uplink_message.locations.user.latitude seems to be uplink_message.location.latitude
uplink_message.locations.user.longitude seems to be uplink_message.location.longitude
uplink_message.locations.user.altitude seems to be uplink_message.location.altitude

question: will the message format change according to the spec or is the spec outdated?

Which spec? You’ve got the link to the v3 docs, so all the info on v3 that is known is there - maybe take some time to drill down in to it all to see the details provided?

Major Changes In The Things Stack | The Things Stack for LoRaWAN is the only doc i found and it contradicts my received data, but anyway … please close this topic.

Many apologies, I copied the wrong link, it should have been:


But it seems you were already there - and in there are integrations (menu at the top) with gives MQTT which gives an uplink example:


I have a question about uplink message. Right now Im sending the data to my tago.io account. But on the same uplink message is sending a lot of stuff that I don’t want or need like for example: lora_bandwidth, fcnt, snr, fport, rssi, etc… is there a way to send only the data I want on my TTN account like: Temp and Batt?
thank you

Not at present - but you can ignore the data you don’t want and there isn’t any intrinsic cost to you for the extra transfer beyond the extra TCP packets which requires power which leads to global warming …

Thank You @descartes