TopherMayor/hermes-ice
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
main
hermes-ice/homelab/concepts/matter-multi-fabric.md
Hermes Agent e4d91aadf9 Initial commit: homelab infrastructure wiki 
- Full Obsidian vault content
- Host configs (ice, grizzley, ubuntu, proxmox, truenas, panda, hyte)
- Media stack documentation
- Traefik HA setup
- Automation scripts
- Bachelor party planning
2026-05-24 16:08:40 -07:00

9.6 KiB
Raw Permalink Blame History

title, created, updated, type, tags, confidence, sources
title created updated type tags confidence sources
Matter Multi-Fabric Architecture 2026-05-10 2026-05-10 concept
matter
thread
smart-home
iot
ecosystem
concept
hub
high
UniFi Network clients
HA integrations
network-device-census

Matter Multi-Fabric Architecture

The smart home uses Matter's native multi-admin capability to unify devices across HA, Apple, Google, and Alexa ecosystems. Home Assistant is the central controller; all other ecosystems are secondary fabrics.

Why Multi-Fabric?

Matter multi-admin allows a single device to be commissioned into multiple fabrics simultaneously:

  • Same lock/switch/light appears in Apple Home, Google Home, Alexa, AND Home Assistant
  • Native Matter protocol — no cloud bridges or vendor workarounds
  • Each ecosystem gets independent control; device responds to commands from any fabric
  • Most Matter devices support 4–5 simultaneous fabric memberships

Fabric Topology

┌───────────────────────────────────────────────────────────┐
│                     MATTER END DEVICES                     │
│  Aqara Zigbee devices (via M3 bridge) │ Nest Thermostat   │
└──────┬──────────┬──────────────┬───────────┬──────────────┘
       │          │              │           │
 ┌─────▼───┐ ┌───▼────┐ ┌──────▼───┐ ┌─────▼──────┐
 │ Fabric 1 │ │Fabric 2│ │ Fabric 3 │ │  Fabric 4  │
 │   HA     │ │ Apple  │ │  Google  │ │   Alexa    │
 │ (ZBT-2) │ │(AppleTV)│ │  (Nest)  │ │ (4× Echo)  │
 └─────┬───┘ └───┬────┘ └────┬─────┘ └─────┬──────┘
       │          │           │              │
       ▼          ▼           ▼              ▼
 ┌──────────────────────────────────────────────────────┐
 │            Thread Network (single mesh)               │
 │       Thread Border Routers share credentials         │
 │  ZBT-2 (primary) │ Aqara Hub M3 │ Apple TV │ Echo    │
 └──────────────────────────────────────────────────────┘

Ecosystem Controllers

Fabric 1: Home Assistant (Primary)

  • Controller: home-assistant-connect-zbt-2 on panda (HAOS)
  • Thread role: Primary OTBR — owns Thread network credentials
  • Network: 192.168.30.196 (wired), 192.168.30.12 (WiFi)
  • Access: https://ha.tophermayor.com (via Traefik on ubuntu)
  • Capabilities: Full automation, scripts, scenes, voice pipeline, all integrations
  • Devices seen: Everything (central hub)

Fabric 2: Apple Home

  • Controller: Apple TV 4K gen 3 (Office, WiFi VLAN 30)
  • Thread role: Potential OTBR
  • HA integration: apple_tv
  • Capabilities: Siri voice, Home app, automations
  • Devices: Aqara devices via Matter multi-admin through aqara-hub-m3

Fabric 3: Google Home

  • Controller: Nest Thermostat (192.168.30.179, WiFi VLAN 30)
  • HA integration: nest
  • Capabilities: Google Assistant voice, Google Home app
  • Devices: Nest Thermostat (native), Aqara devices via Matter multi-admin
  • Note: Consider adding Nest Hub as dedicated controller + Thread BR

Fabric 4: Amazon Alexa

  • Controllers: 4× Echo Dot
    • Office Echo (192.168.30.150)
    • Kitchen Echo (192.168.30.26)
    • Bedroom Echo (192.168.30.170)
    • Garage Echo (192.168.30.68, unnamed in UniFi)
  • HA integration: alexa_devices (cloud)
  • Capabilities: Alexa voice, routines, "Everywhere" speaker group
  • Thread role: Echo Dots (gen 5) can act as Thread BRs

Hub-to-Device Mapping

Which devices sit behind which hub, and how they reach each ecosystem:

Direct WiFi Devices (no hub needed)

