A few per stretch. Not one per pole.
This is the assumption that decides whether adaptive lighting is affordable. A stretch of road behaves as one object: it needs its traffic counted, its luminance measured and its weather known — once, not at every pole.
Sensor pole on a controlled stretch — installed site
Three measurements, three devices.
Traffic alone gives you traffic-adaptive operation. Adding luminance and weather gives you the full-adaptive loop — and the compensation for everything that drifts over the years.
Counting radar
A 24 GHz radar developed in house counts vehicles in both directions, minute by minute, from a 4–5 m mounting height. It counts flow — it is not a movement detector, and the lighting does not chase individual cars.
Road luminance unit
Measures the light actually on the road surface, closing the loop: it compensates LED depreciation, changes in surface reflectance — wet or dry — and luminaires that do not behave exactly as designed.
Weather station
Rain, snow and above all fog. When visibility drops, adaptive reduction is suspended and the stretch goes back to its design class, however empty the road is.
One set of sensors serves the stretch it is installed on, and side roads can take their class from the main road they join. A city is instrumented at the level of the road network, not at the level of the pole — which is why the sensor cost does not scale with the number of luminaires.
Presence, and the city ones.
The same network carries measurements that have nothing to do with light — which is how a lighting project turns into an infrastructure.
Presence radar
A 24 GHz radar with about 15 m of range, for cycle paths, parks, yards and perimeters: it raises a whole group of luminaires as someone approaches and lets them fall back afterwards. Used where light on demand makes sense — pedestrian areas — rather than on traffic roads, where flow-based adaptation saves far more.
Standalone control →SensorBox
One pole-mounted box with radar traffic classification, particulate from PM1 to PM10 and noise, with its own eSIM — so it can be installed where there is no lighting network to join, and still report into the same platform.
Water level and leak detection, indoor air quality, temperature and humidity, structural sensors: brought in over LoRaWAN, Modbus or digital inputs, and normalised into the same data model. These are integrations configured per site, and we label them as such rather than listing them as our own catalogue.
Integrations & APIs →The sensor decides, then tells the network.
The device that counts the traffic is the device that works out the class and sends it to the luminaires over the mesh. No cloud, no gateway, no broadband line is involved in that step — which is what makes the reaction immediate and the installation independent.
Mains powered, on a pole
No batteries to replace across a city — the pole already has power.
On the same mesh
Measurements travel on the network that is already there, with no subscription of their own.
Failure is safe
If a sensor stops, the stretch returns to its design class. The standard requires it; the system does it.
Send the stretches you want to make adaptive.
Lengths, lanes, classes and mounting heights: enough for us to say how many sensor sets the network needs and where they go.