Threshold crossed
Chiller 4 · 28.4°CSensor to work order, auto-routed
Sensor tripped.
Work order routed.
Before the call.
LoRaWAN sensor signals open a work order from the matched template, routed to that template's default assignees, with configured SOP or checklist if applicable. The signal arrives, the response is already in motion.
LoRaWAN-native · 7 LNS providers · 30+ sensor types · Routed via Infodeck Workflows
Smart Event Rule fires
Chiller Emergency rule matchedWO opened, routed
WO-2026-1432 · HVAC team · Mike J.When the sensor knew. The team did not.
The auto-response loop replaces what manual rounds miss.
Without Infodeck
- The freezer was warm all weekend. Nobody knew.
- We check equipment manually once a month.
- Energy bills keep climbing but we do not know why.
- The chiller drifted out of spec at 2am. Nobody saw it until the call from the tenant.
With Infodeck
- Routed work orders when readings cross thresholds, opened from the matched template, against the asset, with configured SOP or checklist if applicable.
- 24/7 monitoring without manual checks. The sensor watches; you watch the queue.
- Property history per device for the last 120 days, so you can see whether this trip is the first or the fifteenth.
- Data quality flags help teams identify and filter suspect readings in device history, charts, and exports.
How sensor response gets routed
Sensor threshold met. Work request opened.
Connect via your LNS. Set the rule once. The matched template carries assignees, priority, and configured SOP or checklist where applicable.
Smart Event Rule
Chiller Emergency Auto-Response
When Sensor:Chiller Room Temp>28°Cfor5 min
Condition declared in Workflows. Threshold and duration both required.
Then Create work request from Chiller Emergency template
Single THEN action. Template carries default assignees, priority, and (where configured) SOP or checklist.
Powered by Infodeck Workflows.
Sensor-triggered rules require Professional plan or above.
Building protocols (Modbus / BACnet)? See BMS.
Sensor types we receive from
Connect any sensor
Connect any LoRaWAN sensor through supported integration services.
Temperature & Humidity
Cold storage, server rooms, climate-controlled spaces.
-18.5°C Freezer 2
21.4°C Server Rm A
45% RH avg
Air quality
CO2 / PM2.5 / TVOC
412 ppm 12 µg/m³ · 0.3 ppm
Energy
Power & current
2.4 kW 230V · 10.4A · PF 0.98
Water leak
Detection
Water detection can trigger a routed alert or work request when the configured threshold or rule fires.
Dry Server Rm · Basement · OK
Occupancy
Motion & people count
12 / 0 / 4 Mtg A / B / Lounge
7 LNS providers
ChirpStack V4Infodeck LNSLoriotAWS IoTActilityHTTPTheThingsNetwork
Per-device data view
One asset, one history. The first trip or the fifteenth?
Property History charts for the last 120 days per device. Connection state with last-uplink timestamp. For broader portfolio analytics, see /platform/analytics/.
Asset
Chiller Room 4 · Building A · Level 2
Online
RSSI -78 dBm · SQI 8
Property History · Temperature
30-day view (120-day available) · Last uplink: 2 min ago
Reading Threshold (28°C)
Current 22.4°C
24h avg 21.8°C
History window 30 days
Downlink Send command ↓
Who works with the loop
One signal. Three vantage points.
Facility Manager
I get the work order before the call.
The auto-response loop opens the work order against the asset from the matched template, assigned via the template's default assignees, before the tenant phones the front desk.
Maintenance Technician
The job arrives with the asset context already in it.
Sensor breach to work order opened from the matched template, assigned via template default assignees, with asset history and (where configured) SOP or checklist already attached to the work.
FM Manager / Ops
Which devices keep tripping thresholds?
Per-device history shows whether this trip is the first or the fifteenth. For broader portfolio analytics, see /platform/analytics/.
FAQ
Common questions
What sensors does Infodeck support?
LoRaWAN sensors connected through supported LNS providers: ChirpStack V4, Infodeck LNS, Loriot, AWS IoT, Actility, HTTP, TheThingsNetwork. Sensor properties are defined by asset type and codec.
How do sensors connect to Infodeck?
Each LNS provider POSTs uplinks to a forward-hook endpoint. Connect once per LNS service, then link individual devices to assets.
Can sensor data trigger work orders?
Yes. Smart Event Rules use the Workflows engine to open a work request from a matched template when a threshold condition fires. The template carries default assignees, priority, and (where configured) the SOP or checklist. Sensor-triggered rules require the Professional plan or above.
How long is sensor data retained?
Plan-gated: Lite 7 days, Basic 30 days, Pro 90 days, Enterprise 365 days. Property History charts cover up to 120 days. Export available.
How does device status monitoring work?
Four states: Online, Stale, Offline, Unknown. RSSI / SQI signal quality on every reading. Last-uplink timestamp on the device record.
What happens when a sensor sends a bad reading?
Mark it with a Data Quality flag. Flagged readings can be filtered out of device history charts and exports. See /platform/data-quality/.
Can Infodeck send commands back to a sensor or actuator?
Yes. Send downlink commands from the device detail page. Requires the Asset Type to have Actions defined and the Integration Service to support downlinks.
How is this different from BMS integration?
BMS integration bridges building-management protocols (Modbus, BACnet, MQTT). IoT auto-response bridges LoRaWAN sensors via LNS providers. Both end the same way: a routed work order.
LoRaWAN sensors supported
Ready to let sensors open the work order for you?
Connect via your LNS. Set the rule once. Every threshold breach opens a work order from the matched template, with the template's default assignees and (where configured) SOP or checklist already in place. Before the call.
Data Quality FlagsRole-Based AccessPlan-gated data retention