Device profile
Create a device profile per model. Set the LoRaWAN version and regional parameters to the channel plan on the quote — EU868 or US915 unless the paperwork says otherwise. Enable OTAA. ABP is not the default for these kits.
Attach the codec to that profile. The codec file ships with the kit and is summarized on the decoder pages for PS-210, PS-240, PS-410, and PS-610. If the first uplink does not match the public example, trust the file in the shipment.
Application and devices
Put plant-room leak nodes and tank level nodes in one application if they share a gateway and one operations team. Keep device profiles separate. Name each device with the room or tank name, and store the DevEUI in the asset register.
A join-accept followed by uplinks means the radio path works. A join-accept followed by codec errors means the profile points at the wrong decoder. A missing join means keys, region, or coverage — not the JSON field names.
What to check when the dashboard is empty
Frame counter stuck: the node is silent or the session was reset without a rejoin. Frame counter moving and fields null: codec. Frame counter moving and values present: your downstream integration, MQTT, or database, not the sensor.
Gateway duty and spreading factor are network-server topics. If only the far tank fails, walk the survey again before you change the codec that already works on the near tank.
Related pages
FAQ
One codec for every Particlesensing model?
No. One device profile and codec per model. Cloning is safe only onto the same hardware.
OTAA or ABP?
OTAA. The kits ship join credentials for OTAA. Do not invent ABP keys.
Where are byte offsets documented?
In the decoder file shipped with the kit. Public pages list named fields and an example JSON.
Does ChirpStack replace our BMS?
No. ChirpStack is the network server. Forward decoded fields to the BMS or historian over the integration you already run.