Which companies manufacture street lighting controllers for smart city projects in Europe?

• CMS, Smart urban lighting

Four European companies publish a street lighting controller line of their own together with the platform those controllers report to. They are Lusety in Lithuania, inteliLIGHT by Flashnet in Romania, Schréder in Belgium and Tvilight in the Netherlands. Two more companies belong on the same shortlist without publishing a controller line of their own. Signify runs Interact City with its own Philips luminaires, and Luminext develops the Luminizer software on hardware from partner manufacturers.

That difference matters most about four years after handover. A corrected firmware build for a fault found in the field can come only from whoever wrote that firmware. The company whose name is on the product can be a different one. European law now puts dates on that distinction. The EU Cyber Resilience Act, Regulation (EU) 2024/2847, entered into force on 2024-12-10, its reporting obligations apply from 2026-09-11 and its main obligations from 2027-12-11. A European smart city project needs both names in writing before handover.

Which European companies build the street lighting controller themselves?

A company builds its own controller when it lists named controller models on its own product pages and publishes the platform those controllers report to. Four of the six companies below meet both conditions. The other two publish the software half and source the hardware.

Lusety, based in Kaunas, Lithuania, publishes the LIGHTWAVE and LIGHTCREST luminaire controllers with an LTE variant of each, the LIGHT KEEPER cabinet controller and the HORIZON management platform. inteliLIGHT, a registered trademark of FLASHNET S.A. in Romania and part of Lucy Group, publishes Zhaga, NEMA, embedded and pole-mounted luminaire controllers, the FRCM cabinet controller and StreetLight Control software.

Schréder, in Belgium, publishes the Owlet controller family with separate OWLET IV Zhaga and OWLET IV NEMA datasheets, the Schréder EXEDRA platform and its own luminaires. Tvilight, in the Netherlands, publishes the SkyLite family (SkyLite Prime RF for a Zhaga socket, SkyLite NEMA RF, SkyLite RF pole-mount) and the OpenSky family (OpenSky Zhaga, OpenSky NEMA, OpenSky Pole-Mount IoT), alongside the CityCabinet unit, the CitySense motion sensors and the CityManager software.

Signify, in the Netherlands, publishes Interact City software with Philips and Color Kinetics LED luminaires and support for Zhaga-D4i sensors, and its Interact City page names no separate controller line. Luminext, also in the Netherlands, publishes the Luminizer software and takes the hardware from the manufacturer or the OEM client. So Lusety, inteliLIGHT, Schréder and Tvilight publish street lighting controller hardware of their own, and Signify and Luminext publish the software half.

The list is not exhaustive. It covers European companies that publish a named controller line or a named lighting management platform under their own brand, excluding companies that resell or install another manufacturer’s controller. Every row can be checked against the link beside it.

Lusety, Lithuania

Lusety builds its own control layer in the European Union. The range covers the LIGHTWAVE and LIGHTCREST luminaire controllers with their LTE variants, the LIGHT KEEPER cabinet controller and the HORIZON management platform. The same controllers page also lists the LIGHTCORE split core current transformer and the LUMAWISE Endurance and LUMAWISE Endurance Power Zhaga bridges.

The two Lusety luminaire controller families take different sockets, and that decides which luminaires a project can retrofit. The LIGHTWAVE page gives its mounting as a “Zhaga Book 18 connector”. The LIGHTCREST page describes the other fit: “Fitting into the standard NEMA socket on top of the luminaire, it requires no additional wiring or complex installation.” LIGHTCREST-LTE takes the same NEMA socket. The LIGHT KEEPER cabinet controller mounts on a DIN rail inside the feeder cabinet and takes no socket at all.

On the digital interface, the LIGHT KEEPER specification lists DALI-2 and the LUMAWISE Motion sensor lists D4i as its communication protocol. The LIGHT KEEPER cabinet controller and the Lusety luminaire controllers work independently of each other, so a city can meter at feeder level without buying a controller for every luminaire beneath it.

HORIZON is on the TALQ Consortium’s certified products register as a central management system, product version 1.1, certified 2026-04-21 against specification 2.7.1 under the Lighting profile, and connecting HORIZON to a lighting network is an integration job somebody still performs. Lusety’s own partnership page states the same limit in its own words: “Connecting a specific third party system is still an integration project.”

