How do I test a BACnet device without a BMS?

Updated 18 September 2026

Short answer

You do not need the building management system, a laptop, or the integrator to prove a BACnet device is alive and working. Any BACnet client on the same network can do it — including Easy BACnet on a phone. Join the network, run a Who-Is, and if the device answers with its name and Device ID it is online and speaking BACnet. Read its points to confirm the sensors report sane values, and — carefully — command a commandable point to confirm it responds. That is a full functional check with nothing but a phone.

Why you can do this without the BMS

BACnet has no login and no single master. Any device on the network can ask any other device questions, which is exactly what a BMS does — it is just a BACnet client with a nice front end. So a handheld client can perform the same discovery, reads and writes the BMS would, which makes a phone ideal for commissioning checks, startup verification, and “is this new controller actually talking?” before the BMS is even connected.

The test, step by step

1. Prove it is on the network (discovery)

Run a scan. If the device answers a Who-Is with its name, Device ID and IP, it is powered, on the network, and speaking BACnet/IP — three things confirmed at once. If it does not answer, that is a network or address problem, not necessarily a dead device: see why does my BACnet device show offline?

2. Prove the sensors read (inputs)

Open the device and read its input points. Do the values make physical sense — a room temperature near room temperature, a damper position between 0 and 100%? A point flagged fault or unreliable, or reading an impossible number, points at a sensor or wiring problem on the equipment. This alone catches a lot of commissioning faults.

3. Prove it responds to control (outputs)

On a commandable output, write a value at a manual priority and watch what happens — a valve drives, a fan starts, the feedback point moves. Then release it so you do not leave an override behind. This confirms the whole chain: the controller received the command and the actuator obeyed. Do this only where it is safe to move the equipment, and always release afterwards — see how to write to a BACnet point and priority and stuck overrides.

What a phone test can and cannot tell you

Can: confirm the device is online, that points read sane values, that outputs respond to commands, and capture the whole lot as a CSV for a record.
Cannot: reach devices on another subnet without a BBMD, or plug straight into an MS/TP trunk — those go through a router. And it does not replace the BMS's scheduling and trending; it proves the device works, not that the whole sequence is programmed.

This is the field-tech use Easy BACnet is built for: walk up to a new or suspect controller with a phone, prove in two minutes whether it is the device, the network or the program at fault, and leave a CSV behind — no BMS access required.