HiveMQ Edge 2026.11 is Released

What's New in HiveMQ Edge 2026.11

HiveMQ Edge 2026.11 introduces a second EtherNet/IP protocol adapter — EtherNet/IP – Logical Addressing — extending EtherNet/IP connectivity beyond Rockwell controllers to any device that follows the Common Industrial Protocol (CIP) object model, with both read and write support. The release also folds in a round of library upgrades and a few targeted fixes.

EtherNet/IP Logical Addressing Adapter

What It Is

The new EtherNet/IP – Logical Addressing adapter connects HiveMQ Edge to any EtherNet/IP device that conforms to the Common Industrial Protocol (CIP). Where the existing EtherNet/IP adapter reaches Rockwell/Allen-Bradley controllers by symbolic Controller Tag name, the new adapter addresses data by its numeric position in the CIP object model — a @class/instance/attribute path. Because logical addressing is part of the CIP standard rather than a Rockwell extension, the adapter is vendor-neutral: it works with any CIP-conformant device, not only ControlLogix and CompactLogix PLCs.

The adapter supports three capabilities:

• Read (northbound): poll CIP attributes and publish the resulting datapoints as MQTT messages.
• Write (southbound): write values received as MQTT messages back to CIP attributes.
• Combine: use the datapoints the adapter publishes as inputs to data combiners.

How It Works

You configure each tag with a CIP logical address and a CIP data type:

    <tag>
    <name>temperature</name>
    <definition>
        <address>@4/100/3</address>
        <dataType>INT</dataType>
        <readWrite>READ_ONLY</readWrite>
    </definition>
</tag>
  

A generic CIP device does not describe its own data — it hands back a block of bytes. The adapter reads those bytes and interprets them according to the data type you configured on the tag. You therefore supply the byte layout yourself, from the device's documentation or its EDS file.

A single CIP attribute often packs several fields into one block of bytes. You map each field to its own tag by giving the tag a batchByteIndex — the byte offset of that field within the attribute — and, for a boolean packed into a single bit, a batchBitIndex. A COMPOSITE tag then aggregates its sibling tags at the same address into one structured message: instead of publishing each field separately, the adapter emits a single JSON object whose keys are the field names. This turns a flat block of bytes into a structure that mirrors the device's data.

For writing, two modes control how a write covers an attribute:

• PARTIAL_WRITE (default): a read-modify-write sequence that overlays the supplied tag values and preserves all unmapped bytes.
• COMPLETE_WRITE: replaces the whole attribute directly, for when the configured tags span the entire attribute.

How It Helps

• Reach non-Rockwell CIP devices. Any EtherNet/IP device that follows the CIP object model is now addressable from HiveMQ Edge, not only Rockwell PLCs.
• Full bidirectional integration. Read process data northbound and write setpoints and commands southbound.
• Structure over raw bytes. Map the individual fields packed into a CIP attribute to named tags, and publish them together as one structured message.
• Pick the right adapter per device. The two EtherNet/IP adapters coexist — symbolic addressing for named Controller Tags, logical addressing for the CIP object model — so each configuration stays clean and matched to the device.

The adapter is fully documented on the public protocol adapters page, including the addressing model, batch and composite tags, both write modes, the supported CIP types, and a comparison of the two EtherNet/IP adapters.

Additional Improvements

Improvements

• Various library upgrades. This release incorporates a round of dependency updates across the Edge codebase (backend and frontend), including security-relevant bumps identified by automated scanning. Keeping the dependency tree current reduces exposure to known vulnerabilities in transitive libraries.

Bug Fixes

• Corrected an off-by-one in the Simulation adapter's random LONG generation. The configured maximum value was inclusive when it should have been exclusive, so a configured max could occasionally be produced as an actual value; the range is now respected.

Get Started Today

Use the download link to get HiveMQ Edge 2026.11, or find us on GitHub and Docker:

Get started by running

    docker run --name hivemq-edge --pull=always -d -p 1883:1883 -p 8080:8080 hivemq/hivemq-edge
  

Or clone our repository

    git clone git@github.com:hivemq/hivemq-edge.git
  

You may also try out our Helm Chart

    helm repo add hivemq https://hivemq.github.io/helm-charts && helm repo update