Why does my BACnet device show offline?

Q: Why does my BACnet device show offline?

“Offline” in BACnet almost always means I stopped hearing from it, not it is broken. The usual causes, most common first: your phone or client is on the wrong subnet so the broadcast never reaches it, a Wi-Fi access point is dropping the broadcast packets, a firewall is blocking UDP 47808, the device shares a Device ID or network number with another device, or it genuinely lost power or its network link. A device showing a fault flag is a different thing from one showing offline — worth separating first.

Updated 18 September 2026

Short answer

“Offline” in BACnet almost always means I stopped hearing from it, not it is broken. The usual causes, most common first: your phone or client is on the wrong subnet so the broadcast never reaches it, a Wi-Fi access point is dropping the broadcast packets, a firewall is blocking UDP 47808, the device shares a Device ID or network number with another device, or it genuinely lost power or its network link. A device showing a fault flag is a different thing from one showing offline — worth separating first.

Offline versus fault — not the same

First separate two things people both call “offline”. A device that does not answer discovery or reads at all is a communication problem — the causes below. A device that answers fine but whose points show a fault or unreliable flag is a health problem on the equipment — a failed sensor, not a network fault. If you can read the device but a point looks wrong, that is fault, not offline.

The causes of a truly unreachable device

1. Wrong subnet (by far the most common)

Controls equipment usually sits on its own subnet or VLAN. If your phone is on guest Wi-Fi, the office network, or a different scope, the broadcast that finds BACnet devices never reaches them and everything looks offline. See what is a subnet, and why doesn't the switch give me the right one?

2. Dropped broadcast packets

BACnet discovery is a broadcast, and Wi-Fi access points drop broadcast packets freely under load. A device that appears one scan and vanishes the next, or shows offline intermittently, is often this. Scanning repeatedly — which a good tool does automatically — works around it.

3. A firewall on UDP 47808

BACnet/IP lives on UDP 47808 (0xBAC0). A software firewall, antivirus, or a locked-down switch dropping that port makes devices unreachable even on the right subnet. See what port does BACnet use?

4. A duplicate Device ID or network number

Two devices sharing a Device ID, or a duplicated network number, makes devices appear and disappear or answer for each other — a classic “it is online, no it is not” symptom. If it started when equipment was added, suspect this. See BACnet Device IDs explained.

5. It is on another subnet with no BBMD

Broadcasts do not cross a router by themselves. A device on a different segment needs a BBMD or a directed add-by-IP, or it will always look absent from your side.

6. It really is down

Lost power, a pulled network cable, a dead MS/TP trunk behind its router. Once the five above are ruled out, this is what is left — and now you know to look at the equipment, not the network.

A quick order to check in

Confirm your phone's IP is on the same subnet as the controls.
Scan again a couple of times — dropped broadcasts hide devices.
Try adding the device directly by IP; if that works, it is a broadcast/subnet problem, not a dead device.
Check for duplicate IDs in what you did find.
Ask whoever runs the network about UDP 47808 and VLANs.

Easy BACnet re-broadcasts discovery for up to about forty-five seconds to beat dropped packets, shows your phone's own subnet when a scan is empty, and flags duplicate Device IDs when it sees them — the three things behind most “offline” reports.