The EG71 solves a common integration headache: modern buildings run a mix of wired and wireless protocols, and getting them talking to one system usually means multiple gateways, converters and cabling runs.

EG71 handles it with one device. It brings LoRaWAN®, Modbus RTU/TCP, BACnet/IP, KNX and M-Bus onto a single gateway, so field devices across HVAC, energy monitoring, lighting and building automation systems report through one point of integration.

Processing happens locally. Built-in edge computing runs configurable logic on-site, so control decisions don’t depend on a live cloud connection, and response times stay fast even if the network drops out.

Connectivity is flexible by design. Ethernet, 4G, RS485 and digital I/O interfaces mean EG71 connects to a wide range of field devices, whether you’re retrofitting an existing building or specifying for new construction.

Once configured, EG71 connects building data to the cloud for remote monitoring and management, giving facility teams visibility without needing to be on-site.

Backed by OneTemp’s local expertise, EG71 is a practical, scalable option for integrators and building managers who need multi-protocol reliability without adding hardware complexity.

1: When powered via USB, M-BUS and Universal Inputs will not work properly.

EG71 pairs well with OneTemp IoT Cloud for teams who want local support alongside their monitoring platform. OneTemp IoT Cloud gives you real-time dashboards, automated alerts and long-term data logging, backed by the same team supplying the hardware. There’s no gap between vendor and platform support.

The platform includes pre-configured payload formatters for Milesight devices, so setup is fast, and it scales from a handful of sensors to a multi-site network without switching systems.

Explore OneTemp IoT Cloud →

What’s the biggest value of the EG71 for building integrators?

The EG71 cuts hardware and integration costs by replacing several point solutions with one gateway. Instead of running separate protocol converters, I/O modules and a LoRaWAN gateway, integrators get all three in a single device.

• Direct wired protocol access: BACnet, Modbus and KNX devices connect without extra converters
• Built-in I/O: digital and analog signals connect directly, no expansion modules needed
• Wireless integration: LoRaWAN® sensors run through the same gateway
• Local logic and control: edge processing handles automation and alarm logic on-site
• Flexible forwarding: data reaches BMS, SCADA or cloud platforms via MQTT, HTTP, BACnet or Modbus

For OneTemp customers, that means fewer devices on-site, simpler wiring and commissioning, and one local point of contact for support and stock.

Which building protocols does the EG71 support?

• Wired: BACnet/IP, BACnet MS/TP, Modbus TCP, Modbus RTU, KNX TP, and M-Bus (M-Bus support is under development, contact OneTemp for current status)
• Wireless connectivity: built-in LoRaWAN® network server for direct sensor management
• Northbound data forwarding: MQTT and HTTP for active data pushing, plus BACnet/IP and Modbus TCP for BMS or SCADA polling

This lets integrators connect wired equipment and wireless sensors through one gateway, process data locally, and forward it to whichever system needs it.

How is the EG71 different from a standard protocol converter or LoRaWAN gateway?

Most protocol converters handle one translation job. Most LoRaWAN gateways just connect sensors to a network server. The EG71 does both, plus local processing, remote management and developer tools, in one edge device. Fewer integration layers between field devices and your BMS or cloud platform, less hardware to spec, wire and maintain.

Can the EG71 replace Niagara or JACE controllers?

Depends on the project. For small to mid-sized jobs focused on protocol conversion, data aggregation and edge integration, the EG71 is a genuine alternative, and a simpler, lower cost one.

For large-scale BMS projects built around Niagara’s native controller libraries or established JACE workflows, it won’t cover the full function set. In those cases, the EG71 works best as an edge integration layer: connecting field devices and forwarding data to Niagara, your BMS, SCADA or cloud platform, rather than replacing the controller outright.

Is there an API to read all EG71 data points?

Not a standard RESTful API for full data point access. Most integrations instead use:

• MQTT or HTTP for active forwarding
• BACnet/IP or Modbus TCP for BMS/SCADA polling
• Node-RED for I/O control logic

If your project needs direct API level access, get in touch and we’ll confirm the current options with Milesight.

What certifications does the EG71 have?

CE, CE RED and FCC. BTL and KNX certification haven’t been obtained yet. If you need security testing documentation or have project-specific compliance requirements, contact OneTemp and we’ll source the latest from Milesight.

Can the EG71 run a lightweight mini BMS or custom dashboard?

Yes. It collects data from wired and LoRaWAN® devices, runs local logic through Node-RED or Python, and forwards it to an HMI, dashboard or upper-level platform via MQTT or HTTP. It also supports Docker for local application deployment.

The EG71 doesn’t include a visualisation front end itself, so dashboarding needs to sit in an upper-level platform such as OneTemp IoT Cloud, a BMS, or a custom application.

Can the EG71 be used for HVAC integration and control?

Yes, provided the HVAC equipment has a compatible communication interface:

• BACnet, common in building automation systems
• Modbus, often used for inverters, heat pumps and controllers
• I/O signals such as dry contacts and analog inputs
• MQTT/HTTP for compatible smart HVAC devices

For VRV/VRF or split systems, check compatibility first. These often run vendor-specific protocols, so confirm whether your equipment supports BACnet, Modbus, I/O control or a compatible open API before specifying.