TTN Decoder Repository Update Issue

pcciot-administrator
Tue, 20 Jan 2026 12:25:32 +0000

pcciot-administrator:

I would like to open this discussion in the hope of advising caution to other TTN users when selecting “use device repository” when creating sensor applications and introducing hardware.

Hi @descartes you may note the purpose of this discussion, to advise caution when using a feature on TTN. I’ve quoted it here for you again. Milesight have been informed, separately. I’m of course aware that Milesight are the ones to change their decoders, however TTN is the platform where all applications are automatically changed to use the new decoder, and are therefore directly relevant to this notice.

This issue is relevant to all users using the device repository for their applications. 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. 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”.

Full consideration of the text within an informative post may lead to a more constructive discussion. This was not a support request, nor an opportunity for unnecessary correction, it was a caution related to a feature with alternative workarounds.