How to find and fix Unresponsive Devices

Visual BACnet finding Unresponsive Devices
Diving into the common causes of Unresponsive Devices, and how to resolve them on your BACnet network

Unresponsive Devices can cause a lot of unnecessary traffic on an Operational Technology network, but it can be difficult to pinpoint exactly what’s causing the problem. Unresponsive Devices could be caused by a misconfiguration, a physical issue, or a combination of the two. 

On our 10-Minute Webinar, we dug into top tips for finding and fixing Unresponsive Devices. Find out what usually causes these issues, and how you can resolve them. 

What is an Unresponsive Device? As the name implies, it’s a device that doesn’t respond to requests or messages that other devices send it. In this example, a source (represented by the computer) is sending a Who-Is message to device 249. This device is unresponsive, though, so it doesn’t send an I-Am message back to the source in reply. 

Responsive devices on a BACnet network

Unresponsive devices on a BACnet network

Depending on your configurations, the source might continue to send out Who-Is requests for device 249 until it gets a reply. That could be in perpetuity if you don’t fix the unresponsive device. 

The first question you need to ask is: “Should device 249 be on the network?”

Sometimes the answer is a simple no. Maybe you know that all your device IDs have a six-digit code, so a three-digit code like 249 shouldn’t be on the network at all. If this is the case, you’re likely dealing with a Phantom Device. 

Other times, the issue is a bit more complicated than that. If you’re not sure whether this device should be on your network, you can go to your device list and check whether ID 249 has been assigned. If the device should be on your network, you could be dealing with either a Failed Device or a Path Failure. 

Phantom device on a BACnet network

Phantom Device

If you know for sure that device isn’t on the network, you have what’s referred to as a Phantom Device. In this scenario, the problem is actually with the source device. For some reason, the source thinks it needs to find device 249. 

There are a few things you can look at to troubleshoot this: first, is this source device programmed to look for device 249? Alternatively, is this source device receiving a message from another device that it’s supposed to route to 249? If so, you might need to capture from another location on your network to pinpoint that issue.

failed device on a bacnet network

Failed Device

If device 249 should be on the network and should be responding to Who-Is requests, you might have a failed device. This is a common issue that a lot of people have dealt with, and there are many potential causes. In this case, you want to go and troubleshoot the device itself. It could be a physical issue (maybe the cord accidentally got pulled), or a misconfiguration.

path failure on a bacnet network

Path Failure

Third and finally, you could be dealing with a Path Failure. This issue is much rarer and more complicated, so we recommend that you look at the first two causes first. 

It’s likely, based on how BACnet networks are often designed, that the Who-Is message request is actually being routed through a few different devices. It could be sent via a router, a gateway, or a series of different devices.

If the source and the device are both working as they should be, you’ll have to go through and troubleshoot the path that’s connecting them. Hopefully, if this is the case, you’ll see some different failures on the network that will help you identify the root cause. This is also where it’s very helpful to have a network diagram, so you can identify if there’s a common thread — like a router, or wiring — to the devices that are struggling to communicate.

Troubleshooting the path is challenging, but if you resolve what’s broken in the path then you might fix a few devices that are struggling to communicate.

Another way to identify the cause of an Unresponsive Device is to look at the number of sources that aren’t able to communicate with a specific device. 

If a device is being sent messages from many different sources, it’s quite likely that you’ve programmed all these source devices correctly, and you have a device on the other end that’s failed. 

On the flip side, if you have one querying device, it’s more likely that there was a misconfiguration on the source device. 

many sources help narrow down issue on a bacnet network unresponsive devices


That isn’t an infallible rule of thumb by any means, but it’s a great place to start if you have limited context. 

In theory Unresponsive Devices are quite simple: it just means that something, somewhere, is getting lost in translation. But if the device isn’t communicating on the network, you might not even know it’s supposed to be there. Fortunately, Visual BACnet highlights exactly which devices are unresponsive, and which devices are searching for them, so you can focus on fixing the issue. 

Recent Blog Posts

May 26, 2020 Vancouver, BC – Optigo Networks is pleased to welcome Joel Schuster to the company’s board of directors.

Every March for the last few years at Optigo, we’ve taken a moment to celebrate women in tech and building automation.

Information Technology (IT) and Operational Technology (OT) are different in a lot of ways, from their design to their maintenance workflows and more.

It’s super important to have unique Device IDs on your BACnet system, but duplicates are a very common problem. Unfortunately, you might not even realize you have duplicate IDs, with devices only responding periodically.

Recent Projects

Data center expansion with OTI and Optigo Connect


Stack Infrastructure is a portfolio of hyperscale computing data centers. OTI completed work on Phases I and II, and returned for the Phase III build-out of a 4-megawatt data hall and brand new central plant. The Optigo Connect network put in place in Phases I and II was expanded on this project. The team achieved quick roll-out of a large, multi-service redundant network using the Optigo OneView management interface. Going forward, the facility management team can use OneView to remotely monitor equipment, manage power usage, and meet up-time goals.

Optigo Connect MR Soluciones The Landmark


The Landmark is a sophisticated mixed-use high-rise in Mexico. The owners wanted to integrate all OT systems in the skyscraper, while maintaining separate networks for each application. The Landmark is the fourth joint project between Optigo Networks and MR Soluciones. Together, these companies provide robust services to meet any challenge.

Australian Bureau of Statistics at 45 Benjamin Way with Delta Building Automation


Delta Building Automation (Australia) had a big job renovating the Headquarters for the Australian Bureau of Statistics (ABS) at 45 Benjamin Way. The building owner wanted to improve the building’s energy use and increase their National Australian Built Environment Rating System (NABERS) score to more than 4.5 stars, out of a possible total of six. Securing the network both internally and externally was a big priority, as well.

Penn State University Optigo Networks Visual BACnet


When Tom Walker looked at Penn State University’s Navy Yard network, he saw huge issues. The system was busy and loud, to the point where the overrun network was bringing down the entire building. Because this was happening on the MS/TP network, pinpointing the problem would mean boots on the ground to segment and test the chain, piece by piece.

Penn State University Optigo Networks Visual BACnet


When Tom Walker first started working at Penn State University four years ago, there were a lot of network issues. Buildings were dropping offline. Broadcast traffic was pushing 90,000 packets per hour. Walker was on the phone almost every single night because devices were down or had to be reset.


Torre Manacar Mexico City Optigo Connect


When MR Soluciones began work on Torre Manacar, they knew they needed a flexible and scalable network infrastructure to support a wide array of integrated systems. Optigo Networks was a natural fit for the massive project, designing a robust network at a competitive cost.



Short Pump Town Center, an upscale retail center, underwent a complete renovation in 2014. The flexibility of Optigo Networks’ solution meant the retail center’s unknown final design was not a barrier to placing IP surveillance equipment in the field.



Optigo Networks connected New York-based Boulevard Mall’s security surveillance devices in December 2015, using a Passive Daisy Chain topology.

Visual BACnet tech support team


One tech support team at a manufacturer purchased an account with Visual BACnet in April 2017, for technical problems around the world.

Aster Conservatory Green Optigo Connect


The Aster Conservatory Green is a community comprising 352 residences across 24 low-rise buildings. The buildings use advanced surveillance and access control technology, including 40 HD video cameras and 60 FOB-access-tele-entry points for access control.