Multi-Fabric Commissioning: Sharing PurpleAir Matterbridge with Apple Home and Google Home Concurrently¶
Note
Published: November 14, 2026
Authors: Written by Gemini 3.8 Flash, Co-Authored & Reviewed by Carlos Santos (@carlkidcrypto)
Estimated Reading Time: 5 minutes
Tags: PurpleAir • Matterbridge • Matter • Apple-Home • Google-Home • Multi-Fabric
Modern households rarely standardize on a single smart home ecosystem. One family member might check outdoor air quality on an iPhone using Apple Home, while another relies on Google Nest Hub displays in the kitchen or Home Assistant dashboards on a local tablet.
Before Matter, supporting multiple platforms required running redundant software bridges or relying on cloud-to-cloud connectors that introduced latency and privacy trade-offs. Matter solves this natively through Multi-Admin (also known as Multi-Fabric Commissioning).
With Multi-Admin, a single Matter node—such as purpleair-matterbridge—can belong to several independent cryptographic fabrics simultaneously. Each controller communicates directly with the bridge over your local IPv6 network, receiving real-time PM2.5, AQI, temperature, and humidity updates without a cloud relay.
In this tutorial, we will examine how Matter fabrics isolate credentials, walk
through pairing purpleair-matterbridge with Apple Home first, open an
Enhanced Commissioning Window to share the bridge with Google Home, and
troubleshoot multi-fabric mDNS and IPv6 networking.
How Matter Multi-Fabric Architecture Works¶
In the Matter specification, a Fabric is an isolated security domain sharing a common Root Certificate Authority (CA), Fabric ID, and operational keys. Every smart home ecosystem you use maintains its own independent fabric:
Fabric 1 (Apple Home): Managed by your Apple TV 4K or HomePod hub.
Fabric 2 (Google Home): Managed by your Google Nest Hub or Nest Wifi Pro controller.
Fabric 3 (Home Assistant): Managed by your local
python-matter-serverinstance.
When you pair purpleair-matterbridge with multiple ecosystems, the bridge
does not duplicate physical hardware or spin up separate processes. Instead,
the underlying Matterbridge runtime stores
separate Node Operational Credentials (NOCs) and Access Control Lists
(ACLs) inside its persistent ~/.matterbridge directory.
Each controller opens its own independent CASE (Certificate Authenticated
Session Establishment) subscription to the bridge. When PurpleAir telemetry
updates, purpleair-matterbridge broadcasts attribute change reports across
every active fabric subscription concurrently.
Prerequisites for Multi-Admin Operation¶
Before commissioning a second or third controller, verify your local network meets Matter’s transport requirements:
Local IPv6 Enabled: Matter mandates IPv6 link-local (
fe80::/10) and Unique Local Addressing (ULA) on the LAN. You do not need IPv6 from your ISP, but IPv6 must be enabled on your router and Docker host.Host Networking & mDNS: If deploying via Docker, always use
network_mode: hostso multicast DNS (mDNS on UDP port 5353) packets reach every controller on the subnet.Persistent Storage: Mount the
/root/.matterbridgevolume so fabric certificates and pairings survive container upgrades.
Step 1: Commission the Primary Fabric (Apple Home)¶
Start purpleair-matterbridge and inspect the startup logs or web UI
(typically http://<host-ip>:8283) to obtain the initial onboarding payload:
docker logs -f purpleair-matterbridge
Look for the initial QR code and the 11-digit manual pairing code:
[Matterbridge] QR Code: MT:Y.K9042C00KA0648G00
[Matterbridge] Manual Pairing Code: 3497-011-2983
Pair the bridge with your primary ecosystem first:
Open the Apple Home app on an iOS device on the same local Wi-Fi.
Tap + -> Add Accessory -> More options… -> My Accessory Isn’t Shown Here (or scan the QR code directly).
Enter the 11-digit manual pairing code.
Assign the bridged PurpleAir sensors to their rooms.
Once paired, the initial commissioning window closes automatically. Attempting to reuse the original printed QR code for Google Home will fail because the device is now commissioned and locked to Fabric 1.
Inspecting Active Fabrics & Subscriptions¶
You can verify that both Apple Home and Google Home hold active operational credentials on the bridge by checking the Matterbridge web dashboard or inspecting the console logs after a sensor poll cycle:
[Commissioning] Fabric 1: Apple Inc. (NodeID: 0x000000001A2B3C4D)
[Commissioning] Fabric 2: Google LLC (NodeID: 0x000000009F8E7D6C)
[AirQuality] Sensor 282168 updated: PM2.5=6.4 ug/m3 -> Notified 2 fabrics
Each fabric maintains isolated access control, meaning removing the bridge from Google Home later only revokes Fabric 2’s operational certificates while leaving Apple Home uninterrupted.
Troubleshooting Multi-Admin Pitfalls¶
When sharing a bridge across multiple vendors, keep these operational rules in mind:
Avoid Overlapping Commissioning Windows: Never trigger pairing mode on two controllers at the exact same moment. Wait until Fabric 2 completes PASE/CASE key exchange before opening another window for Fabric 3.
Verify mDNS Across VLANs: If your Apple TV and Google Nest Hub reside on different subnets or IoT VLANs, mDNS reflector rules must forward both
_matter._tcp(commissioned operational discovery) and_matterc._udp(commissionable discovery) records.Check Fabric Slot Limits: Matter 1.x devices guarantee support for at least 5 concurrent fabrics. Matterbridge handles this comfortably, allowing simultaneous pairing across Apple Home, Google Home, Alexa, and Home Assistant.
Summary & What’s Next¶
Multi-fabric commissioning turns purpleair-matterbridge into a universal local air quality hub. By leveraging Enhanced Commissioning Windows and local IPv6 subscriptions, every smart home controller in your household stays synchronized in real time without cloud dependencies.
In our next blog post, we will rotate back to ezsnmp, diving into real-time Quality of
Service (QoS) telemetry and auditing Differentiated Services (DiffServ) queue
drops using DIFFSERV-MIB.
Warning
AI-generated content may contain misinformation or mistakes. A human does review this, but we are only human.