Skip to content
1HOME.FRDistributor in France

Integrations · Hub

Integrations: Matter, Apple Home, Google Home, Alexa and your system

A wired installation does not speak the language of voice assistants, and that is not a flaw: they were designed for different jobs. The gateway is the translator. This page explains how, and lists every combination we document.

Ecosystems03
Platforms06
Updated08 / 2026

A wired bus carries short telegrams between board modules. A voice assistant thinks in « accessories »: a lamp, a blind, a thermostat, each with a normalised set of states. Nothing links the two spontaneously.

The gateway does that job: it reads the structure of your installation, converts it into objects the platforms understand, and passes commands back the other way.

01How a gateway works, in four steps

  1. Reading: the gateway imports the installation configuration.
  2. Translation: each function becomes a normalised object type.
  3. Publication: those objects are exposed to one or more platforms, directly or through Matter.
  4. State feedback: a light switched on from the wall shows as on in the app.

02What stays local, what goes through the cloud

FunctionLocalCloud
Wall switches and bus automationsAlwaysNever
App on the home networkYesNo
Voice controlNoYes
Access from outsideNoYes

03Documented combinations

04Who does what: Matter, Apple Home, Google Home, Alexa

PlatformNatureHardware required
MatterInteroperability standard (CSA)Any compatible controller
Apple HomeApple ecosystemA home hub (HomePod or Apple TV) for remote access and automations
Google HomeGoogle ecosystemA Google account; a Nest speaker or display for voice
Amazon AlexaAmazon ecosystemAn Amazon account; an Echo speaker for voice
SmartThingsSamsung ecosystemA compatible hub depending on the integration path
Home AssistantOpen, self-hosted platformA host machine maintained by the user

The right-hand column is the one people discover too late. Apple's home hub in particular is a real cost, and it must appear in the quote rather than in a surprise at commissioning.

05Choosing a platform when starting from scratch

  • Look first at the phones in the household: it is the criterion that matters most day to day.
  • If the household is mixed, go through Matter and its multi-admin rather than arbitrating.
  • Count the ancillary hardware: an Apple home hub or a speaker is not free.
  • Check which object types the platform can represent before promising a use case.

05Choosing a platform: the questions that actually matter

Most platform comparisons are written around features. In practice the choice is settled by four constraints that have nothing to do with feature lists.

  • What the household already owns. Phones, speakers and displays already in the house weigh more than any specification sheet.
  • Which hardware the platform requires on its side — a home hub, a speaker, an account — because that is a real cost added to the gateway.
  • What happens without an internet connection, function by function. Wall switches and bus automations keep working; voice and remote access do not.
  • Whether you want to keep more than one platform at the same time, which is precisely what the Matter multi-admin path allows.

None of these four is a reason to change the gateway. They decide which page of this matrix applies to you, not which product you buy — the product is settled by the system already in place.

Frequently asked questions

Can an integration disappear with an update?

It happens: consumer platforms move fast. That is a strong argument for Matter exposure, which relies on a public specification rather than a proprietary integration.

Does Matter replace KNX?

No. Matter is an interoperability language between platforms; KNX is a building infrastructure with actuators in the board. Matter does not command an actuator on a wired bus — the gateway does.

Can several voice assistants be used at once?

Yes — that is exactly what Matter multi-admin brings: one object can belong to several ecosystems in parallel.