TTN Decoder Repository Update Issue

descartes
Tue, 20 Jan 2026 12:02:22 +0000

No one here can action your suggestion - suggestions should be made as a GitHub repro.

TTI, the developers of the free software & infrastructure you are using, do not change the payload formatters for a device, that is done by the manufacturer, so you may want to take this up with Milesight.

You could script something that checks GitHub for any PF changes but overall, I’d go with explaining to Milesight how they shot some customers in the foot. There is version of device available which they could have implemented to leave the old one alone.

Also, tell them that magnets aren’t open or closed, so door_status would have been better if they were going to mess with the semantics of the PF.

Plus, PF aren’t guaranteed to be processed on any TTS if server load times out the processing. Good practise is to decode yourself from raw at your own end point as you have control over both the code and system load.

Additionally, if your applications are not directly used by the communities, you may fall in to commercial use territory which means that a TTI instance with access to the TTI team to take up such issues would be appropriate - @rish1 can advise you best.