HiveMQ Edge: The Open-Source Gateway from PLC to MQTT
HiveMQ Edge Protocol Adapters: What Each One Reads, Writes and Costs
HiveMQ Edge protocol adapters compared: OPC UA, Modbus TCP, S7, EtherNet/IP, ADS and BACnet, read or write, polling defaults and licence status.
HiveMQ Edge protocol adapters are the part of Edge that talks to devices. Each adapter speaks one industrial protocol, holds a list of tags and turns them into MQTT messages. The questions that decide a design are which adapter your controller needs, whether it can write, how it gets data (polling or subscription), how often, and whether it sits behind the licence key. This page answers those from HiveMQ’s documentation as read on 20 November 2026. It is a child of HiveMQ Edge and part of the HiveMQ hub.
The short answer: Edge has adapters for OPC UA, Modbus TCP, Siemens S7, Beckhoff ADS, EtherNet/IP, BACnet/IP, MTConnect, HTTP(S), files, databases and a simulator. Most are documented as read-only toward MQTT, with EtherNet/IP logical addressing and OPC UA documented with write options. Polled adapters default to 1000 ms. HiveMQ’s documentation calls writing back a commercial southbound feature.
The HiveMQ Edge protocol adapters compared
Directions below are as documented. “Read” means device to MQTT. The pages were summarised by a fetch tool, so confirm parameter names on the live page before they go in a specification.
| Adapter | Direction | How it gets data | Key defaults and limits |
|---|---|---|---|
| OPC UA | Read, write, discover | Server subscription | publishingInterval 1000 ms, serverQueueSize 1, eventQueueSize 64; security policy NONE by default |
| Modbus TCP | Read | Polling | pollingIntervalMillis 1000, timeoutMillis 5000, publishChangedDataOnly true, 16-bit data type by default |
| Siemens S7 | Read | Polling | Port 102, polling 1000 ms, publishChangedDataOnly true; S7-300, S7-400, S7-1200, S7-1500, LOGO |
| Beckhoff ADS | Read | Polling | Port 48898, AMS port 851, address <program>.<variable>, polling 1000 ms |
| EtherNet/IP (CIP logical addressing) | Read, write | Polling | Address @class/instance/attribute, port 44818, default data type SINT, default read only |
| BACnet/IP | Read | Polling | Port 47808, discovery every 5000 ms, polling 1000 ms |
| MTConnect | Read | Polling of agents over HTTP(S) | Polling 1000 ms, publishes every interval |
| Databases | Read | Query per tag | PostgreSQL, MySQL, MS SQL; polling 1000 ms; publishes every interval |
| HTTP(S), File, Simulation | Listed | Varies | Simulation writes only to tags with a static value |
What is free. HiveMQ’s documentation lists the OPC UA, Modbus, Siemens S7, Beckhoff ADS, EtherNet/IP, HTTP(S), File Input, Simulation and BACnet adapters as open-source features. The MTConnect and Databases adapters are documented but not in that list, and their licence tier is not stated. HiveMQ’s Edge overview lists southbound MQTT to OT as a commercial feature, currently for the OPC UA adapter only. The adapter page also documents write options for EtherNet/IP logical addressing (it uses the CIP service Set_Attribute_Single) and for static-value Simulation tags. We could not reconcile these two statements from the documentation alone, so confirm with HiveMQ whether EtherNet/IP writes need the licence key. The other adapters we read are documented as read-only.
Polling and subscription settings that matter
Polling defaults to 1000 ms and goes down to 1 ms. HiveMQ’s documentation gives pollingIntervalMillis a default of 1000 and a minimum of 1. A tag list polled at 1 ms is not a data strategy, it is a load test on a controller. The plant consequence is on the scan: reads compete with the program for controller time, a point covered in PLC scan cycles, polling and SCADA data. We would start at the speed the consumer needs, not the speed the adapter allows.
OPC UA settings apply to the whole adapter. The documentation states per-tag values are not supported for the subscription settings. In our reading, that means signals with different needs, such as a fast counter and a slow temperature, need separate adapter instances. The default serverQueueSize of 1 keeps only the latest sample per publishing interval, so a value that changes faster than 1000 ms loses the intermediate changes unless the queue size is raised. That is our inference from what the setting means, not a statement from HiveMQ.
The unchanged-values conflict. The adapter documentation says the OPC UA adapter “does not filter unchanged values”: every data notification the server sends is published, even if the value did not change. A HiveMQ community thread titled “OPC UA adapter updates only on data change” reports the opposite behaviour, and HiveMQ’s reply there says the adapter publishes MQTT messages for data changes detected on subscribed nodes. We could not settle which is right. Test it on a bench server with a constant value before you size traffic or a historian.
Changed-only is not uniform. Modbus, S7, ADS and BACnet default publishChangedDataOnly to true. MTConnect and Databases publish every interval, and so does the Simulation adapter. A consumer that assumes “only changes” will be wrong on some adapters.
Siemens S7: the PUT/GET requirement
HiveMQ’s documentation states the S7 adapter requires PUT/GET access enabled on the controller. The adapter reads S7-300, S7-400, S7-1200, S7-1500 and LOGO, on port 102 by default. HiveMQ’s release notes record S7 and ADS being added to the adapter catalog in Edge 2023.8 and promoted from alpha to general availability in 2023.9.
In our view, PUT/GET is a security decision, not a checkbox. It lets a remote partner read and write controller memory without the finer protections available on newer controllers. We did not read Siemens’ own guidance for this page, so we state this as our view. The practical answer is to decide it with whoever owns controller security, to restrict which hosts can reach port 102, and to keep Edge on a segment designed for it. See OT network segmentation in brownfield plants and IEC 62443. Where a controller offers OPC UA, compare that route on the same security terms.

