When to use this profile
Use this profile when one node supervises a conductive rope in a plant room, data-hall aisle, or basement trench. The alarm is zonal. Map each physical run to a zone index in the commissioning pack so operators know which aisle to walk.
Mount the radio above the water line. Only the rope should get wet. If you also need a point probe in a drip tray, that is a different kit and a different decoder on the same application.
Join and reuse
Devices join with OTAA. Paste the shipped decoder into ChirpStack or The Things Network once, then clone the device profile when you add halls. A rising frame counter with a stuck wet flag usually means the rope is still bridged, not that the radio stopped.
Named fields
| Field | Type | Notes |
|---|---|---|
| wet | boolean | True when conductive liquid bridges the rope |
| zone | integer | Optional zone index for multi-run nodes |
| battery_mv | integer | Battery millivolts for maintenance planning |
| fcnt | integer | Frame counter; stalls mean a silent node |
Example after decode
{
"wet": true,
"zone": 2,
"battery_mv": 3300,
"fcnt": 184
}Byte offsets live in the decoder file shipped with the kit. If the first uplink disagrees with this example, trust the shipment file and the factory functional-test record.
Related pages
FAQ
Does the PS-210 decoder report distance along the rope?
No. It reports wet/dry and a zone index. It is not a distance-to-leak locator.
Which bands does the shipped PS-210 decoder assume?
Standard quotes cover EU868 and US915. Confirm other regional plans on the quote before you lock firmware.
Where do I paste the PS-210 codec?
ChirpStack device profile or The Things Network payload formatter. See the integration pages for the click-path.
What if the example JSON does not match my first uplink?
Trust the decoder file in the shipment over this summary. The functional-test record shows the payload captured before the kit left the factory.