Solutions · Loxone
1Home for Loxone: voice and Matter on your Miniserver
A Loxone Miniserver runs a house very well, but it remains a closed world as far as Apple Home, Alexa and Matter are concerned. A dedicated 1Home server reads its configuration and republishes its objects to those platforms, without touching your Loxone Config programming.
Loxone made a coherent choice: an integrated ecosystem, a single programming tool, a well-built app. The downside is familiar to every owner — as soon as you want to step outside the Loxone app, the path narrows.
The dedicated server exists to translate. It connects to the Miniserver on the local network, reads the structure of the house as it was programmed, and exposes it to consumer platforms. Loxone programming remains the only authority over the actuators.
01What 1Home adds to a Loxone Miniserver
The benefit is mostly a matter of reach: the same functions, but available from interfaces your occupants already use every day.
- Voice assistants: Alexa, Google Home and Apple Home receive Loxone rooms and objects as ordinary accessories.
- Matter exposure: the Miniserver becomes visible to any compatible controller, without relying on integrations added one by one.
- Multi-admin: several platforms in parallel — a household split between iPhone and Android no longer has to choose.
02Prerequisites and compatibility
Three things decide whether commissioning will go smoothly, and they are worth checking before ordering.
- The Miniserver generation and its software version: different generations do not expose the same network interfaces.
- Access to the Miniserver on the local network, with service credentials holding the required read rights.
- A clean Loxone configuration: badly named objects and fictitious rooms will appear as they are in Apple Home or Alexa.
03Commissioning: what is automatic, what is configured
Object discovery is automatic; the quality work is the filtering that follows. A well-programmed Loxone house easily exposes several hundred objects — publishing them all to Alexa produces an unusable list.
- Connect the 1Home server to the network and pair it with the Miniserver.
- Import the structure: rooms, categories, controllable objects.
- Select: publish only what makes sense by voice or in a third-party app.
- Rename in plain language — « parents' bedroom blind », not « VR2-C3 ».
- Run room-by-room acceptance, then pair the target platforms.
Allow half a day of integrator time for a house of average size, more if the Loxone configuration has to be tidied up first.
04Known limits on the Loxone side
- Composite Loxone objects — complex function blocks, multi-parameter control loops — do not always have an equivalent among the device types of Apple Home, Google Home or Matter: they are then exposed in simplified form, or not at all.
- Voice commands depend on an internet connection and on the assistant's service: an outage does not stop the house, it stops the voice.
- Loxone firmware updates can change interfaces: plan a verification after every major update.
The Loxone combinations we document page by page are listed on the integrations hub — in particular Loxone and Apple Home and Loxone to Matter.
Frequently asked questions
Does Loxone work with Apple Home?
Not natively for the whole set of objects. That is exactly the role of a dedicated 1Home server: translating Miniserver objects into accessories the Home app can understand, within the device types Apple recognises.
Is a Loxone Cloud subscription required?
Loxone remote access and 1Home remote access are two different paths. The conditions applying to each must be checked against both manufacturers' documentation before ordering; we restate them in the quote.
Can I keep the Loxone app in parallel?
Yes. Nothing is exclusive: the Loxone app keeps working and the new interfaces are added alongside it.