LonWorks to KNX Migration: Why Switch Now?
LonWorks technology is facing a decisive turning point. With production due to end in March 2026, discover why KNX is emerging as the sustainable alternative for your building automation.
Alert: End of LonWorks Production
Order deadline: 15 September 2025
Last delivery: 15 March 2026
Cause: End of production of the Renesas Neuron chip
The End of LonWorks Production in 2026
LonWorks technology is facing a decisive turning point. With the end of production of the Renesas Neuron chip scheduled for March 2026 and the order deadline set for 15 September 2025, professionals in building automation and BMS (Building Management Systems) must anticipate their migration to alternative solutions.
KNX, the open standard protocol for building automation, is emerging as the alternative of choice to replace LonWorks installations.
Why is LonWorks Disappearing?
End of Technology Support
- Renesas is ceasing production of the essential Neuron chip
- Closed ecosystem dependent on a single supplier
- Market decline in the face of open technologies
Immediate Consequences
- End of production of LonWorks equipment
- Shortage of components from 2026
- Planned obsolescence of existing installations
KNX: The Sustainable Alternative to LonWorks
Advantages of the KNX Protocol
ISO/IEC 14543-3 internationally recognised standard
Over 500 certified manufacturers
No technological limitations
Decentralised bus with no single point of failure
Advanced diagnostics for complete monitoring
Easy addition of new features
Installation Compatibility
- Reuse of existing cabling possible (twisted pair)
- Flexible topology: line, star, tree
- Power supply integrated on the data bus
Technical Comparison: LonWorks vs KNX
| Criterion | LonWorks | KNX |
|---|---|---|
| Openness | Closed ecosystem | Open standard |
| Manufacturers | Limited (Renesas) | 500+ certified |
| Cabling | Twisted pair | Twisted pair/IP/RF |
| Speed | 78 kbps | 9.6 kbps (sufficient) |
| Diagnostics | Limited | Advanced (ETS) |
| Scalability | Constrained | Unlimited |
Technical Migration: From LonWorks to KNX
Transition Steps
Phase 1: Preparation (3-6 months)
- • Audit of the existing LonWorks installation
- • Planning of the KNX architecture
- • Training of technical teams
- • Selection of KNX equipment
Phase 2: Migration (6-12 months)
- • Gradual migration by functional zones
- • Testing and system validation
- • Training of end users
- • Documentation complete
Compatibility Solutions
- Gateways for LonWorks/KNX communication
- Temporary coexistence of both protocols
- Selective migration of critical equipment
KNX Applications to Replace LonWorks
Residential Automation
- • Smart lighting with presence detection
- • Heating/air conditioning with zone-by-zone regulation
- • Roller shutters automated based on sunlight
- • Security integrated (alarm, access control)
Commercial Automation
- • BMS (Building Management Systems)
- • HVAC (Heating, Ventilation, Air Conditioning)
- • Energy management and monitoring
- • Street lighting intelligent
LonWorks to KNX Migration Cost
Initial Investment
Direct costs
- • KNX equipment: comparable price to LonWorks
- • Technical training: 1-2 weeks
- • Programming tools: ETS software
- • Installation: 30-50% saving (cabling reused)
ROI and Economic Benefits
- • Reduction in maintenance costs (20-30%)
- • Energy savings: 15-25%
- • Longevity guaranteed over 20+ years
- • Added value to the building
Recommended Migration Schedule
Critical Timeline
Recommended KNX Manufacturers and Solutions
Major Market Players
- • ABB: complete residential/commercial range
- • Schneider Electric: integrated BMS solutions
- • Siemens: smart building expertise
- • Jung: design and innovation
- • Gira: premium solutions
Specialised Solutions
- • Gateways: Weinzierl, Intesis
- • Supervision: Facility Pilot, ETS Inside
- • IoT/Cloud: KNX Secure, KNX IP
Frequently Asked Questions (FAQ)
Why is LonWorks disappearing in 2026?
Renesas is ceasing production of the Neuron chip essential to LonWorks operation. The order deadline is set at 15 September 2025 and final delivery at 15 March 2026.
Can I reuse my existing LonWorks cabling with KNX?
Yes, in most cases, the twisted-pair cabling used for LonWorks can be reused for KNX, which considerably reduces migration costs.
How much does LonWorks to KNX migration cost?
The cost varies depending on installation size, but reusing existing cabling enables savings of 30-50%. ROI is generally 3-5 years thanks to energy savings.
When should I plan my migration to KNX?
It is recommended to start now to benefit from the last LonWorks equipment for the transition and plan the migration before 2026 with peace of mind.
Conclusion: Anticipating for a Successful Transition
The end of LonWorks in 2026 represents a unique opportunity to modernise your installations with KNX, the future protocol for building automation.
Acting now allows you to:
- • Secure the longevity of your installation
- • Benefit from the last LonWorks equipment for the transition
- • Plan the migration to KNX with peace of mind
- • Optimise energy performance
Do not wait until 2026: contact a certified KNX integrator today to evaluate your migration project.
Need help with your migration?
Our KNX experts specialise in LonWorks installation migration. Get a tailored study and a migration plan adapted to your situation.
Consult our migration expertsAbout the author
Jean Dupont
Certified KNX Expert
Specialist in LonWorks to KNX migration with 15 years of experience. Jean has supported over 50 migration projects and is fully familiar with the technical challenges.
Similar articles
Urgent LonWorks migration?
Get a feasibility study and a personalised quote for your migration to KNX.
Free migration assessmentRecommended articles
KNX vs Loxone: which system to choose in 2025?
Detailed comparative analysis to choose the right home automation protocol.
Read more
The advantages of KNX for smart homes
Discover why KNX is the reference protocol in building automation.
Read more
KNX installation prices in Luxembourg 2025
Complete pricing guide to budget your KNX project.
Read more