1Home MatterPro: your installation exposed to Matter

01What a Matter bridge is, and what it changes

A bridge declares to a Matter network a list of devices which, physically, are something else: your KNX circuits or Loxone objects, translated.

1. The bridge reads the wired installation and derives a list of objects.
2. It publishes them as normalised Matter device types.
3. Matter controllers discover them like any off-the-shelf accessory.
4. Each controller drives them — without the wired installation being modified.

02Exposed device types and limits of the standard

This is the honest point to know before buying: Matter covers common categories very well and specialised building functions far less. The standard evolves by versions, and what is missing today may arrive tomorrow.

• Well covered: switched and dimmed lighting, sockets, blinds and shutters, sensors, temperature setpoints.
• Partly covered: complex control loops, advanced scenes, specific comfort equipment.
• Out of scope: anything with no normalised device type in the current version of the specification.

03Multi-admin: several platforms in parallel

This is the most concrete benefit for a real household. Multi-admin lets the same Matter device belong to several ecosystems at once: the iPhone on one side, Android on the other, with no duplicate hardware and no family arbitration.

04Network prerequisites

Matter is a modern IP protocol: it assumes a healthy local network, which is not always the case in homes wired ten years ago.

• IPv6 active on the local network — the most frequently forgotten prerequisite.
• Working multicast discovery: beware misconfigured VLANs and filtering access points.
• A compatible Matter controller on the platform side.
• A Thread border router only if you add Thread equipment — the bridge itself does not necessarily depend on one.

05What Matter does not solve

The standard is genuinely useful, and it is also routinely oversold. Knowing its limits before ordering is what stops a bridge from being blamed for something it was never meant to do.

• Matter normalises common device types. A function with no equivalent in the standard does not become visible just because a bridge is present.
• It does not replace the bus. Wired automations and wall switches remain the reliable layer, and that is a feature, not a shortcoming.
• It does not remove platform-side hardware requirements: a controller is still needed on each ecosystem you want to use.
• It does not freeze the situation. The list of supported types evolves with the standard, so what is out of scope today may not be tomorrow.

Read the other way round, the bridge is worth exactly this: it stops you having to choose one platform for the next ten years. That is the decision it buys back, and it is a decision worth not making too early.

Frequently asked questions