That’s probably not a TTN problem (the data has cryptographic checksums, if it were corrupted, passing the checks anyway would be an extremely rare coincidence) but rather a software bug in the value encoding or decoding.
Get the bare data of the decrypted packet and decode it by hand and see if that makes sense.
Many attempts to write things like javascript decoders to run online fail over subtle bugs with things like sign extension, etc.
If all else fails, modify the node firmware to print out (on the debug serial port) the reading, then a hexdump of the plaintext packet to be sent - which should be the same as the decrypted packet you get from TTN.
I think this because you choose Cayenne LPP decoder type? Ursalink sensor payload strucuture has differences with Cayenne format:https://www.ursalink.com/en/download/t1_payload_structure.pdf
You could choose Custom decoder and add the decoder example to check it.