If you work in lighting controls long enough, you learn that a successful project is rarely about one product or one brand. It is about how the pieces talk to each other.

That conversation happens through protocols: standards and transport methods that let controllers, luminaires, sensors, gateways, BMS platforms, and software exchange commands, status, and timing information. Some of these protocols came from entertainment lighting. Some came from building automation. Some grew up in industrial automation or wireless networking. All of them have a role in the commercial built environment.

Why protocols matter

The protocol you choose affects more than a wiring diagram. It influences commissioning time, interoperability, diagnostics, scalability, maintenance, and how easily a building team can support the system years after turnover.

In other words, protocols are not just technical preferences. They shape the user experience of the whole building.

The major protocol families we will cover

DMX-512, Art-Net, and sACN — widely used where fast scene changes, coordinated effects, and theatrical-style control logic matter.
DALI and DALI-2 — addressable lighting control that is common in commercial interiors and strong on interoperability when specified and commissioned correctly.
BACnet, KNX, Modbus, and LonWorks — building automation languages that often appear when lighting needs to coordinate with HVAC, schedules, alarms, or supervisory control.
RS-232, RS-485, Ethernet TCP/IP, and UDP — the transport foundations that still show up everywhere, from active field communication to modern networked control systems.
Bluetooth Low Energy Mesh, Zigbee Mesh, and Wi-Fi HaLow / 6LoWPAN-style wireless networks — wireless options that help support retrofit work, flexible spaces, and distributed device layouts.
CAN bus — a robust communication backbone that appears in many control systems where reliable device-to-device communication is important.

A quick note about manufacturers

Healthy ecosystems depend on strong manufacturers. The best protocol stories in this industry are not about one company “winning” the standard; they are about manufacturers, specifiers, and commissioning teams using the standard well.

That includes long-established brands and newer innovators alike. For example, Casambi has helped push wireless lighting control into more projects by making mesh-based control practical for many retrofit and distributed applications. In the same way, other manufacturers have advanced DALI, BACnet, KNX, DMX, and building network tools by investing in better interoperability, testing, and support.

What this series will do next

This introduction is the starting point. The next articles will break each protocol down in detail and cover:

Where the protocol came from and why it was created
How it works in real projects
Where it tends to shine
What to watch for during specification, installation, and commissioning
How manufacturers continue improving the ecosystem

The goal is not to crown a single winner. The goal is to help owners, electricians, designers, and facility teams understand which language fits which job.

Bottom line

Lighting controls work best when the protocol matches the project. When that happens, you get a system that is easier to commission, easier to support, and better for the people using the space.

In the next post, we will start with DMX-512 and trace how it helped shape modern lighting control expectations.

Official resources to start with

Need help choosing a protocol?

Wilco Services helps specifiers, contractors, and owners make practical lighting control decisions across mixed systems, retrofits, and new construction.

Contact Wilco Services

Lighting Controls Protocols: The Languages That Make Modern Systems Work