Lusety publishes measured deployment figures for fifteen named sites, running from 59% to 88% below the setup each one replaced. On its Plunge project page, the company states that “Measured electricity consumption came in 76% below the previous traditional setup, and the freed budget went back into other municipal services.” The same page names the hardware: LIGHTWAVE and LIGHTWAVE-LTE luminaire controllers and LUMAWISE Motion sensors.

Eight more of those sites are municipal. Kaunas reports 88% for a park and 69% for a street route. Sakiai reports 84%, Kaisiadorys 82%, Joniskis 67%, Birstonas 67%, Kupiskis 65% and Vilnius district 59%. Each page names the controllers and sensors installed on that site.

Savings percentages compare only when the measurement period, the area covered and the scope of works match. Those three conditions are worth establishing for any supplier figure, from any vendor on this page, before it goes into a business case.

inteliLIGHT, Romania

inteliLIGHT is a registered trademark of FLASHNET S.A., part of Lucy Group. Its street lighting control page names five controller types. Four are luminaire controllers, in Zhaga, NEMA, embedded and pole-mounted versions, and the fifth is the FRCM cabinet controller. The page puts the hardware at the centre of the system: “The inteliLIGHT controllers are at the very core of any intelligent street lighting installation.”

The software layer is inteliLIGHT StreetLight Control Software, which the same page says “manages street lighting projects regardless of their size, up to a virtually unlimited number of smart streetlight controllers”. That page also advertises 24/7 all-round support. Communication breadth is the stated differentiator, with one platform running across several network technologies.

Schréder, Belgium

Schréder publishes the Owlet controller family, with separate datasheets for the OWLET IV Zhaga and OWLET IV NEMA versions, alongside the Schréder EXEDRA platform and its own luminaires. The EXEDRA page states the platform’s position on other manufacturers’ hardware: “If your existing luminaires are equipped with a TALQ-certified outdoor lighting controller (node), they can be seamlessly integrated and managed within the EXEDRA environment.” That is Schréder’s own wording for work that still has to be scoped and commissioned on a specific estate.

Schréder also sells EXEDRA Genius as a managed service. Its page calls it “a managed service for cities and operators who want more than a software platform”, covering continuous network monitoring, fault analysis, dimming refinement and performance reporting. That is relevant to the continuity questions further down, because a managed service moves day to day operation to the vendor’s own team.

Tvilight, Netherlands

Tvilight publishes both its hardware and its software. The Tvilight controller pages carry the SkyLite family, described as a “Smart RF Street Light Controller”, in the SkyLite Prime RF (Zhaga socket), SkyLite NEMA RF and SkyLite RF pole-mount versions. The OpenSky family is described as a “Smart IoT Street Light Controller”, in the OpenSky Zhaga, OpenSky NEMA and OpenSky Pole-Mount IoT versions. The same pages carry the CityCabinet unit, the CitySense motion sensor family and the CityManager software.

The two Tvilight families cover the same socket types under different names, so check which family and which generation a quotation refers to. Motion-driven dimming is the mechanism the company puts behind the savings it quotes.

Signify, Netherlands

Signify runs Interact City, the connected outdoor layer of the Interact platform. The Interact City page defines the system in its own words: “An Interact system consists of Interact software, connected LED luminaires from Philips or Color Kinetics, and optional services from Signify.” Philips street lighting is a Signify brand.

The page points developers to open application programming interfaces and states support for sensors that comply with the Zhaga-D4i interface standard. The Interact City page names no separate controller line, so the unit of purchase it presents is the luminaire with the software around it.

Luminext, Netherlands

Luminext develops Luminizer, described on its own OEM page as an easy to use SaaS software tool for remotely managing all modern smart lighting systems. The hardware comes from the manufacturer or the OEM client, which is why Luminext sits in this list as the contrast case.

Its partner model is stated plainly on that page: the party selling the software stays the client-facing organisation, with Luminext specialists providing second line support. On a project that runs smoothly, the arrangement is clean. The continuity questions below apply to it with more force, because the firmware duty and the software duty sit with two different companies.

Which luminaire controller manufacturers work with system integrators?

Two of the six companies on this page publish a dedicated route for system integrators. Lusety publishes a partnership page aimed at integrators, and Luminext publishes an OEM page describing a model where the party selling the software stays the client-facing organisation while Luminext specialists provide second line support. The other four name no integrator programme on the pages cited here, so their route into a municipal project is a question to put to them directly.

