Smart Street Light Control Systems: How They Work, What They Save, How to Buy One

“Smart street lighting” is often sold as a smart-city platform with sensors, cameras and Wi-Fi on every pole. For most road owners the value is simpler: lights that report their own faults, run at the right level at each hour of the night, and are billed on what they actually use. This guide explains how such systems are built, what they save and how to buy one without locking yourself in.

The three layers

1. The node on each light. A small controller, usually plugged into a socket on top of the luminaire (Zhaga Book 18 or NEMA 7-pin), sometimes built in. It switches and dims the driver, measures voltage, current, power and energy, detects faults (lamp failure, driver failure, power loss) and often includes a photocell and a GPS or position tag.

2. The communication network. How the node talks to the central system:

3. The central management system (CMS). Usually a web application where operators see every light on a map, receive alarms, set dimming profiles, read energy data, and export reports for maintenance and billing.

What it actually does for the road owner

• Fault reports instead of night patrols. Each failed light raises an alarm with its position, so crews go straight to it. In many cities, finding failed lights depends on patrols or complaints; a monitored network closes that gap.
• Dimming by time, traffic or event. Different profiles for different roads, holidays or events, changed from the office. See LED street light dimming and controls for the dimming options in detail.
• Metered energy. Each node measures what its light uses. Where the utility accepts metered data, the city pays for actual consumption rather than a flat estimate per lamp.
• Asset records. Every light’s type, installation date, burning hours and repair history in one place.
• Constant light output. Drivers can start at a lower level and rise over the years, saving energy while the LEDs are new.
• A platform for other sensors, such as traffic counters or environmental sensors, if and when they are needed.

A business case for 1,000 lights

Take 1,000 LED street lights of 100 W, burning about 4,200 hours a year, at US$0.15/kWh:

• Annual energy at full output: 1,000 × 100 W × 4,200 h = 420,000 kWh, about US$63,000
• A dimming profile that runs at full power in the evening and 50% from midnight to dawn typically cuts 25–30%; at 30% that is about 126,000 kWh and US$18,900 a year
• Fault reporting and fewer patrols save labour and vehicle time, and lights are repaired faster, which is a public-safety benefit even where it is hard to price

The node, the network and the software subscription have to be paid for out of these savings. The business case is usually strongest where lights are already LED (so the remaining energy is the target), traffic falls sharply at night, the network is large, and labour for patrols is expensive. To estimate the energy part for your own network, enter the equivalent full-power hours of your dimming profile as the operating hours in our LED retrofit savings calculator.

How large projects are being contracted

Large cities increasingly buy smart lighting as a performance contract rather than a supply order. Delhi, which in October 2026 began replacing about 100,000 streetlights with app-monitored smart LEDs, reportedly requires the contractor to keep 99% of lights working and maintain them for seven years, with a daily penalty for each fault not fixed within 48 hours. In contracts like this, fixture reliability and the speed of fault detection are worth money to the contractor, which is exactly what a monitored network provides.

Interoperability: avoid being locked in

A street lighting network lasts 15–20 years, longer than most software platforms and radio technologies. Three standards keep the options open:

• Zhaga Book 18 or NEMA sockets on the luminaire, so the node can be replaced or upgraded without opening the light.
• D4i drivers (DALI-2 with standardised data and power for the node), so any certified node can dim the driver and read its energy and diagnostic data.
• TALQ for the interface between the central software and the outdoor network, so lights from different suppliers can be managed in one system.

Order luminaires with a socket and a D4i or DALI driver even if the city starts with simple photocells or shorting caps. Adding the controls later is then a plug-in job.

Security and data

A connected street lighting network is part of the city’s infrastructure. Ask suppliers about:

• Encrypted communication between node, gateway and CMS
• User accounts and access rights in the CMS
• Firmware updates over the air, and who is responsible for them
• Where the data is hosted, who owns it, and how it can be exported if the contract ends

Buyer’s checklist

1. Scope: number of lights, roads and existing luminaires; whether the luminaires already have sockets and dimmable drivers
2. Functions you need now (switching, dimming, fault alarms, metering) and later (sensors)
3. Network technology suited to the city: coverage, ownership, running costs
4. Interoperability: Zhaga or NEMA, D4i, TALQ; ask for certificates
5. Service levels: alarm response time, data availability, software support period
6. Total cost over 10–15 years: nodes, gateways, installation, subscriptions, SIM fees, replacement
7. Pilot first: a few hundred lights on mixed roads for a few months, with measured savings

Our LED street lights can be supplied with dimmable drivers and Zhaga or NEMA sockets ready for the controller your city chooses. Tell us which system you use or plan to use, and we will match the driver and socket configuration.