Loxone vs Others
Inteto is centred on Loxone. This page explains how we think about Loxone, AV platforms, consumer smart home ecosystems and flexible systems such as Home Assistant and Homey. The aim is not to make every platform sound equal. It is to show why Loxone is usually the right backbone for core building automation, with other technologies used as supporting layers where they make sense.
The 60 second answer
“Others” covers several very different categories. For our projects, the default starting point is Loxone for the building backbone. AV platforms, voice assistants and flexible integration tools can then be considered for specific layers, rather than being treated as direct substitutes for the whole system.
Loxone is the building automation backbone
- Designed around lighting, heating/cooling, shading, energy and everyday building behaviour
- Local operation for core functions, helping reduce reliance on cloud services
- Well suited when the system must be commissioned, supportable and easy to hand over
AV platforms focus on experience
- Systems such as Control4 are often strong where cinema, distributed audio/video and media control are the centre of the brief
- They can be a good fit as a dedicated entertainment layer in larger projects
- In many homes, the best answer is the right platform in the right layer
Consumer ecosystems are convenience layers
- Apple Home, Google Home and Alexa are useful for voice control, app access and simple smart devices
- They are usually better as front ends than as the core logic for the building
- Good for convenience; not always ideal for critical lighting, heating or shading behaviour
Flexible platforms are integration layers
- Home Assistant, Homey and similar systems are powerful for custom integrations and technical owners
- They can solve niche problems and connect awkward devices
- The trade off is supportability, maintenance and clean handover for less technical users
Compare by layer, not by logo
Most poor smart home decisions come from forcing one product to do every job, or from putting a convenience layer in charge of critical building behaviour. A more resilient design starts with Loxone as the building layer, then separates the experience, convenience and integration layers around it.
Building layer
- Typical focus: lighting, climate, shading, access, energy and reliability
- Good fit: Loxone automation, designed and commissioned as infrastructure
- Success measure: the property behaves properly without constant app use
Experience layer
- Typical focus: cinema, audio/video, media scenes and source control
- Good fit: AV focused control platforms where entertainment is the main brief
- Success measure: “watch” and “listen” journeys feel seamless
Convenience layer
- Typical focus: voice commands, mobile app access and simple smart devices
- Good fit: Apple Home, Google Home, Alexa and similar ecosystems
- Success measure: easy control without making the building dependent on voice or cloud services
Integration layer
- Typical focus: niche devices, dashboards, data, automations and custom workflows
- Good fit: Home Assistant, Homey and middleware where flexibility matters
- Success measure: added capability without creating an unsupported maintenance burden
Where Loxone is often a strong fit
If you want the building to behave predictably without constant tinkering, Loxone is our preferred backbone.
- Lighting scenes that are instant and reliable
- Climate strategies designed to manage unnecessary runtime without comfort whiplash
- Shading logic to prevent glare and overheating
- Energy visibility that makes usage easier to understand and investigate
- Guest friendly operation with sensible wall controls
This is the difference between a clever demo and a system you can operate every day.
Where AV focused platforms are often a strong fit
If the brief includes serious entertainment requirements, a dedicated AV control platform may be a useful layer alongside Loxone. If the brief is purely AV focused and not really a Loxone automation project, we would rather say that early than pretend otherwise.
- Multi room AV orchestration and polished media journeys
- Home cinema workflows where source, screen, lighting and audio need to feel effortless
- Broad entertainment ecosystems with strong AV integration options
- One interface that prioritises watch/listen comfort
Control4 is a known example in this category. Our position is not anti-Control4; it is clear that Loxone should be as the building automation backbone, with the right specialist tools used only where they genuinely improve the design.
Where Apple Home, Google Home, Alexa, Home Assistant and Homey fit
These are not bad options. They are just different categories of product. The commercial risk is using a convenience or hobbyist platform as if it were building infrastructure.
Apple Home, Google Home and Alexa
Useful as front end layers for voice, app control and simple smart devices. If the customer already has Echo, Google Nest, HomePod or Siri in the property, these can often be considered as convenient ways to request scenes, lighting, comfort or shading where supported.
The key is not to confuse voice control with building control. Smart speakers are good for commands; Loxone is better for the decisions and local logic behind them.
Home Assistant, Homey and similar systems
Excellent for technically confident owners who want deep customisation, experimentation and niche integrations. They can also be useful as middleware. But they are not usually the cleanest handover proposition for a less technical homeowner or workplace client.
Loxone
Well positioned as a stable automation backbone: planned, wired where it matters, commissioned professionally and designed to keep core building behaviours local and predictable.
Our view: voice assistants can sit on top, Home Assistant style platforms can help with niche integrations, and Loxone should carry the core building logic when reliability, supportability and handover matter.
For Apple households, HomeKit/Siri support can be part of the conversation on compatible current Loxone systems. For Alexa and Google households, routes such as Matter or specialist bridge services can be assessed during scoping rather than assumed blindly.
A practical decision framework
Answer these honestly and the right architecture becomes clearer. For Inteto, that usually means centred on Loxone, then supporting layers where required.
Start with Loxone if…
- Lighting, climate, shading, heating/cooling and energy are the core brief
- You want the main building behaviours to work locally and predictably
- You need a system that can be commissioned, documented and supported long term
Add a dedicated AV layer if…
- Multi room AV, home cinema and media journeys are the core brief
- You are investing heavily in AV distribution, sources and entertainment rooms
- You want a polished entertainment-first control layer
Use consumer ecosystems if…
- You want voice control, mobile app access and simple scene requests
- The devices involved are non-critical and easy to replace
- You accept that cloud services and vendor changes can affect behaviour
Use flexible platforms if…
- You need custom dashboards, awkward integrations or enthusiast-level control
- There is a clear owner for maintenance and updates
- The extra flexibility is worth the extra governance
Our default architecture: Loxone for the dependable building backbone, then carefully chosen voice, AV or integration layers where they add value. We are not positioning ourselves as a general multi-platform installer. The goal is a supportable Loxone system with the right technology in the right layer.
Want a straight answer?
Tell us what matters most: comfort, resilience, AV experience, energy visibility and long term supportability. We’ll recommend an architecture centred on Loxone that fits the building, not the trend.