Protocol integration · Two-way
DI/DO to LoRaWAN — Wireless I/O
Many assets expose simple dry contacts — run, trip, alarm, door open. LoRaWAN I/O modules read them and can switch relays remotely through downlink.
- What problem do we solve?
- Simple status and on/off control often requires a surprisingly expensive wired I/O extension.
- How do we solve it?
- MatrixAI engineers the Digital inputs / outputs ↔ LoRaWAN conversion — device audit, converter selection, mapping, decoding and commissioning.
- What technologies do we use?
- DI/DO, LoRaWAN, network server codecs, MQTT / REST
- What can we integrate?
- IoT platforms, BMS, CAFM, SCADA, billing and cloud services
Architecture
Digital inputs / outputs ↔ LoRaWAN
- 01
Contacts & Relays
Run · Trip · Door
- 02
I/O Module
LoRaWAN
- 03
Gateway
Class C for control
- 04
Platform
Events & commands
- 05
Operators
Alerts · Control
How we do it
Engineering steps
- 01List contacts and relay outputs required
- 02Select I/O module and power source
- 03Configure change-of-state uplinks
- 04Configure downlink commands for outputs
- 05Test fail-safe behaviour
Typical data points
- Run / stop status
- Trip and fault alarms
- Door and hatch contacts
- Relay output state
Use cases
- Pump run and trip monitoring
- Remote lighting control
- Generator status
More integrations
Other protocols
FAQ
DI/DO integration questions
How quickly does a remote relay switch?
With Class C devices, typically within seconds. Class A devices only receive commands after they send an uplink, so they are not used for time-critical control.
Need Digital inputs / outputs ↔ LoRaWAN integration?
Tell us about your site, assets and existing systems. A LoRaWAN specialist will review your requirements and propose a practical architecture — no obligation.