Building Automation System Not Communicating

Likely causes

These categories help organize the diagnostic process; they are not a remote diagnosis.

• Power, network, wiring, termination, addressing, gateway, switch, or controller faults
• Protocol, configuration, software, certificate, credential, licensing, or time-sync issues
• Failed device, network storm, damaged segment, cybersecurity change, or unsupported legacy layer

Safe facility observations

Facility staff may record alarm text, thermostat or BAS display status, affected areas, time of onset, visible water or ice from a safe location, and unusual sound or odor. Do not open energized panels, reset a repeatedly tripping breaker, bypass safeties, force controls, handle refrigerant, work on combustion equipment, or enter pressure systems.

• Record the first failure time, affected devices, alarms, and recent IT or power changes
• Preserve screenshots and note whether local equipment still operates
• Do not reboot infrastructure repeatedly or alter addresses, credentials, or terminations

Professional diagnostic process

Diagnosis isolates supervisory, IP, gateway, field bus, power, controller, and device layers while coordinating IT ownership, credentials, backups, cybersecurity, and mechanical fallback operation.

Equipment commonly involved

The fault can originate in the primary equipment or a connected system.

• BAS server or cloud interface
• Network controllers and gateways
• Field controllers and sensors
• Switches, cabling, and power supplies

Risks of delay

Loss of visibility can hide alarms, leave schedules or overrides active, disable optimization, and increase comfort, freeze, process, or equipment risk.

Repair considerations

Restore the failed layer, preserve configuration, verify time and trends, clear inappropriate overrides, confirm alarms and commands, and test mechanical response.

Replacement considerations

Modernization should define points, sequences, protocols, cybersecurity, ownership, backups, graphics, training, acceptance tests, phasing, and legacy integration.

Related maintenance

Maintain backups, credentials, inventories, drawings, software and license status, network health, alarms, trends, schedules, time sync, and controller condition.

Safety notice

This guide is educational and is not a substitute for on-site diagnosis. Follow facility safety procedures and applicable code. If there is smoke, fire, suspected gas, exposed electrical damage, a significant refrigerant release, pressure hazard, or an immediate life-safety concern, evacuate or isolate the area as appropriate and contact emergency or qualified response personnel.