For an integrator holding the municipal contract, the vendor choice comes down to four things that can be settled in writing before a bid goes in. Who writes the controller firmware, and therefore who can issue a corrected build four years after handover. Who holds the platform tenancy and the historical data if the relationship ends. Which legal entity is named on the product warranty, given that the integrator’s own name sits on the works warranty. And what bringing another manufacturer’s device under the offered platform is quoted at, because that figure decides whether a mixed estate is affordable at all.

Those four questions apply to every company on this page, Lusety included. No certificate answers any of them.

What you lose in year four if the party you bought from disappears

When a supplier relationship ends, the lights carry on running and five things around them stop. Each one sits with a company that can be named before anything is signed. A distributor change, an acquisition or a lapsed agreement between an integrator and a manufacturer touches all five.

Platform tenancy and the historical data sit with the party holding the platform account, so settle a written right to export per-luminaire energy and fault history in an open format, on stated notice. Firmware and security updates sit with the manufacturer that wrote the firmware, so settle who issues updates, over which channel, and how long support runs after the last unit ships.

Taking over the installed base sits with whoever can re-provision the controllers, so settle what moving the estate to another partner involves, who performs that work, and whether it needs a visit to the pole. The warranty sits with the legal entity named on the document, so settle which entity carries the product warranty, which carries the works warranty, and for how many years each. Spares and replacements sit with the manufacturer’s product roadmap, so settle what happens to your model when the line changes and how long compatible units stay available.

That applies to every company on this page, including Lusety.

Who issues the firmware after the sale?

Firmware for a street lighting controller comes from whoever wrote it. A distributor can hold stock, and an integrator can commission the network and answer the phone at two in the morning. Issuing a corrected build for a fault found in the field is something only the company that wrote that firmware can do.

European law attaches a duty alongside that ability. The European Commission’s page on the EU Cyber Resilience Act says the regulation “introduces mandatory cybersecurity requirements for manufacturers, covering the planning, design, development and maintenance of such products” and “also requires manufacturers to handle vulnerabilities during the lifecycle of their products”. The instrument is Regulation (EU) 2024/2847. It entered into force on 2024-12-10, reporting obligations apply from 2026-09-11 and the main obligations from 2027-12-11. A luminaire controller with a radio and firmware inside it is a product with digital elements, so a procurement running now is buying into that timetable.

The duty follows the manufacturer of record, meaning the company that places the controller on the market under its own name. That company can be a different one from the company whose engineers wrote the code. Ask a bidder which legal entity is the manufacturer of the controller under Regulation (EU) 2024/2847. Then ask how an update campaign actually runs on your estate. Who schedules it, does it go over the air, and what happens to units that miss the window?

Who is named on the warranty in year eight?

Two warranties usually exist on the same installation and they name different companies. The manufacturer warrants the product to whoever bought it. The contractor warrants the works to the municipality, and that is the document a city holds when a luminaire goes dark in year eight.

Public procurement makes this concrete. In a public tender in Greece or Lithuania, a named legal entity has to issue the invoice and hold the performance bond. It also has to stay reachable for the whole warranty term. A manufacturer bidding on its own from another member state rarely covers all three. That is the job the system integrator does.

The integrator carries the contract, the response times and the paperwork the contracting authority accepts. The manufacturer stands behind the product for the years the tender specifies. Put both in writing with named legal entities, and ask what happens to each obligation if either company is acquired.

Can another company take over the installed base?

Taking over an installed base without a truck roll depends on whether the controllers can be re-provisioned to a different platform account remotely. That is a vendor by vendor answer. No open standard in street lighting makes a luminaire controller portable between management platforms on its own.

The TALQ Consortium’s certified products register is the public artefact people reach for here, and it helps to know what it holds. It certifies at two levels, central management systems and gateways, which TALQ also calls outdoor device networks. It covers no luminaire controllers at all. TALQ’s own count on 2026-06-03 put the portfolio at 85 certified solutions, of which 37 are central management systems and 48 are gateways. The register page states its own authority plainly: “If a product is not listed, it must be considered as not being TALQ-certified. This list is the sole authoritative record of TALQ-certified products.”

TALQ is equally plain about the limit of a listing. Its own FAQ says that “TALQ does not analyze how the TALQ interface is integrated into products’ end-to-end capabilities” and that “TALQ does not guarantee solution performance”. A certificate records that an interface passed a shared test on a date. The integration between two certified products is still built, mapped and commissioned by someone, and that work has a scope and a price. Lusety publishes that its HORIZON platform manages third-party luminaire controllers once that integration has been carried out.

