Open Standard Protocol

LonWorks: The Protocol That Time Forgot

LON was supposed to be the open future of building automation. Then BACnet won. If you're running LonWorks, you're not alone — and there's a path forward.

Discuss LON Integration

What is LonWorks?

LonWorks (LON) is a peer-to-peer networking protocol developed by Echelon Corporation in the 1990s. Unlike master-slave protocols, every LON device can communicate directly with every other device.

LON was adopted by many manufacturers as an "open" alternative to proprietary protocols. Honeywell, TAC/Schneider, and others built LON-based products. For a while, it looked like LON might become the industry standard.

Then BACnet happened. ASHRAE's standard became the dominant open protocol, and LON investment slowed. Today, LON systems are still running but support and expertise are declining.

LON Strengths

  • • True peer-to-peer architecture
  • • Highly reliable networking
  • • Multi-vendor interoperability (in theory)
  • • Still functional after decades

LON Challenges

  • • LNS (LonWorks Network Services) complexity
  • • Declining manufacturer support
  • • Expertise harder to find
  • • Integration with modern systems

Common LON Installations

  • • Honeywell Excel/LON systems
  • • TAC/Schneider Xenta controllers
  • • Tridium JACE with LON
  • • Lighting control systems

The LNS Problem

LON networks are managed through LonWorks Network Services (LNS) — a database that tracks every device, binding, and configuration on the network.

This creates challenges:

  • • LNS databases can become corrupted over time
  • • Device replacement requires LNS updates
  • • Network documentation often incomplete
  • • Finding LNS expertise is difficult

We Know LNS

Working with LON networks requires understanding both the protocol and the LNS database. Many contractors can do one or the other — we do both.

We can:

  • Recover and repair LNS databases
  • Commission new LON devices
  • Document existing LON networks
  • Integrate LON with BACnet/Niagara
  • Plan and execute LON migrations

LON Integration Options

LON-to-BACnet Gateway

Hardware gateways that expose LON network variables as BACnet objects. Keep your LON devices running while integrating with modern systems.

Best For:

  • • Quick integration needs
  • • Preserving existing investment
  • • Phased migration plans
RECOMMENDED

Niagara LON Driver

Niagara Framework includes native LON support. Communicate directly with LON devices and integrate with any other protocol.

Best For:

  • • Full integration capability
  • • Mixed protocol environments
  • • Long-term flexibility

Controller Replacement

Replace LON controllers with native BACnet equivalents. Eliminates LON entirely but requires more upfront investment.

Best For:

  • • End-of-life equipment
  • • Major renovations
  • • Complete modernization

LonWorks FAQ

Is LonWorks still supported?

The protocol itself is stable and devices continue to work. But manufacturer support for LON-based products is declining, and finding new LON equipment is increasingly difficult.

Can LON and BACnet coexist?

Absolutely. We regularly run hybrid environments where LON devices are integrated via Niagara alongside native BACnet equipment. This allows gradual migration.

What if my LNS database is corrupted?

We can often recover LNS databases or rebuild them from the network. In worst cases, we can re-commission devices. It's painful but fixable.

How long should I expect LON to last?

Well-maintained LON systems can run for many more years. But we recommend having a migration plan — even if execution is years away. The expertise pool is shrinking.

Need Help With Your LON Network?

Whether you need LNS support, integration with other systems, or a migration plan — we can help.

Discuss Your LON System