Best LoRaWAN I/O controllers for industrial automation in 2026

Pairing a LoRaWAN I/O controller with the right field sensors is the first step, so start with the best IoT sensors for industrial monitoring and then pick the controller that reads or switches the rest. Best overall for retrofits: Dragino LT-22222-L. Best for mixed sensor interfaces: Milesight UC300. Best for irrigation and water valves: Milesight UC511. Models are compared from manufacturer documentation, not from lab tests.

Why this matters in 2026

Most factory floors, pump stations and plant rooms already contain equipment with a dry contact, a 4–20 mA output or a relay coil. Replacing that equipment is expensive. Wiring a LoRaWAN I/O controller to it is not.

The controller turns a physical signal into a LoRaWAN uplink, and a LoRaWAN downlink into a physical action. That is the whole job. It lets you monitor a pump status, read a pressure transmitter or switch a contactor without running network cable to the machine.

Kilo Electronics is an online authorised dealer of electronics and IoT hardware, selling to individuals, makers, professionals and businesses across Europe. Industrial automation is one use case among many, so the shortlist below is written for anyone from a hobbyist automating a workshop to an engineer planning a site rollout in 2026 or 2027.

What a LoRaWAN I/O controller actually is

A LoRaWAN deployment has four layers: the sensor or controller, the gateway, the network server and the application. The I/O controller sits in the first layer. It talks to a gateway over LoRa radio, and the gateway forwards messages to the network server over Ethernet, Wi-Fi or cellular backhaul.

Two consequences matter for buying:

• The controller is not a gateway. You still need gateway coverage at the site.
• Cellular backhaul on the gateway does not make the controller a cellular device. The controller only speaks LoRaWAN.

LoRaWAN is built for small, infrequent messages. In the EU868 band, duty-cycle rules limit most channels to 1% transmit time. That suits status reports and occasional commands. It does not suit fast control loops or anything that needs a response in milliseconds.

What makes a good LoRaWAN I/O controller

These are the criteria used to rank the models below:

• Interface mix: digital inputs, digital outputs, relay outputs, analog inputs (0–10 V or 4–20 mA) and serial ports such as RS485. Count what your machine needs, then add a spare.
• Power: mains, 12–24 V DC or battery. A controller that switches loads usually needs constant power; a battery model suits low-duty monitoring or valve pulses.
• Downlink behaviour: how and when the device listens. A Class A device only listens briefly after it transmits, so a command can wait until the next uplink. Class C devices listen continuously but need constant power.
• Enclosure and mounting: DIN rail, wall mount or outdoor housing, and the ingress rating. An IP rating does not prove suitability for every mounting arrangement, so check the manual for the intended use.
• Payload decoding: whether the manufacturer publishes a decoder for your network server, so you do not write one from scratch.
• Regional variant: the radio plan, such as EU868, must match the country where it runs. This is separate from any cellular band on the gateway.

LoRaWAN I/O controllers at a glance

The order of rows matches the sections below. Availability at Kilo Electronics is not stated in this table; the catalogue changes, so confirm that a model is listed before you plan around it.

1. Dragino LT-22222-L: best LoRaWAN I/O controller for retrofits

The Dragino LT-22222-L is a LoRaWAN I/O controller that combines digital inputs, digital outputs, relay outputs and analog inputs in a single unit. That mix is why it tops the list for retrofits. One box can read a run signal, read a 4–20 mA transmitter and close a relay on a starter.

A typical use is an older pump station. The controller reads the pump status contact, reads a level or pressure signal and lets an operator trip a relay remotely. No new PLC, no cable run back to the control room.

LT-22222-L pros:

• Covers inputs, outputs, relays and analog in one device, so fewer boxes per cabinet.
• Suited to adding remote monitoring to equipment that already exists.
• Dragino publishes manuals and decoder resources for common network servers.

LT-22222-L cons:

• Remote commands arrive as downlinks, so latency depends on the device class and uplink interval.
• Counts of each I/O type are fixed. If your cabinet needs more points, you add a second unit.
• Needs a suitable enclosure and wiring for an industrial environment; the bare board is not the finished installation.

LT-22222-L best for: retrofits that need a bit of everything. Verdict: Buy for monitoring-plus-switching jobs where timing is not critical.

2. Milesight UC300: best for sites with mixed sensor interfaces

The Milesight UC300 is an IoT controller that supports several interface types, including digital, analog and serial connections such as RS485. It is the better choice when the machine does not offer a simple contact, but has a Modbus-style serial device, a pulse output or an analog transmitter.

Imagine a small plant room with a flow meter on RS485, a pressure transmitter on 4–20 mA and a door contact. One UC300 can gather all three, and you manage a single device on the network instead of three.

UC300 pros:

• Handles several signal types in one controller, which reduces device count.
• Fits sites where the equipment mix is not yet fixed.
• Milesight provides a configuration tool and decoder resources.

UC300 cons:

