Skip to content
SiteSync SiteSync Docs

Decoder concepts

Applies to SiteSync StandardEnterprise Management Introduced in 1.0.0 Role: Administrator

A decoder turns a device’s raw LoRaWAN payload into named, structured values SiteSync can model as tags. Decoders are selected on a device profile — one decoder per profile — and run automatically on every uplink from devices using that profile.

Two ways to decode

Section titled “Two ways to decode”
  • JavaScript decoder — a function you paste in or a .js file you upload, run inside SiteSync.
  • API decoder — SiteSync sends the payload to a URL you specify and uses the decoded response.

See Create a decoder for both.

Managing decoders

Section titled “Managing decoders”

SiteSync lets you add, delete, and manage decoders — including updating decoder titles and uploading decoder files — so only relevant, current decoders are available to device profiles.

Key behavior

Section titled “Key behavior”
  • A decoder is required on a profile. Without one, decoding fails for every device on that profile.
  • When adding a new sensor type, create or select a decoder that matches the device’s payload format, then assign it in the device profile.
  • If a device shows no data or is flagged Decode Error, check that the correct decoder is assigned in its profile.
Section titled “Related tasks”
Was this page helpful? Report incorrect documentation Last reviewed 2026-07-30