Modbus and SNMP equipment reaches an IoT platform through something that asks it for data, because both protocols answer requests rather than report on their own. A gateway on site polls the field devices and sends each one’s readings over a single outbound connection, or a poller reaches an SNMP agent across the network.
A meter on an RS-485 line has no idea the internet exists. Getting it onto a platform comes down to three questions: who asks it for data, from where, and how each answer keeps its device’s identity.
Why do Modbus and SNMP devices need a gateway or a poller?
They speak only when spoken to. The Modbus Application Protocol Specification calls Modbus a request/reply protocol for client/server communication, in which the client initiates each transaction, so a Modbus device waits to be asked.
SNMP reads work the same way: a manager asks the agent for objects and the agent answers. Notifications (traps and informs) are the exception, which RFC 3410 describes as unsolicited transmissions. A Modbus RTU device sits on a serial line with no IP address, so something on that line has to read it (the wiring is in RS-485 wiring for Modbus RTU).
Opening a port so a cloud service can reach into the site is the wrong fix; port forwarding security risks explains why. The safer shape is a gateway that polls locally and dials out.
What should a Modbus IoT gateway do for the devices behind it?
It should read each field device on a schedule, turn raw registers into named values, and report every device separately over one outbound, encrypted connection. I check five points before I trust one:
- One identity per field device. Each meter gets its own history, alarms and screens, not a pile of keys on the gateway.
- Timestamps from the read. A reading stamped when it was taken lands in the right place in history, even after an outage buffer. That needs a synchronised clock on the gateway.
- Named, scaled values. A raw register means nothing on a screen; a value with a name and a unit does. The register map work is in Modbus register addressing.
- Outbound only. Nothing on site should accept connections from the internet.
- A way back. A setpoint written to a holding register goes through the same gateway, which has to report whether it was applied.
Hermetry connects field devices to live dashboards, rules and alerts: IoT telemetry and SCADA in one platform. Since 2.2.2 (4 November 2026), a gateway reports for the devices behind it through the gateway API. It logs in as itself, marked as a gateway, and Hermetry creates each field device as a child device the first time the gateway reports it, with its own readings, alarms and dashboards; commands and shared attributes reach a child through its gateway. A gateway takes 500 children by default and never more than 1,000. Hermetry Edge, software on licensed gateways, reads Modbus RTU over RS485, Modbus TCP, OPC UA and BACnet/IP, depending on the model (see gateways and devices behind a gateway).
Should SNMP equipment be polled on site or from the cloud?
Poll on site when the agent sits on a private network or only speaks SNMPv2c. A cloud poller needs a route to the agent, either a public address or a VPN or tunnel into the site, and that route is only as safe as the SNMP version on it.
RFC 3410 says SNMPv1 and SNMPv2c support only trivial authentication based on plain-text community strings and are fundamentally insecure. SNMPv3 adds authentication and privacy through its user-based security model. I would not send a v2c community across the internet. Traps are the other reason to stay local. The agent pushes them, so the receiver has to sit where the agent can reach it, and on a private network that means on site.
Which values to read from a UPS, and which ones deserve an alarm, are in remote site UPS monitoring.
Frequently asked questions
Which port does Modbus TCP use?
The Modbus Application Protocol Specification says Modbus can be reached at the reserved system port 502 on the TCP/IP stack. A gateway that reads Modbus TCP devices on the site network usually connects to that port on each device; the device itself never needs a route to the internet.
What happens to the devices behind a gateway when the gateway goes offline?
In Hermetry, all of a gateway’s child devices go offline with it. On any platform, a silent meter behind a gateway can mean a failed meter or a failed link, so I check the gateway’s own connection first and alarm on it separately from the field devices.
Can Hermetry receive SNMP traps?
Traps are received on site by a licensed gateway; the cloud has no trap listener. For an agent polled from the cloud, Hermetry’s docs suggest polling the relevant status OIDs and adding an alarm rule on their keys to be alerted quickly.

