In short: Modbus devices cannot send their own data to the cloud: something on site has to read their registers and pass the values on. In Hermetry that is Hermetry Edge, software that runs on a licensed gateway or router next to the devices. It reads them over Modbus RTU (RS485) or Modbus TCP and sends their readings to Hermetry over one outbound, encrypted connection, so nothing on site has to accept connections from the internet.
Why Modbus needs something on site
Modbus is a request and response protocol from the control panel world. A Modbus device waits to be asked: a master reads its registers, one request at a time, over a serial line (Modbus RTU on RS485) or the local network (Modbus TCP). The device never starts a conversation and knows nothing about the cloud. To see its values on a dashboard, something on site must ask the questions, turn the register values into named readings and send them on.
What Hermetry Edge does
- Reads the field devices. Edge polls Modbus RTU devices on RS485 and Modbus TCP devices on the site network. Which protocols a gateway reads depends on its model.
- Makes each one a device of its own. Every field device appears in Hermetry as a child device of the gateway, with its own readings, alarms and dashboards, while all of them travel over the gateway’s one connection.
- Dials out, never in. The gateway connects to Hermetry over TLS with its own certificate from the platform’s authority. No fixed IP, no port forwarding, no VPN of your own.
- Keeps readings through outages. Licensed gateways can keep data while the link is down and send it afterwards with the time each value was read; how much depends on the model.
- Is managed from the platform. Settings and signed firmware are sent remotely, in waves, to one gateway or a whole fleet.
What you need
- A licensed gateway or router from the list of licensed devices, with the interface your devices use: an RS485 port for Modbus RTU, or the site network for Modbus TCP. The hardware is bought separately; Edge is priced on its own.
- The register map of each device: which registers hold which value, their data type and scaling. The maker’s manual has it.
- For Modbus RTU: the serial settings (baud rate, parity, stop bits) and each device’s address on the line.
Step by step
- Install. Mount the licensed gateway next to the devices and wire them to it: the RS485 pair for Modbus RTU, or the network for Modbus TCP.
- Claim. Open the claim window on the gateway’s local Cloud page, then claim it in Hermetry under Devices › New device. The gateway left the factory with an identity Hermetry knows; nobody types credentials on site.
- Choose the field devices. On the gateway, set up the devices it reads: serial settings, addresses, register maps and polling intervals, and which of them it reports to the cloud. Their names become the child device names in Hermetry.
- Map them to profiles. Children get a profile by the type the gateway reports, or the gateway profile’s profile for new children. Create one profile per kind of device (for example “Energy meter, three-phase”), so each kind has its own keys, alarms and dashboards.
- Run. Watch the readings on a dashboard, set alarm rules, and update the gateway remotely when needed.
Getting the registers right
Most first-day problems are register problems, not network problems:
- Offsets. Register 40001 in a manual is often address 0 on the wire. If every value looks shifted, check the offset.
- 32-bit values. A float or a 32-bit counter spans two 16-bit registers, and makers disagree on their order. A value that looks absurd is often a swapped word order.
- Polling interval. Poll as often as the process needs, not as fast as the line allows: a slow RS485 line with many devices is easy to overload.
Our article on Modbus register addressing goes deeper into offsets, function codes and floats, and PLC data logging without touching the PLC program covers reading a PLC that is already running a process.
On Hermetry’s cloud, Modbus devices are read through Hermetry Edge. On-premises installations can also use gateway software of their own through the gateway API described in Devices behind a gateway.
Frequently asked questions
Can Hermetry read Modbus devices directly from the cloud?
No. Modbus devices answer requests on their own line or network, so the reading happens on site, by Hermetry Edge on a licensed gateway, which then sends the values to Hermetry.
Do I need a fixed IP address or a VPN?
No. The gateway dials out to Hermetry over TLS; nothing on site accepts connections from the internet.
What happens when the connection drops?
Licensed gateways can keep readings while the link is down and send them afterwards with the time each was read, so they land at the right place in history. How much a gateway keeps depends on its model.
Does every Modbus device become a separate device in Hermetry?
Yes. Each one is a child device of the gateway with its own readings, alarms and dashboards, while all of them share the gateway’s one connection.
Read more: Hermetry Edge, Licensed gateways and Hermetry Edge, and the use case Automatic energy meter reading across many sites.

