UMA Mesh. The integration backbone.

The connectivity layer between every device on the floor and the platform that reasons over them. BACnet, Modbus, MQTT, LoRaWAN, EnOcean and vendor APIs. One model out, your kit in, no rip-and-replace.

Book a Demo Watch the demo

LIVE · INTERACTIVE DEMO

Click anywhere. It's the real UMA Vision. No login required

What UMA Mesh does

The middleware that quietly does the hard part.

Buildings already have data. UMA Mesh is the layer that bridges every system, normalises every payload, and hands UMA Vision one consistent shape to reason over. The platform you see is only as strong as the mesh underneath.

01
One model out

Every device, regardless of vendor, lands in UMA as the same shape of telemetry. Booking, analytics and Vision read from one schema.
02
Your kit in

BACnet BMS, Modbus meters, MQTT brokers, LoRaWAN networks, REST APIs and vendor SDKs. Bring what you have.
03
Managed not bolted-on

Polling schedules, decoders, credentials and gateways are all UMA-operated, with audit and observability built in.
04
Open by design

Webhook out, REST in, OpenAPI spec available. The middleware layer behaves like infrastructure, not a black box.

Mesh → Vision · Automation

Build the rule once. Read the result everywhere.

Mesh hands Vision a normalised feed. Rules live next to the data they act on. The same numbers turn up in the analytics dashboard the next morning, with the lift attributed.

Rule engine · Live

A visual rule builder over your live mesh feed.

Pick the sensor, pick the condition, pick the action. Mesh fans the trigger out to the BMS, the HVAC controller or the access system. Analytics gets the receipt so the savings are measurable.

See Workplace Automation

Protocol coverage

The protocols that actually run buildings.

First-class support for the protocols you find in nine commercial estates out of ten. Bespoke decoders for the long tail, scoped project by project.

BACnet/IP

Object discovery, COV subscriptions, seven-day historical pulls. Read-only by default, write-back on request with controls.

BACnet/MSTP

Serial trunks bridged through a Mesh gateway so the BMS riser does not need an IP rework to share data.

Modbus TCP

Polling against Modbus registers for power, HVAC and metering. Configurable scan rates, scaled values, unit conversion in-flight.

Modbus RTU

Same as TCP, over RS-485. Mapped into the UMA model the moment values land.

MQTT

Subscribe to topics on your existing broker or use UMA-hosted. TLS, per-tenant credentials, topic-level ACLs.

LoRaWAN

ChirpStack, TTN, AWS or private network servers. Per-device decoders mean any LoRaWAN sensor reads the same.

EnOcean

Energy-harvesting wireless. Gateway speaks MQTT or BACnet to Mesh. No batteries, no recabling.

Zigbee

Coordinator-managed deployments and ZigBee-over-IP gateways supported via Mesh adapters.

REST + GraphQL

Pre-built connectors for major vendor SDKs, plus generic REST and GraphQL adapters for the long tail.

What Mesh connects

Six device families, one feed.

Whatever was on the wall before UMA arrived, the mesh meets it where it is. No rip-and-replace, no parallel cabling. The kit you bought stays useful.

BMS and HVAC

JCI, Trend, Tridium, Siemens Desigo, Honeywell. Setpoints, status, schedule and energy in one feed.

Sensors

Milesight, Pressac, Kontakt, EnOcean, Disruptive, Terabee, Quandify, Netvox and any standards-compliant LoRaWAN.

Network kit

Cisco Meraki MR/MV/MX, Cisco Spaces, Catalyst APs and the wider Cisco IoT footprint.

Video and collab

Webex Control Hub, Cisco Spaces telemetry, Neat Pulse, Logitech Sync, Poly Lens, Yealink DMP, Jabra Xpress.

Access and security

Salto KS, HID Origo, Paxton, Vecos lockers. Door state, badge swipes and locker availability painted on the plan.

Energy and water

BMS submetering, Quandify ultrasonic water, EnOcean energy harvesters, LoRaWAN meters. Live and aggregated.

Mesh → Vision · HVAC

Heat the rooms that are actually booked.

Mesh stitches the BMS, the calendar and the occupancy sensors into one feed. Heating follows the booking, not the schedule. The savings show up in the reservation breakdown and the energy line in Analytics.

HVAC · Booking-aware

Live device control, fed by the same model the analytics read.

Per-room setpoints, schedules and modes are surfaced in Mesh and acted on through whichever BMS or controller is wired up. The reservation feed tells you which rooms drove the load, so the budget conversation is about evidence, not opinions.

See ESG outcomes

How Mesh works

Gateway. Broker. Vision. Four moving parts.

No magic, no black box. Mesh is a small set of well-understood components, each documented, each instrumented, each replaceable.

01 Edge gateway

Listens on the protocol the device already speaks (LoRaWAN, BACnet, Modbus, MQTT). One physical box per site, or virtual where the BMS is IP-native.
02 Mesh broker

Normalises every payload into the UMA telemetry schema. Per-device decoders, credentials, polling schedules: all UMA-managed.
03 Identity and audit

Each tenant’s data isolated. Per-device audit log, per-payload integrity. Vision only reads what is published.
04 UMA Vision

Booking, occupancy, IAQ, energy, ESG, automation rules. One model, every signal the building can produce, painted on the plan.

Mesh → Vision · Flows

Visual flows that move signal into decisions.

Drag sensors, decoders, switches and actions onto a canvas. Deploy. Mesh fans the rule out to every gateway in scope. Analytics surfaces the outcome so the next iteration is informed.

Flow builder · Deployable

From sensor input to room setpoint, all in one canvas.

Inputs → decoder → logic → action. Push deploy and the rule runs from the next packet. Energy saved per zone, per day, lands in the analytics view alongside the bookings that drove the demand.