Decode uplink data message failure

[DylanWork]

Hi all,

I have an error coming through the console that I’ve noticed, I don’t see any other posts on it.

I’m unsure if this error means that the message doesn’t reach it’s final location (another service subscribes to its mqtt topic etc).

This error occurs pretty rarely, I’ve seen it 3x over several weeks of testing with multiple units, but there were plenty of times I wasn’t looking and if the right packet gets missed it can really mess with the end results.

Has anyone seen or experienced this error?

Cheers,
Dylan

[descartes (Nick McCloud)]

This is a known thing with the JS decoder which is a convenience function only.

Entering “script timeout” in to the search box, the second item looks particularly useful:

How to reduce size of payload formatter script now larger ones are blocked

This is the original issue that was raised internally to TTI: You’ll note that the v3 stack is already seeing timeouts (not just TTI sysops, I have seen timeouts on the console as well as in WebHook packages for <1k decoders) so some correction was inevitable. This happens often enough on v2. The bottom line seems to be that payload formatting is a convenience function that should not be relied upon for production deployment, ie, decode the raw payload on your own servers. I really like the …