PlaygroundWORK PROJECT / PROJECT STUDYAll work

Network reliability / Work project · field-tested failover

Flappy.

A stable KNX/IP endpoint with automatic failover between interfaces.

PythonKNX/IPTCP / UDPHome Assistant OSDocker
FIELD-TESTED / HOME ASSISTANT OS

BUILT FOR THE PLACE IT RUNS

On-site systems.
Not a hosted website.

Installed alongside Home Assistant OS and connected to the site’s KNX interfaces. The proxy cannot run as a public website; it needs the HAOS host and local bus hardware.

Deployed to 5+ sites · under 80 ms recovery in tested conditionsRésumé-reported deployment context
flappy / interactive studyLOCAL PREVIEW
KNX/IP / STABLE ENDPOINT + BACKEND PATHS
HOME ASSISTANTStable KNX endpoint
PATH 01 / PRIMARYKNX interface AHealthy · active
PATH 02 / FALLBACKKNX interface BHealthy · standby
PRIMARY PATH ACTIVEMonitoring configured interfacesRésumé result: under 80 ms in tested conditions

Illustrative state transition · the click does not reach a KNX bus.

THE ENGINEERING QUESTION / 02

How can Home Assistant keep a stable KNX endpoint when an interface or gateway drops out?

A KNX/IP failover proxy for Home Assistant OS that checks multiple backend interfaces and handles failover and failback across TCP, UDP, and USB paths.

THE APPROACH / 03

Make the system’s logic visible.

Keep a stable proxy endpoint in front of the KNX interfaces, monitor their health, switch to an available path, and restore the primary when it recovers.

A CLOSER LOOK / 04

From the first input
to a useful outcome.

This sequence summarizes the project’s core idea. The interactive panel is a local visual study; use the linked repository or live service for the implemented project.

01 →

Watch health

Check configured KNX interfaces while keeping one stable endpoint for Home Assistant.

02 →

Switch paths

When the active path fails, select an available backend interface and continue routing.

03 →

Recover primary

When the preferred interface returns, fail back while maintaining the stable endpoint.