networked lighting controls
Apply the project brief to networked lighting controls: record zone and load schedule and commissioning ownership and exclusions before asking for an alternative. Use the application description as an input to supplier review; do not assert a universal product rating, installation result or project approval.
Site conditions before hardware selection.
How site conditions change the purchasing brief
Networked lighting controls are purchased as hardware that must later sit on a bus or IP backbone. Ceiling height, partition density and existing dimming interface each change which controllers, sensors and gateways are even eligible. This page does not provide installation instructions, photometric design or a claim that one vendor’s nodes will join another vendor’s network. UL listing and DLC Qualified Products List status, when a project requires them, are checked against named models after a factory reply—not assumed from a family brochure.
| Application condition | Information to collect | Supplier confirmation |
|---|---|---|
| Office floors with mixed daylight and occupancy | Measured zone count, load type per zone, intended scenes, and whether wall stations are in the hardware price | Controller capacity, sensor compatibility, and which power supplies are included versus extra |
| Warehouse or high-space networked runs | Mounting height, circuit count, input voltage at the panel, and who owns addressing after delivery | Supported topology, spare addresses, and whether commissioning is excluded from the hardware quote |
| Hospitality or campus mixed protocols | Existing 0-10V dimming interface versus DALI loops versus wireless pockets that must remain isolated | Gateway list, interoperability evidence, and any software or subscription fees sitting outside hardware |
Site constraints change zone and load schedule and commissioning ownership and exclusions. A denser partition plan may split occupancy groups without changing lumen packages on the fixtures. A longer warehouse run may force additional power supplies even when the same controller family is named. If the buyer later allows a wireless lighting control system in one wing, that pocket is recorded as a separate configuration—not as proof that the rest of the building will interoperate. Decisions that require the buyer or a qualified project team, rather than this sourcing service, include photometric coverage, AHJ filings, software administration and who walks the job for addressing.
Compare light output of attached luminaires before wattage when a packaged kit is quoted. Do not copy ballast-compatible versus ballast-bypass tube rules onto a controller RFQ. Constant current versus constant voltage remains a load-matching question for drivers, not a reason to swap two gateways. Strip IP rating versus whole-system suitability is similarly out of scope unless the inquiry actually includes tape lighting as a load. Continue with inquiry options, manufacturer matching, sample planning or the RFQ form.
Ready to compare the same scope?
- Zone schedule and protocol mix for networked lighting controls
- Quantity and units for controllers, sensors and gateways
- Destination and timing, with commissioning exclusions written down