The DesignLights Consortium’s Networked Lighting Controls Technical Requirements V5.2 took effect on August 17, 2026. On its own terms, it’s a modest update. Two additions stand out: thermostat integration, which lets occupancy data from the lighting control system influence HVAC operation, and standardized configuration reporting under ANSI/NEMA C137.9, which gives utilities a consistent way to verify how a system was actually configured. Both remain reported capabilities rather than required ones. Cybersecurity requirements didn’t change.
What makes the update worth an executive’s attention is the direction it points, particularly when you read it alongside what one of North America’s largest lighting companies has already done. Effective March 26, 2025, Acuity Brands, Inc. became Acuity Inc. Its SEC filings now open by describing the company as a “market-leading industrial technology company” using technology to solve problems in “spaces, light, and more things to come.” Acuity still owns an enormous lighting business. It didn’t abandon lighting. But it deliberately stopped defining itself by lighting alone.
Read that next to V5.2, and the controls update gets more interesting. Lighting controls spent twenty years trying to become part of the lighting sale. Their future increasingly depends on becoming part of the building sale. The question for the lighting channel is how much of that value it intends to follow.
Lighting controls spent twenty years trying to get into the lighting sale. Their future depends on getting into the building sale.
What V5.2 Actually Changes
The DLC’s own research explains some of the logic behind the move. Earlier studies have consistently shown that networked lighting controls can produce meaningful lighting-energy savings, including in LED-to-LED upgrades. That opportunity remains. But in many mature LED markets, the next meaningful increment of savings may no longer come from the fixture alone — and V5.2 explicitly points toward HVAC.
The new requirements recognize systems capable of passing occupancy information to thermostats. That matters most in small and midsize commercial buildings that have programmable or smart thermostats but no full building automation system. Early results from the Northwest Energy Efficiency Alliance, cited in reporting on the DLC update, suggest that occupancy information from luminaire-level lighting controls can reduce cooling energy by as much as 11 percent and heating energy by as much as 21 percent in a well-maintained building. The DLC has described the broader working range for HVAC savings at approximately 8 to 21 percent.
The incentive infrastructure around networked lighting controls is already substantial. As of the V5.2 update, the Qualified Products List contained 96 NLC systems from 61 manufacturers, and the DLC said more than 100 utilities were using the QPL to determine incentive eligibility. More than 200 commercial lighting rebate programs are offering dedicated NLC incentives in 2026, according to BriteSwitch data reported by Lighting Controls Academy. The DLC says NLC incentives are available in 46 states and three Canadian provinces, with QPL listing required for eligibility in 31 of those markets.
Thermostat integration remains optional. But once utilities can measure additional HVAC savings from infrastructure already being installed as part of a lighting project, optional can become economically important fast.
Once a utility can measure HVAC savings from a sensor it already paid for, optional doesn’t stay optional for long.
Why Now, When the Ceiling Was Promised in 2010?
Experienced readers have heard the sensor-grid argument before. Enlighted was founded on the idea that sensors distributed through the lighting system could provide building-level intelligence. When Siemens acquired the company in 2018, the pitch included dense sensing capable of supporting lighting, HVAC, and broader building-management applications. It was hardly alone. Variations of that story were told across the industry for more than a decade, and for most of that time the lighting channel didn’t fundamentally change.
A few things are different now. Penetration is one of them. Only 4 percent of linear luminaires sold through Rhode Island Energy’s midstream program included luminaire-level lighting controls in 2022. In 2026, 75% do. That shouldn’t be mistaken for national penetration, but it shows what happens when product availability, incentives, and channel execution line up.
Verification matters too. C137.9 gives the market a standardized way to report how a controls system has actually been configured. Utilities are far more comfortable paying for savings they can document than for theoretical capability sitting unused in the ceiling.
And perhaps most importantly, the economics are changing. In 2010, the sensor grid was often a platform in search of a payer. In 2026, efficiency programs are increasingly paying for networked controls, and the DLC is building a framework for connecting that installed infrastructure to HVAC savings.
What the lighting system brings to that conversation is density. A luminaire-level system can place networked occupancy sensing throughout a building at a resolution that conventional zone-level HVAC controls typically don’t match. That creates information with potential value beyond illumination, and that’s where the commercial question gets more interesting. Illumination is priced on a multiplier, quoted through the channel, and defended against the spec flip at buyout. The occupancy information sitting above the ceiling isn’t priced into the traditional lighting-channel commission structure at all. If that information starts influencing HVAC schedules, space utilization, building operations, or other services, the value is no longer confined to the fixture transaction.
Who gets paid for the rest?
In 2010 the sensor grid was a platform in search of a payer. In 2026, the payer is the efficiency program, and it has written down what it will pay for.
Who Owns the Controls Conversation?
There’s no single answer. Depending on the building and the project, the lighting rep, electrical contractor, distributor, BAS contractor, mechanical contractor, or systems integrator can all plausibly own part of the controls scope. The industry’s own guidance reflects that fragmentation: startup, programming, integration, commissioning, and acceptance responsibilities can move among parties depending on how the project is written and purchased. The problem isn’t that multiple parties are involved. The problem is what happens when everyone is involved, and nobody clearly owns the outcome.
A 2017 Pacific Northwest National Laboratory study for the U.S. Department of Energy looked at controls performance in two dozen newly built commercial buildings in the Pacific Northwest and Mountain regions, and separately interviewed ten experienced commissioning agents. Six of those ten said energy-code compliance verification wasn’t part of their scope. The study also documented shortcomings in design documentation, configuration, and execution of required control sequences.
It went a step further and put a rough price on the gap: by the report’s own estimate, lost energy cost savings from controls that were installed but not configured as designed averaged $12,025 per building per year on the HVAC measures and $570 per building per year on the lighting measures. The study is nearly a decade old, and its sample shouldn’t be used to estimate today’s failure rate. What remains relevant is the failure mechanism, and where the money sits when it fails. The equipment may be installed correctly, and the intended sequence may be in the design documents, yet the building can still fail to deliver the intended outcome if nobody clearly owns the last mile from installation to operation.
That’s a familiar problem in this industry. It’s the specification problem described in Specification Erosion, in a slightly different form. A specification that allows too many products to become functionally equivalent can erode at buyout. A controls scope that allows too many parties to assume someone else owns the outcome can erode at commissioning.
Ownership differs dramatically by building type, and that distinction matters. On a large specification project with an established BAS, the lighting rep may own the lighting-controls submittal, startup, and warranty while the BAS contractor owns the building-level integration point. The lighting industry is unlikely to walk into sophisticated BAS projects and simply displace established building-automation contractors. Nor does it need to.
The better opportunity for the lighting channel may actually be in smaller buildings. In a small or midsize building with connected lighting controls and a smart thermostat but no BAS, there may be no incumbent building-automation contractor to displace. Historically, there wasn’t much of an integration scope to own. V5.2 is making that building more interesting — and the lighting rep and electrical distributor already call on it.
The lighting channel doesn’t need to displace the BAS contractor in the big building. It needs to show up in the small one, where there’s no BAS contractor to displace.
Does the Manufacturer Have the Capability?
Acuity has been unusually explicit about where it’s going. The company now organizes itself around Acuity Brands Lighting and Acuity Intelligent Spaces. Intelligent Spaces includes Distech Controls, the building-automation company Acuity acquired in 2015, and QSC, the audio, video and control platform acquired in 2025. For the quarter ended May 31, 2026, Acuity Intelligent Spaces reported $303.5 million in sales, up 14.9 percent from the prior year, with a 25.1 percent adjusted operating margin. Acuity Brands Lighting remained much larger at $905.2 million in sales, but revenue declined 1.9 percent from the prior-year quarter.
Those numbers shouldn’t be overread. AIS isn’t simply a lighting-controls business — QSC includes audio and video, and Distech serves markets well beyond traditional lighting projects. Acuity didn’t rename itself because lighting ceased to matter. Lighting remains the largest part of the company by a wide margin. It renamed itself because lighting no longer describes the boundaries of the company it intends to build.
Most lighting manufacturers are not Acuity. Several major companies, including Lutron, Legrand, Signify, Current and Cooper, have developed substantial controls capabilities over many years. The question gets harder farther down the manufacturer landscape. For many mid-market fixture manufacturers, controls are still primarily an attribute of the product. That’s different from owning the controls business. Cybersecurity, configuration reporting, thermostat integration and cloud services require capabilities, support structures and economics that don’t behave like another SKU on the line card. They require people who understand software, commissioning, integration, service and an increasingly different customer conversation. And the manufacturer that builds those capabilities will discover something else fairly quickly: BAS contractors, integrators and mechanical contractors already have relationships in the rooms where much of this value is being discussed.
A mid-market manufacturer can invest and build the capability. It can partner with someone that already has it. Or it can decide that its job is still to be an exceptional fixture manufacturer, and integrate controls technologies where customers require them. What doesn’t make sense is operating economically like a fixture company while telling the market you’re a building technology platform.
Controls as an attribute of the fixture is a product decision. Controls as a business is a different company, and most mid-market manufacturers haven’t chosen which one they are.
Four Questions for the Channel
The scope question.
Look at the last ten meaningful controls projects. Who commissioned the system? Who was paid for that work? Who got the first call when the system didn’t perform as expected? If those are three different organizations, it’s worth asking whether the project really had an owner. The lighting rep can easily end up carrying the customer’s frustration without being paid to own the outcome.
The line-card question.
Is the controls line on the card a true agency capability, or primarily a manufacturer capability being represented locally? Most serious lighting agencies have someone designated as a controls specialist. The more useful test, the same one applied to every line in When Enough Is Enough, is the depth of that expertise. Can the agency handle the questions that routinely come up on a controls project without most of them ending up back at the factory? Can its team interpret a C137.9 configuration report, explain the intended control sequence, work through common integration questions, understand where the lighting scope stops and another trade’s scope begins, and hold a credible conversation with the mechanical or BAS side of the project? That’s a much higher bar than having someone who knows the product line. If the agency can sell the system but still depends on the factory to answer most questions of typical project scope, the controls line is represented locally — it isn’t yet owned locally.
The thermostat question.
Who in the agency, distributor or manufacturer’s regional organization can sit across from the mechanical contractor or controls contractor and have a credible conversation about how occupancy information should affect the building, rather than just how the sensor controls the luminaire? Those are different conversations.
The compensation question.
What does the rep agreement pay when the manufacturer sells software, monitoring, analytics, service, or another recurring offering into an account the agency created? Many traditional agreements were built around commission on invoiced product. They were never written for recurring software and service revenue. If an agency creates access to the customer, supports the controls sale, and helps establish the building relationship, but compensation stops at the fixture invoice, the manufacturer and the rep have a problem waiting to happen. An agency that helps its principal open a market it won’t be paid to participate in eventually notices.
That’s a contract clause, not a complaint.
The rep agreement was written for the fixture invoice. The market it now opens doesn’t stop there.
The Document Is the Message
V5.2 is a technical requirements update. It’s deliberately incremental. That’s precisely why I think it matters.
This isn’t a prediction that lighting manufacturers will become BAS companies, or that lighting reps are about to take the mechanical-controls business away from established contractors. It’s something narrower, and probably more consequential. Networked lighting infrastructure is beginning to create measurable economic value outside illumination. Some of that value will stay in the traditional lighting channel. Some won’t. Building-automation firms, integrators, mechanical contractors, and software companies already know how to sell and monetize parts of this scope. Lighting manufacturers and reps will have to decide where they genuinely add value and where partnership makes more sense.
The strategic question isn’t whether lighting should own all of it. It’s deciding which parts the lighting industry intends to own, which it intends to partner for, and which it’s comfortable surrendering. Acuity has already made its choice at the corporate level. The DLC is starting to put incentive rules behind some of the same capabilities.
The lighting channel can treat V5.2 as another rebate and technical-requirements update and keep selling a fixture with a sensor in it. Or it can recognize that an increasingly valuable part of the controls conversation is moving into a room where the lighting rep has no assigned seat — and go get one.
