US What an IoT controller does
An IoT controller is a device that controls equipment on site and is connected to the internet or a private network at the same time. It reads inputs, decides what to do, drives outputs and reports what happened to a server, cloud dashboard or control room. The name covers everything from a microcontroller board in a smart home product to a DIN-rail computer running a factory line.
Every IoT controller does the same four jobs. It reads inputs: switches, 4–20 mA and 0–10 V sensors, meters on a serial bus or battery sensors over radio. It runs logic: a threshold rule, a script, a Node-RED flow or a PLC-style program. It switches outputs such as relays, valves, lights and motor starters. And it talks upstream, publishing data and receiving commands and configuration changes.
The important point is that the logic runs locally. If the network drops, a well-designed IoT controller keeps the pump running or the light schedule going, buffers its data and sends it when the link returns. Some wireless network vendors also use the name for management software that controls Bluetooth and Zigbee radios in access points; this page covers the hardware meaning.
Types of IoT controller
IoT controllers range from a single chip on a small board to full industrial computers. They are usually grouped by how much logic and I/O they handle.
-
//
Microcontroller boards. ESP32 and Arduino-class boards with Wi-Fi or Bluetooth, used in prototypes, consumer products and simple monitoring.
-
//
Compact IoT I/O controllers. Small sealed or DIN-rail devices with a handful of digital and analog channels and a LoRaWAN, NB-IoT or 4G radio. Streetlight and luminaire controllers are a common example.
-
//
Connected PLCs. Programmable logic controllers with MQTT or OPC UA built in, so the same device runs the machine and reports to the cloud.
-
//
Edge controllers. Industrial PCs on a DIN rail running a soft PLC such as CODESYS, Node-RED or containers, combining control, data handling and local analytics in one device.
-
//
Software controllers. Cloud or on-premises applications that manage fleets of connected devices without touching I/O directly.
IoT controller vs PLC vs IIoT gateway
These devices overlap, and many products sit across two columns. The difference is mainly where control happens and how much I/O the device handles itself.
| Device | Main job | Runs control logic? | Typical I/O | Typical connectivity |
|---|---|---|---|---|
| PLC | Deterministic machine control | Yes, in fast fixed cycles | Many digital and analog channels, expandable | Fieldbus and industrial Ethernet |
| IoT controller | Local control plus remote data and commands | Yes, usually simpler logic | A few to a few dozen channels | MQTT, Modbus TCP, cellular, LoRaWAN |
| IIoT gateway | Collecting and translating data | Rarely | Serial and network ports, little direct I/O | Ethernet, 4G/5G, Wi-Fi |
| RTU | Remote telemetry for SCADA | Limited | Field I/O at remote sites | Radio, cellular, DNP3, IEC 60870-5 |
| Edge controller | Control, data and analytics together | Yes, often a soft PLC | Onboard I/O plus I/O modules | Multiple Ethernet, cellular, cloud |
An RTU is the older utility-world cousin of the IoT controller, built around SCADA protocols rather than cloud ones.
Protocols an IoT controller uses
Connectivity is what makes a controller an IoT controller, and most support several of these standards at once.
-
//
Modbus RTU and Modbus TCP. The common language of meters, drives and sensors, used to read field devices on RS-485 or Ethernet.
-
//
MQTT. A lightweight publish and subscribe protocol, standardized by OASIS and as ISO/IEC 20922, used to send data to brokers and cloud platforms.
-
//
OPC UA. The IEC 62541 standard for secure, structured data exchange between industrial systems, increasingly built into PLCs and edge controllers.
-
//
LoRaWAN and NB-IoT. Low-power wide-area radio for battery sensors and remote controllers, such as streetlights, tanks and pipelines, where cables are impractical.
-
//
BACnet. The building automation protocol (ISO 16484-5) used for HVAC, lighting and access control.
Choosing an IoT controller for industrial sites
Start from the I/O and the site, then the software. Count the digital and analog signals, and check whether inputs need isolation from noisy field wiring; our white paper on DIO vs GPIO for IIoT and edge computing explains why that matters. Where the controller needs more channels, digital I/O modules extend it.
For the hardware, look for 24 V or wide-range 9 to 36 V DC input, an industrial temperature rating, DIN-rail mounting and cellular backup on remote sites. DIN rail PCs suit edge controller roles that run a soft PLC, Node-RED or analytics, while industrial IoT gateways suit sites where data collection matters more than control. For security, follow IEC 62443 practice: secure boot, signed updates, encrypted links and no default passwords.
Quick answers on IoT controllers
IoT controllers: common questions
Is a PLC an IoT controller?
It can be. A PLC with MQTT or OPC UA connectivity to a cloud or remote system works as an IoT controller. A standalone PLC with no network link upstream does not.
Is an Arduino an IoT controller?
Boards with Wi-Fi or cellular can be. Arduino and ESP32 boards suit prototypes and light monitoring, but lack the isolation, certification and temperature range expected on industrial sites.
What is an edge controller?
An industrial computer that controls as well as computes. It runs a soft PLC or control software alongside data processing and analytics, usually on a DIN rail in the control cabinet.
Does an IoT controller need the cloud?
No. Many report to an on-premises server or SCADA system instead. The local logic should keep running whatever the state of the connection.
What is an NB-IoT streetlight controller?
A small IoT controller fitted to each lamp. It switches and dims the light on a schedule, reports faults and energy use over the NB-IoT cellular network, and takes commands from a central management system.
We supply DIN rail PCs, gateways and I/O for IoT control projects with the operating system, protocols and remote management set up as standard, and validate the I/O before the system ships.