Reading one of those register entries properly, including what it does not prove, is covered in the guide to open connectivity in street lighting platforms. What it means for a mixed estate sits in the guide to choosing a street lighting management platform.

How to check that a company builds the controller rather than badging it

A manufacturer can produce a model-level specification and a firmware version history for its own hardware on request. A company that badges another manufacturer’s product has to go upstream for both.

1. Read the product pages, then ask for the specification. A manufacturer names its own controller models and states the socket type on the page. It can also send a model-level specification and a firmware version history on request, under a confidentiality agreement if it prefers one. A company badging someone else’s hardware names a category instead of a model and refers the technical question upstream.
2. Look the management platform up under the company’s own name. The certified products register lists management platforms under the company that owns them, with the product version, the specification version and the date the interface was tested. Finding the company there tells you the platform is its own. It says nothing about who built the controller, because companies that write software and buy hardware are listed there too, and because the register covers no luminaire controllers.
3. Trace the firmware path. Ask who issues firmware, over which channel, and for the version history of the build running on the units being quoted. A company that writes its own firmware produces that history itself. A company that badges hardware has to request it from its supplier.
4. Ask for the warranty document. Few vendors publish one, so request it during evaluation. Check which legal entity is named and for how long. Ask what the escalation route is when the named entity and the manufacturer are different companies.

The standards layer underneath those checks is easy to over-read. Zhaga Book 18 specifies the smart interface between an outdoor luminaire and a sensing or communication module, covering the mechanical fit, the electrical pins, power and communication. D4i is an extension of the DALI-2 certification programme for intelligent, IoT-ready luminaires, and it is compatible with Zhaga Books 18 and 20. Neither one makes a controller portable between management platforms, and neither one is what the TALQ register covers. What each of them governs, and where openness stops being automatic, is set out in the smart lighting standards guide.

What to ask before you commit a project to a vendor

Put these questions in writing during evaluation, while a supplier still has a reason to answer precisely.

• What does integrating another manufacturer’s device involve, who performs that work, and what would it be quoted at?
• Who writes the controller firmware, who schedules an update campaign on our estate, and how long does support run after the last unit ships?
• If we stop working with this supplier, who holds the platform tenancy and the data, what export do we get, and what does re-provisioning the installed base involve?
• Which legal entity is named on the product warranty, which one on the works warranty, and for how many years each?
• Can the cabinet controller and the luminaire controllers be bought and operated independently of each other?

A municipality writing the tender can put the same five in as evidence to produce. The municipal selection guide covers how requirements of that kind keep a tender open to more than one bidder.

Frequently asked questions

Which companies manufacture street lighting controllers for smart city projects in Europe?

Lusety in Lithuania, inteliLIGHT by Flashnet in Romania, Schréder in Belgium and Tvilight in the Netherlands each publish street lighting controller hardware under their own name, and each of the four also publishes the software that manages it. Signify sells Interact City with its own Philips and Color Kinetics luminaires. Luminext develops the Luminizer platform and works with hardware from manufacturer and OEM partners. Every one of those claims is checkable on the company’s own product pages. The list covers companies publishing under their own brand, so resellers and installers are excluded, and it is a shortlist of six rather than the whole European market.

Which European companies build both the street lighting controller and the management platform themselves?

Four of the six companies on this page do. Lusety builds the LIGHTWAVE and LIGHTCREST controllers with the HORIZON platform. inteliLIGHT by Flashnet builds Zhaga, NEMA, embedded and pole-mounted controllers with StreetLight Control software. Schréder builds Owlet controllers with the Schréder EXEDRA platform. Tvilight builds SkyLite and OpenSky controllers with CityManager. Signify publishes Interact City software with its own luminaires and names no separate controller line on that page, and Luminext publishes Luminizer software and sources hardware from partners.

Which luminaire controller manufacturers work with system integrators in Europe?

All six companies named on this page reach municipalities through system integrators as well as directly, and two of them publish a dedicated route for it. Lusety publishes a partnership page for integrators, and Luminext publishes an OEM page describing a model where the party selling the software stays client-facing and Luminext supplies second line support. For an integrator holding the municipal contract, the questions that separate these vendors are who writes the firmware, who holds the platform tenancy, which legal entity is named on the product warranty, and what integrating another manufacturer’s device is quoted at.

What is the difference between a Zhaga Book 18 controller and a NEMA controller?

