TTN Decoder Repository Update Issue

descartes
Tue, 20 Jan 2026 13:15:12 +0000

pcciot-administrator:

you may note the purpose of this discussion, to advise caution when using a feature on TTN

That was the first paragraph. Good point.

But then it looked like an issue about known functionality outside TTI’s remit with suggestions on what TTI & the user base could change to ameliorate the situation.

pcciot-administrator:

As such, there seems to be no benefit from discussing it directly with a commercial use support team, while keeping the wider TTN community uninformed.

I didn’t say to not tell TTN users. I was noting that if you are outside the remit of TTN by having a critical issue with the way it works, you are best off using TTI. And life-ring cabinet sensors strike me as being pretty critical, so using a service with no SLA that’s explicitly for testing and called Sandbox triggers a certain amount of cognitive dissonance. Always fear The Daily Mail headlines!

pcciot-administrator:

You may also note that your advise on good practice is redundant as I already stated we’d “manually enter custom payload decoders, which can be made or sourced from device manufacture websites”

The point I was making was about not running the PF at all. Ever. Not even on TTI. Because timeouts. Which means all values should be validated which can be done by boundary checks or by running the PF locally with an error handler. So you may as well run it once locally where you have control.

All these PF’s have to be held in Redis in memory which increases server load on the free service for memory & CPU time. So copying the PF in to the application or, worse, device, is not great for TTN and can still lead to errors due to timeouts.

As to the last paragraph, I saw the post differently. Giving us all heads up or a reminder was great. I did perceive there was a suggestion of a notification system - a change - an issue. I also perceived an error in the description how TTN device PF’s are updated, which is not arbitrarily by TTI, potentially leaving people to request changes of TTI when it would be better for people to be directed to the right place, the manufacturer. The work around creates additional processing load on a free service.

You say tatws, I say potato.