EtherNet/IP, ADS and the rest
EtherNet/IP is by CIP address, not by tag name. The logical addressing adapter issues generic CIP Get_Attribute_Single and Set_Attribute_Single services to an address written @class/instance/attribute, on port 44818. HiveMQ’s documentation says it connects to any EtherNet/IP device that conforms to the Common Industrial Protocol (CIP), not only Rockwell Automation controllers. The data type defaults to SINT and the writeability defaults to read only, so every attribute needs its type and byte order set correctly. Whether Edge can read Logix symbolic tags by name is unconfirmed on the pages we read. For the Rockwell side, see connecting an Allen-Bradley PLC to Ignition for the alternative routes.
Beckhoff ADS reads by <program-name>.<variable-name> on port 48898. BACnet/IP shipped in 2024.8 as an early-access adapter, and HiveMQ’s 2026.16 notes say it ships with Edge, with unsigned integers now written as JSON numbers, which can break consumers that parse them as text. MTConnect was added in 2025.6.
Where it gets hard
- Tag count. We found no documented maximum. A forum user wrote in March 2024 that the OPC UA adapter stopped adding subscriptions after the first 100. HiveMQ asked in June 2024 for the latest version, configuration and logs, and the thread shows no answer. We treat the report as unconfirmed and unresolved. HiveMQ’s 2026.16 notes list, as a known limitation, at most 30 to 40 protocol adapters with southbound mappings in one Edge, which is a different limit.
- Data types and word order. Modbus returns 16-bit values and has no byte-order setting, only
flipRegisters. A 32-bit float that reads as nonsense is usually word order. - Quality. The OPC UA payload carries
statusCodewhen metadata is present, so a consumer can see a bad-quality value only if that metadata is enabled. - Reconnects. A HiveMQ knowledge-base article is titled “Data Flow Stops After Reconnect”. We could not read its body, and search summaries disagree on the fixed version, so we name no version.
- Change. Adapter behaviour changes between releases. Pin the Edge version and retest after each upgrade.
Limits and open questions
Licence tier for MTConnect and Databases; whether Edge reads Logix symbolic tags; the real tag ceiling; and the unchanged-values behaviour are all unresolved above. HiveMQ’s adapter page is very long and parts of it were read only in summary, so some adapters or settings may sit in the unread parts. We found no PROFINET, Mitsubishi or Omron FINS adapter; treat those as unconfirmed absences.
Up one level: HiveMQ Edge. Across to a sibling: edge-to-cloud bridging. The vendor view is at the HiveMQ hub.
Frequently asked questions
Which PLCs can HiveMQ Edge read?
HiveMQ's documentation lists Siemens S7 (S7-300, S7-400, S7-1200, S7-1500 and LOGO), Beckhoff ADS, Modbus TCP, and EtherNet/IP by CIP class, instance and attribute address, plus OPC UA for any controller that exposes a server. We found no adapter for PROFINET and no native Rockwell Automation tag-name adapter on the pages we read.
Can HiveMQ Edge write to a PLC?
HiveMQ's Edge overview says southbound MQTT to OT is a commercial feature, currently for the OPC UA adapter only. The S7, ADS, Modbus, BACnet, MTConnect and Databases adapters are documented as read-only toward MQTT. The adapter page documents write options for EtherNet/IP logical addressing as well, which the overview does not mention, so confirm with HiveMQ how that interacts with the licence.
How often does HiveMQ Edge poll a PLC?
The polled adapters (S7, ADS, Modbus, BACnet, EtherNet/IP, MTConnect and Databases) default to a 1000 ms polling interval in HiveMQ's documentation, and the interval accepts values as low as 1 ms. OPC UA works differently: it creates a server subscription with a publishing interval that defaults to 1000 ms.
Does the HiveMQ Edge S7 adapter need PUT/GET enabled?
Yes. HiveMQ's documentation states the controller must have PUT/GET access enabled for the S7 adapter. We did not read Siemens' own guidance for this page. In our view it is a security decision for the controller, to be made with the OT security owner and compensated with network segmentation.
Is there a limit on tags per HiveMQ Edge adapter?
We found no documented maximum. A forum user reported in March 2024 that the OPC UA adapter stopped adding subscriptions after the first 100, and HiveMQ asked for logs without a published answer. Treat that report as unconfirmed, and load-test your own tag count. HiveMQ's 2026.16 notes list a known limitation of at most 30 to 40 protocol adapters with southbound mappings in one Edge.
References and further reading
- HiveMQ Edge protocol adapters · HiveMQSettings, defaults and directions for every adapter.
- HiveMQ Edge documentation · HiveMQThe open-source and commercial feature lists.
- HiveMQ Edge 2026.16 release notes · HiveMQ
- HiveMQ Edge: OPC UA protocol adapter max subscriptions · HiveMQ CommunityThe unanswered report discussed in the page.
- HiveMQ Edge: OPC UA adapter updates only on data change · HiveMQ CommunityThe forum side of the unchanged-values conflict.
- HiveMQ Edge OPC-UA: Data Flow Stops After Reconnect · HiveMQ Knowledge Base