• More configuration than a plain relay box. Someone has to set up each interface correctly.
• Features depend on the exact model and firmware version, so confirm the variant before ordering.
• Interface flexibility does not remove the need for sensors and cabling; those add to installed cost.

UC300 best for: engineers building a monitoring cabinet from varied equipment. Verdict: Buy when you have more than one signal type.

3. Milesight UC511: best for solenoid valve control

The Milesight UC511 is a valve controller rather than a general I/O unit. It is designed to drive solenoid valves, which makes it relevant to irrigation, water distribution and process lines that open and close on a schedule or on command.

That focus is both its strength and its limit. If your job is to open a water valve at a remote tank, it does the work without extra relays. If you want to read contacts, switch a motor starter and measure 4–20 mA, it is the wrong tool.

UC511 pros:

• Purpose-built for valve control, so the wiring is simpler than a relay-based workaround.
• Suits remote sites with no mains supply when the documented power option matches the valve type.
• Pairs naturally with tank and level sensing; see the LoRaWAN level sensor options in the related guide.

UC511 cons:

• Limited to the valve types it supports. Check the valve coil and voltage against the manual.
• Downlink-driven control means a valve command is not instant.
• Not a replacement for a general I/O controller.

UC511 best for: irrigation and water-valve jobs. Verdict: Buy for valves, Skip for anything else.

4. Dragino RS485-LN: best for bridging serial equipment

The Dragino RS485-LN is a converter, not a contact-switching controller. It connects an RS485 device, such as a Modbus meter or a drive with a serial port, to a LoRaWAN network. It is listed here because many industrial jobs start with a serial device rather than a contact.

If the equipment already exposes data over RS485, this is often cheaper and cleaner than adding a full I/O controller. If you need to switch a load, you still need a relay or an I/O unit.

RS485-LN pros:

• Brings existing serial equipment onto LoRaWAN without replacing it.
• Suits meters, drives and other devices that already speak RS485.

RS485-LN cons:

• You need the device's register map or protocol details to configure it.
• No relays or digital outputs of its own.
• Poll rate and payload size are limited by LoRaWAN, so it is not for fast data.

RS485-LN best for: serial-equipment monitoring. Verdict: Hold until you confirm the target device's serial settings.

How these were ranked

The ranking uses the criteria above and manufacturer documentation. It is not based on lab tests, field trials or customer reports. Each model owns a different job: retrofit switching, mixed interfaces, valve control, serial bridging. Kilo Electronics does not manufacture any of these devices, and other manufacturers also make LoRaWAN I/O hardware. If a model is not currently listed at Kilo Electronics, it is a comparison option, not a stocked product.

Total installed cost: what the controller price leaves out

The controller is rarely the biggest line on the bill. A realistic hypothetical for a small pump station looks like this:

• Controller: one I/O unit with the right mix of relays and analog inputs.
• Gateway coverage: if no LoRaWAN gateway reaches the site, you add one, plus its power and backhaul. Compare options in the guide to indoor LoRaWAN gateways for offices and warehouses or the enterprise LoRaWAN gateways guide.
• Antenna and cable: the antenna position often matters more than the radio model.
• Enclosure, glands and DIN rail: the controller must survive the environment it sits in.
• Power supply: a 24 V DC supply is common in cabinets; battery models trade that for replacement cycles.
• Network server: hosted service or self-hosted. If you host it, someone maintains it.
• Commissioning time: configuring, decoding payloads and testing relays on site.

The lowest-priced controller can cost more overall if it forces you to add a second unit or custom decoding work.

Safety and control limits you should plan around

LoRaWAN is not a safety system. Do not use a LoRaWAN I/O controller as the only way to stop a machine, trip an emergency circuit or protect people. Hard-wired safety circuits stay hard-wired.

Plan control actions around three facts:

• Downlinks are not instant. A Class A device only receives after it transmits.
• Duty-cycle limits cap how often a device and a gateway can send.
• A controller can lose contact. Decide what the relay should do on power loss or network loss, and test it.

Good fits are scheduled pumping, remote start for non-critical equipment, status monitoring and alarm reporting. Poor fits are interlocks and anything with a human-safety consequence.

Which LoRaWAN I/O controller should you choose?

Start from the signals, not the brand:

• One machine, contacts plus a 4–20 mA signal and a relay: the Dragino LT-22222-L.
• A cabinet with digital, analog and RS485 devices: the Milesight UC300.
• A solenoid valve at a remote tank or irrigation line: the Milesight UC511.
• A serial meter or drive you only need to read: the Dragino RS485-LN.

If you are undecided, choose the LT-22222-L for switching jobs and the UC300 for monitoring jobs, then confirm the exact variant and regional radio plan before you buy.

FAQ

One last thing

Count your signals before you compare models, then add one spare input and one spare relay. The most common reason a second controller ends up in the cabinet is a point that nobody listed at the start, and fitting it in 2026 costs far less than a revisit in 2027.