Easy BACnet
What is a BACnet Device ID, and why do duplicates matter?
Updated 11 October 2026
The Device ID, properly the device instance number, is a number from 0 to 4194302 that identifies one controller across the whole BACnet internetwork, not just its own subnet or MS/TP trunk. Integrators and head-ends map devices by this number rather than by name or IP, so it has to be unique. Two devices with the same ID cause confusing, intermittent problems. The value 4194303 is reserved as a wildcard and isn't a valid Device ID.
Why it exists
IP addresses change, names get edited, and MS/TP devices have no IP address of their own. The device instance is the identifier that stays put across the whole internetwork, including controllers behind routers on RS-485 trunks. When a vendor asks for your BACnet information, this is the number they're after.
Every device reports its Device ID when it answers a scan, which is why a scan list shows it next to each device's name and IP address.
Why duplicates break things
The standard requires every Device ID on the internetwork to be unique. When two controllers share one:
- Discovery gets unpredictable. The head-end binds the ID to whichever device answered, and it may not be the same one next time.
- An integration mapped to that ID can read from, or write to, the wrong controller without any error.
- One device can seem to drop off the network, or the two trade places.
Duplicates usually come from controllers loaded from the same template or backup, or a replacement controller that went in with the old unit's settings on another trunk. Check before you hand a points list to anyone. Easy BACnet flags any instance it sees at two different addresses as a duplicate ID.
4194303 and factory defaults
4194303 (0x3FFFFF, the largest 22-bit number) is reserved: a client uses it as a wildcard meaning “whichever device I'm talking to”, and a real device may not use it as its own ID. Factory defaults vary by vendor. Some ship as 0 or 1, some derive the ID from the MAC address or a serial number, and some MS/TP devices default to a number tied to their MAC. That's why a new controller can collide with another out of the box. If a device does report 4194303, it hasn't been set up properly; Easy BACnet marks it needs commissioning.
Choosing numbers
Most integrators use a scheme that encodes something useful. A common one for MS/TP is network number plus MAC: device 14 on network 201 becomes 20114. Others use building and floor, such as 21001–21099 for building 2, floor 1. Any scheme works if it's written down and actually unique. The sites that hurt are the ones where every contractor started at 1.
Check it on your own network. Easy BACnet is a free Android app that finds BACnet IP devices and reads their points in a couple of taps.
Get it on Google Play