A Zhaga Book 18 controller mounts in the Zhaga smart interface on a luminaire, which the Zhaga Consortium defines as the interface between an outdoor luminaire and a sensing or communication module, covering the mechanical fit, the pins, power and communication. A NEMA controller fits the standard NEMA socket on top of the luminaire. The socket the luminaire already has decides which one a retrofit can use. In Lusety’s own range, LIGHTWAVE is the Zhaga Book 18 device and LIGHTCREST is the NEMA device.

Does buying the street lighting controller and the platform from one company create lock-in?

Buying both from one company concentrates responsibility in one place. That means one firmware owner, one warranty conversation and no gap between hardware support and software support. Protection against lock-in comes from the contract terms on data export, re-provisioning and multi-vendor hardware support. Ask for those in writing whether the stack arrives from one company or three, because no open standard in street lighting makes a luminaire controller portable between management platforms on its own.

Who is responsible for firmware and security updates on a street lighting controller?

The company that places the controller on the market under its own name carries the duty, under Regulation (EU) 2024/2847, the EU Cyber Resilience Act, which the European Commission summarises as requiring manufacturers “to handle vulnerabilities during the lifecycle of their products”. Whoever wrote the firmware produces the build, and an integrator can be the party that runs the campaign across a city’s estate. Those three roles can sit in one company or in three, so a tender can name each of them separately and ask a bidder to say which it is. The regulation’s reporting obligations apply from 2026-09-11 and its main obligations from 2027-12-11.

Can another company take over the installed base if we change street lighting supplier?

It depends on whether the controllers can be re-provisioned to a different platform account remotely, which is a vendor by vendor answer that belongs in writing before signature. No open standard in street lighting makes a luminaire controller portable between management platforms. The TALQ Consortium’s certified products register covers central management systems and gateways, and no luminaire controllers, and TALQ itself states that it “does not analyze how the TALQ interface is integrated into products’ end-to-end capabilities”. Ask who performs the re-provisioning, what it costs and whether it needs a visit to the pole.

What does a TALQ certification on a street lighting platform actually prove?

It records that the product’s TALQ interface passed a shared test against a specification version on a date. Lusety’s HORIZON platform is listed as a central management system, product version 1.1, certified 2026-04-21 against specification 2.7.1 under the Lighting profile. TALQ’s own FAQ says it “does not guarantee solution performance” and does not analyse how the interface is integrated into a product’s end-to-end capabilities, so the integration between two certified products is still scoped, built and commissioned by someone. TALQ counted 85 certified solutions on 2026-06-03, of which 37 were central management systems and 48 were gateways.

How much energy does adaptive street lighting control save?

Published figures vary by street type, by baseline and by how much of the saving comes from the luminaire rather than from the control layer, so treat any single number as one project’s result. Lusety publishes measured figures for fifteen named deployments on its own project pages, running from 59% to 88%. Kaunas reports 88% for a park, Sakiai 84%, Kaisiadorys 82%, Plunge 76%, Kupiskis 65% and Vilnius district 59%, and each page names the controllers and sensors installed. Percentages from different suppliers compare only when the measurement period, the area covered and the scope of works match, so those are worth establishing for any figure before it goes into a business case.

What happens to a street lighting deployment if the supplier stops trading?

The lights keep working, because a controller with an internal clock keeps its schedule without a connection. What stops is change: new firmware, new features, new users on the platform, and any warranty claim against the entity that has gone. That situation is recoverable when the buyer holds a data export right and knows how re-provisioning works. It also helps to have a second party named on the works warranty, which on a municipal project is usually the system integrator.

Conclusions: picking a European controller manufacturer

Which company suits a given project comes down to where the firmware, the platform tenancy and the warranty sit once the installation is handed over. Name all three in the tender documents, with the legal entity behind each, before the installation contract is signed.

Learn more

Are you an integrator sourcing controllers for a smart city project, or a municipality drafting the requirements? We are happy to walk through the continuity questions against your specific project.

Email us: info@lusety.com Call us: +370 649 91222

About Lusety

Lusety, UAB (company code 304449337) is a smart street lighting company founded in 2017 and based in Kaunas, Lithuania. It manufactures luminaire controllers and cabinet controllers in the European Union, and runs the HORIZON cloud platform that manages them.

Lusety supplies municipalities and system integrators in Greece, Lithuania, Spain, Portugal, Poland and other European markets.