Device IP HA Integration Apple Google Alexa
Nest Thermostat 192.168.30.179 nest — ✓ Native —
Office Echo 192.168.30.150 alexa_devices — — ✓ Native
Kitchen Echo 192.168.30.26 alexa_devices — — ✓ Native
Bedroom Echo 192.168.30.170 alexa_devices — — ✓ Native
Garage Echo 192.168.30.68 alexa_devices — — ✓ Native
Apple TV 4K TBD apple_tv ✓ Native — —
Shelly 1PM (bedroom) 192.168.30.75 shelly ‡ Bridge ‡ Bridge ‡ Bridge
Shelly 1PM (office) 192.168.30.7 shelly ‡ Bridge ‡ Bridge ‡ Bridge
Govee Floor Lamp L 192.168.30.91 govee_light_local ‡ Bridge ‡ Bridge ‡ Bridge
Govee Floor Lamp R 192.168.30.217 govee_light_local ‡ Bridge ‡ Bridge ‡ Bridge
Govee unnamed ×2 .34, .242 govee_light_local ‡ Bridge ‡ Bridge ‡ Bridge
TP-Link HS103 ×3 .116, .165, .210 tplink ‡ Bridge ‡ Bridge ‡ Bridge
TP-Link KP115 192.168.30.193 tplink ‡ Bridge ‡ Bridge ‡ Bridge
Levoit Purifier 192.168.30.21 vesync ‡ Bridge ‡ Bridge ‡ Bridge
LG OLED TV 192.168.30.79 webostv ‡ Bridge ‡ Bridge ‡ Bridge

‡ Requires HA Matter Bridge — not yet configured.

Aqara Zigbee Devices (via aqara-hub-m3 Matter bridge)

All Zigbee devices are managed by ZHA via home-assistant-connect-zbt-2. The Aqara Hub M3 can additionally bridge them to Apple/Google/Alexa via Matter.

Device Location Zigbee Parent HA (ZHA) Apple (M3) Google (M3) Alexa (M3)
Light Switch H2 US Baby Room ZBT-2 ✓ † † †
Light Switch H2 US Front Door ZBT-2 ✓ † † †
Light Switch H2 US Entrance ZBT-2 ✓ † † †
Light Switch H2 US 1st Floor ZBT-2 ✓ † † †
Ceiling Light 36W Baby Room ZBT-2 ✓ † † †
Smart Lock U100 Front Door ZBT-2 ✓ † † †
Motion Sensor P1 Living Room ZBT-2 ✓ † † †
Door/Window Sensor Rooftop ZBT-2 ✓ † † †
Vibration Sensor T1 Rooftop ZBT-2 ✓ † † †
STARKVIND Purifier TBD ZBT-2 ✓ † † †

† Pending Aqara Hub M3 Matter bridge commissioning into Apple/Google/Alexa fabrics.

Aqara WiFi Devices (direct)

Device IP HA Integration Apple Google Alexa
Hub M3 192.168.30.59 matter, zha † † †
Camera Hub G3 192.168.30.113 — — — —
Doorbell G410 192.168.30.118 — — — —

† Hub M3 is the bridge device — commissioning it into other fabrics exposes all bridged Zigbee devices.

Thread Border Router Strategy

All border routers must join a single Thread mesh with matching credentials:

Border Router Host Status Role
home-assistant-connect-zbt-2 OTBR panda ✅ Active Primary — owns credentials
aqara-hub-m3 Bedroom ⚠️ Verify credentials match Secondary BR
Apple TV 4K gen 3 Office Potential OTBR Not yet configured
Echo Dot (gen 5?) Various Potential OTBR Not yet configured

Rule: Export Thread credentials from ZBT-2 OTBR. Ensure all other BRs join same network (Network Key, PAN ID, channel).

Non-Matter Devices → HA Matter Bridge

HA can expose non-Matter devices to other ecosystems via Matter Bridge:

Device Type Protocol HA Integration Bridge Status
Shelly 1PM Gen4 ×2 WiFi shelly ⬚ Not configured
Govee lights ×5 WiFi/LAN govee_light_local ⬚ Not configured
TP-Link Kasa ×4 WiFi tplink ⬚ Not configured
VeSync purifier WiFi/Cloud vesync ⬚ Not configured
LG TV ×2 WiFi webostv ⬚ Not configured
IKEA purifier Zigbee ZHA ⬚ Not configured

Commissioning Checklist

When adding a new Matter device:

  1. Commission into HA first (Settings → Devices & Services → Matter → Add Device)
  2. Get multi-admin pairing code from HA device info
  3. Commission into Apple Home using pairing code
  4. Commission into Google Home using pairing code
  5. Commission into Alexa using pairing code

For non-Matter devices:

  1. Add to HA via native integration
  2. Enable HA Matter Bridge in HA Settings → Matter → Bridge
  3. Commission HA Bridge into target ecosystems

Relationships

Open Tasks

  • Verify Thread credentials match between ZBT-2 and Aqara Hub M3
  • Commission Aqara Hub M3 into Apple Home via Matter
  • Commission Aqara Hub M3 into Google Home via Matter
  • Commission Aqara Hub M3 into Alexa via Matter
  • Set up HA Matter Bridge for Shelly/Govee/TP-Link/VeSync/LG devices
  • Test multi-admin with Lock U100 across all 4 ecosystems
  • Consider adding Nest Hub for Google Thread BR
  • Evaluate Echo Dot Thread BR capability (gen 5 required)
Reference in New Issue View Git Blame Copy Permalink