News analysis · Announcement dated 24 September 2026; sources checked 28 September 2026.
Schneider Electric’s proposed acquisition of Shelly Group puts open smart-building interfaces at the centre of a major industry transaction. On 24 September, Shelly announced an agreement supporting Schneider’s intended takeover offer. For lighting teams, the immediate significance is strategic: a proposed combination of device-level automation and wider energy management. It is not a release of new lighting hardware or a completed acquisition.
What the companies announced
According to Shelly’s official announcement, the intended cash offer is €70 per share, valuing the company at approximately €1.2 billion. Completion is conditional on regulatory approvals and a minimum acceptance threshold of 95%; the companies expect closing by the first quarter of 2027. These are announced terms and expectations, not completed milestones.
Shelly describes its strategy as combining interoperable devices, open interfaces and cloud services for homes and smaller buildings. The proposed partnership would add Schneider’s resources and energy-management experience. Whether that leads to particular new integrations, support arrangements or product functions remains to be established through subsequent announcements.
The technical asset behind the headline
Open interfaces give an installer something more concrete to evaluate than a corporate compatibility promise. Shelly’s Gen2+ technical documentation describes JSON-RPC commands for device control and status. Its RPC channel documentation covers HTTP, persistent WebSocket connections and MQTT. The channels have different behaviour: HTTP handles individual requests, while WebSocket supports an ongoing connection and device notifications.
Our interpretation is that the interface matters because it makes the control path inspectable. A project team can identify how a command reaches a device, how state returns to the controller and which component must remain available. That is a more useful basis for evaluating lighting reliability than assuming every feature of a vendor’s app will appear in another platform.
What this means for wireless lighting
A wall control, a receiver and a building platform perform different jobs. The takeover announcement does not demonstrate that a particular wireless switch works with a Shelly device, that an energy-harvesting control supports Matter, or that a future Schneider integration is already available. Those conclusions require model-specific documentation and a supported connection between the devices.
For installers, the practical opportunity is to ask suppliers to document the complete command path. For product teams, it is to make supported interfaces, firmware requirements and recovery behaviour easy to find. For lighting designers, it is to retain clear requirements for switching and dimming while evaluating the automation layer separately. These are our project implications, not commitments made by either company.
What to watch next
The next useful signals are the formal offer process, completion announcements and any published changes to integrations or support. Shelly’s firmware update policy also cautions that device families do not all receive the same updates. A company-level announcement should therefore never substitute for checking the exact product and firmware used in a project.
For another example of separating an industry roadmap from available hardware, read our analysis of Thread’s Sub-GHz development plan. Keep the current specification grounded in documented equipment; review new capabilities when the supporting evidence becomes available.