Hi all,
I’m Thomas, I plan and build smart homes in Austria, mostly Loxone and Home Assistant side by side. Over the last months I’ve been extending the PyLoxone integration into something I use on customer installations, and I’d like to share it. It’s open source and installed via HACS as a custom repository.
**Repo:** GitHub - smartmacherei/Loxone-Integration · GitHub
**Current release:** v1.7.1
## What it does differently from PyLoxone
**Devices instead of a flat entity list.** Physical inputs and outputs are discovered from the Miniserver program itself (the `.Loxone` project), not only from the visualization. A Tree touch switch, a wallbox, an Air door contact each become one device with their entities under it. Battery and online state are created as diagnostic entities. Nothing has to be added to the Loxone visualization first.
**Real-time values over UDP (way 2).** With one option the integration writes UDP logger references into the Miniserver program for the discovered terminals, uploads the program and restarts the Miniserver. From then on the Miniserver pushes changes instantly; Home Assistant only polls as a fallback. Before touching anything it downloads the current program from the Miniserver, verifies a backup on disk (an openable `.Loxone` project plus the full archive) and refuses to upload if the backup can’t be verified. Gateway/Client systems are supported: each Miniserver gets its own logger and heartbeat, the archive is uploaded to the gateway only. Verified on a four-Miniserver installation.
**HA → Loxone with a label (way 3, new in 1.7).** Give any entity the label `loxone`, press the button “Apply HA values to program”, and the integration creates a virtual UDP input “HA Werte” in the Miniserver with one command per value. From then on every state change is sent as a UDP datagram, plus all values every 5 minutes. A `climate` entity gives four inputs (mode index, current temperature, target temperature, action), sensors and switches one each, select entities the option index. Nothing changes in the program unless you press the button; a diagnostic sensor shows what is pending.
*Rendered from the real entity names and icons, not a live capture.*
**Lighting moods as effects.** A Loxone lighting controller is a light entity, its moods are the effect list.
**Diagnostics that help.** A “Check connection” button tests web port, login, FTP/TLS and UDP reception without uploading anything. The diagnostics download includes the program archive (treat it as confidential, it contains your project). Contacts follow the Loxone status texts, so a door contact labelled “1 = closed” in Config shows closed in HA.
**Lower load.** The old `loxone_event` bus event is gone (it filled recorders with hundreds of thousands of rows); state updates go through an internal dispatcher. Disabled entities are not polled, device internals are read every 4 hours.
## Install
1. HACS → Custom repositories → `https://github.com/smartmacherei/Loxone-Integration\`, category Integration.
2. Download “Loxone”, restart HA.
3. Settings → Devices & services → Add integration → Loxone. Host, HTTP port (default 80), user, password. Use a user that may read the program.
4. Way 1 (reading Loxone) is always on. Way 2 (UDP real-time) and way 3 (HA → Loxone) are options you switch on deliberately, because they change the Miniserver program. Read the disclaimer in the README first and keep your own backup of the project.
It uses the same `loxone` domain as PyLoxone, so install only one of the two.
## Honest limits
- Way 3 has been verified on a real four-Miniserver installation only since today; treat it as new.
- Automatic program editing is tested with Loxone Config 16.x and 17.x archives. Other formats are left untouched.
- Physical output switches write straight to the terminal. If the Loxone program also drives that output, disable the entity.
- Values to Loxone are numbers only; text states are listed as unsupported.
## Why I built it
Loxone runs the base automation in the houses I install: light, shading, room control, alarm. Home Assistant is the shared surface on top, for PV, heat pump, wallbox, cameras and everything Loxone doesn’t know. The integration is the bridge between the two, and I wanted it to work without touching the Loxone visualization for every single input.
Feedback, bug reports and program archives from other Config versions are very welcome, best as GitHub issues (the diagnostics download tells me most of what I need).
Thomas