The uplink JSON format is documented. You add the decoded fields if you implement a payload formatter. The same scheme was used for v2.
TTI don’t arbitrarily skip payload formatter processing. If the JavaScript processing takes longer than 100ms then it is dropped and the original JSON is forwarded on. Otherwise the Application Server runs the risk of becoming thread bound and grinding to a halt.
The principle time this occurs is when a perfect storm of uplinks arrive simultaneously with a fair number of them requiring the larger multi-purpose formatters. A LNS has a limited amount of time to get an uplink to the end system and potentially receive a response to then forward to a gateway to downlink, so time is of the essence.
A forum search yields: Best practices in order to decode the payload
I didn’t, you did:
I’m sorry you feel this is hostile - I was attempting to reframe exceptions, particularly regarding the role & boundaries of the LNS.
Here’s a strategy:
It may seem that the fastest and most efficient resolution is for Wattics to process the JSON which then opens up their service to TTI users. The format is not specific to LoRaWAN so I’m sure they have to process incoming data for other services.
However you then have the problem that the payload format is specific to a device, so you then need something to transform it, but you can’t sure will be processed.
Best practise is that you should not rely on a third-party service to store your original data - they may purge it after post-processing and outright data loss is not unusually.
So your very best strategy is turn on Data Storage so there is a copy on the TTI servers as a last gasp backup, put in a webhook to a data sink for your own backup (one of mine costs just £7/year) and use a webhook to AWS Lamda functions to re-format the data to suit Wattics, see Payload Format to include only measurements
Being an AWS server-less function, all the scaling is taken care of for you. And as mentioned in the above post, may actually be free.
Whilst this strategy is free and you get what you pay for, etc etc, I’ve presented on web hooks at two TTI online conferences last year as well as providing a frequently implemented set of templates - GitHub - descartes/TheThingsStack-Integration-Starters: Starter / Template code for various The Things Stack (v3) integrations - so it may merit some inspection.