Most devices talk to Hermetry themselves over MQTT, HTTP or LoRaWAN. This section covers the devices that do not, and the tools around the gateways and routers they sit behind.
There are two ways a device can reach Hermetry through something else:
| Way | How it works | Typical devices |
|---|---|---|
| Behind a gateway | A gateway on your site reads the field devices and reports for them on its own connection. Each field device becomes a child device in Hermetry. | Modbus meters and controllers behind a licensed gateway, sensors behind your own edge computer |
| Polled by the platform | Hermetry connects to the box at a public address on a schedule, through an endpoint that holds its address and credentials. | SNMP agents (switches, UPSs, servers, printers), cameras and recorders |
Either way, the result is an ordinary device: it has a profile, readings, attributes, alarms and dashboards like any other, and it counts toward your plan’s device limit.
What is available today
| Feature | Status |
|---|---|
Child devices reported by a gateway (v1/gw/* uplink) | Available |
| Commands and shared attributes sent to child devices through their gateway | In development |
| Protocol endpoints and polled devices | Available |
| SNMP polling from the cloud (v2c and v3, to a public address) | Available |
| SNMP traps | Not received by the cloud |
| SNMP polling done on site by a licensed gateway | In development |
| Hermetry Edge on licensed gateways and routers (field protocols, buffering) | Available; capabilities depend on the model |
| OPC UA and BACnet in Hermetry Edge | In development |
| Remote access to a licensed router’s web panel | Available |
| eSIM profile management on licensed routers | In development |
| Local LoRaWAN network server on a router, LoRaWAN relays | In development, see Local mode and relays |
Cameras and recorders are polled devices too. They have their own section: Cameras.
Pages in this section
Gateways
- Devices behind a gateway: the
v1/gw/*topics, how children are created, their profiles and limits - Commands to devices behind a gateway (in development)
- Licensed gateways and Hermetry Edge: what Edge software adds on licensed hardware
Polled devices
- Protocol endpoints: adding a polled device, the public-address rule, write-only secrets, testing and discovering
- Polling devices over SNMP: SNMPv3 and SNMPv2c agents, the SNMP mapping of a profile, test polls
- SNMP templates reference: every key of the four built-in templates
- Polling intervals, back-off and quota
Licensed routers
Permissions
| Permission | Lets a person | Default minimum role |
|---|---|---|
| View protocol endpoints and the connection of polled devices | See endpoints and the Connection tab of polled devices | User |
| Create, edit, test and delete protocol endpoints; discover and connect polled devices | Add polled devices, change endpoints, run test polls | Admin |
| Open, enter and close the web panel of a claimed router | Use Open panel on a router’s device page | Admin |
| View the panel sessions of the workspace | Open the Panel sessions list | Admin |
The built-in IoT viewer role template sees endpoints and every IoT list, but has no right to change anything and sees no credentials or panel sessions. See Users and roles.
Related
- Gateways and devices behind a gateway: a one-page summary
- Licensed devices
- Choose how to connect your devices