Field contract
After decode, dashboards should show open/closed, battery millivolts, and a frame counter. Mount the reed on the frame and the magnet on the leaf within the datasheet gap.
Correlate door openings with temperature or leak alarms in your application logic. The decoder only reports contact state.
Commissioning checklist
Join with OTAA, paste the PS-220 codec, and verify open/closed matches a manual door cycle. Record hinge side, normally-open versus normally-closed wiring, and DevEUI in the commissioning pack. Align magnet and reed per the datasheet gap.
Door contacts explain access and warm spikes; they are not leak or temperature sensors. Pair them with leak and cold-room kits when the site story needs both.
Limits and related kits
PS-220 reports contact state and battery, not temperature or wet/dry. Use PS-610 for product temperature and PS-210 or PS-211 for water. Security-grade intrusion systems are out of scope for this industrial contact kit.
Facility and cold-room solution pages describe when door status belongs on the same dashboard. Order from the PS-220 product page.
Integration notes
Publish open as a discrete beside temperature and leak points for the same room. Use application logic to correlate a warm spike with an open door rather than inventing a combined payload. Document reed gap and magnet side so replacements restore the same open polarity.
Stock trials should prove one door leaf before branding. OEM manuals must keep the PS-220 field names identical to the shipment codec.
Named fields
| Field | Type | Notes |
|---|---|---|
| open | boolean | True when the magnet gap exceeds the reed threshold |
| battery_mv | integer | Battery millivolts |
| fcnt | integer | Frame counter |
Example after decode
{
"open": true,
"battery_mv": 3350,
"fcnt": 12
}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
Is open the same as wet?
No. Door contacts report open/closed. Leak kits report wet/dry. Keep separate device profiles.
Typical magnet gap?
Confirm on the datasheet; many installs stay within about 15 mm. Larger gaps cause false opens.
Heartbeats?
Hourly heartbeats are common so a silent node is obvious even when the door stays closed.
Where do I paste the codec?
ChirpStack device profile or TTN payload formatter. See the integration pages for the click-path.
Does open mean forced entry?
No. Open means the magnet gap exceeded the reed threshold. Access policy and security response stay in your procedures.
Can door contacts share a gateway with leak kits?
Yes on the same LoRaWAN network. Keep separate device profiles and decoders per model.
What if open chatters?
Check magnet alignment and gap. Mechanical bounce is an install issue, not a decoder bug.