Need to connect SNMP and BACnet? The Weble WBox routes SNMP BACnet natively: one gateway speaks both protocols and maps data points in real time — no PC, no middleware, no cloud dependency.

SNMP→WBoxgateway→BACnetOne WBox gateway · native conversion · no PC

The protocols

SNMP

SNMP (v1, v2c, v3) monitors network and technical infrastructure — UPS units, switches, servers, IP sensors — by reading OIDs and receiving traps.

SNMP driver →

BACnet

BACnet (BACnet/IP, MS/TP) is the standard for building management systems and HVAC supervision.

BACnet driver →

Typical use case

The server room is part of the building, but its equipment speaks IT protocols: UPS units, precision cooling, network switches — all SNMP. The WBox brings them into the BACnet BMS: battery charge, cold-aisle temperature and port states become BACnet points, so facility management supervises the technical room with the same alarms and trends as the rest of the building.

Example deployment

Typical scenario Server room watched by the BMS UPS units, precision cooling and network switches expose their state over SNMP. The WBox polls the OIDs (v1, v2c or v3), receives traps (LinkDown, power failure) and publishes everything as BACnet objects: the building BMS monitors the server room like the rest of the plant. Technical documentation →

How the WBox bridges SNMP and BACnet

The SNMP driver polls each device's OIDs (v1, v2c or v3) and listens for traps; the values are exposed as BACnet Analog and Binary objects with COV notifications to the head-end. The integration is read-only by design — the driver does not issue SNMP SET — which is exactly what supervision needs: full visibility of the IT infrastructure with no risk of writing to it.

Example mapping

A server-room example:

  • OID 1.3.6.1.2.1.33.1.2.4 (UPS battery charge) → BACnet Analog Value 2 (%)
  • OID 1.3.6.1.2.1.1.3 (sysUpTime) → BACnet Analog Value 8
  • Trap linkDown (switch port) → BACnet Binary Value 3 (alarm)

Capacity & limits

  • SNMP — SNMP polls any number of IP agents (v1, v2c, v3) and receives traps; the driver is read-only — it never writes to your equipment.
  • BACnet — BACnet/IP scales to large object counts; BACnet MS/TP carries up to 127 master nodes per segment.

On the WBox, a driver licence enables the whole protocol — there is no artificial per-point tier to unlock. Capacity scales with the gateway model, from the compact S103 to the E413: you are bounded by the field bus, not by your licence.

Frequently asked questions

How do I connect SNMP and BACnet?

SNMP is the IP equipment monitoring protocol and BACnet is the building-management (BMS) protocol. A single WBox gateway runs the SNMP and BACnet drivers, speaks both protocols at once and maps the data points between them — no PC, no middleware, no cloud dependency.

Is the SNMP ⇄ BACnet bridge bidirectional?

Yes. The WBox reads and writes on both sides: a value or command on the SNMP side propagates to BACnet, and vice-versa.

Do I need a PC, a PLC or proprietary hardware?

No. The SNMP and BACnet drivers are licence-activated on one WBox — no gateway PC, no intermediate PLC and no proprietary hardware.

Which WBox model do I need?

Any WBox with the SNMP and BACnet driver licences. The online configurator recommends the right model from your interfaces and point count.

What you need

One WBox gateway with these two driver licences:

SNMP SNMP Driver licence 100.00 CHF BACnet BACnet Driver licence 100.00 CHF

Route SNMP BACnet on your project

Find the right WBox gateway for your installation, or get in touch to validate your case.

Configure my gateway

Related routes

← All routes