Aqara Matter Advanced Bridging: Scene & Signal Sync with Home Assistant
If you’ve been running an Aqara hub as a Matter bridge in Home Assistant, you already know the basics: pair the hub via Matter, watch a handful of your Aqara devices appear as native HA entities, control them locally. That works well for devices Aqara has mapped to Matter device types.
But it doesn’t cover everything. Your IR blaster sequences, camera pan-tilt commands, Aqara Cube gestures, door lock fingerprint events — none of those have Matter equivalents, so they stay locked inside the Aqara Home app. Until the Aqara Matter 高阶桥接 (Advanced Matter Bridging) update changed that.
This guide covers what Advanced Bridging actually does, which hubs support it, and exactly how to configure 场景同步 (Scene Synchronization) and 信号同步 (Signal Synchronization) so they appear as usable entities in Home Assistant.
What is Aqara Matter Advanced Bridging?
Standard Matter bridging maps physical Aqara devices — sensors, switches, locks — to their Matter equivalents and exposes them in HA. You get entities that mirror real hardware.
Advanced Bridging is different. It doesn’t expose new hardware. It exposes two things that previously had no representation outside the Aqara ecosystem:
Scene Sync bridges an Aqara Home scene (a saved action sequence you’ve set up in the app) into HA as a virtual switch or plug entity. Activating that switch fires the scene. This matters most for devices that Aqara can control but that have no Matter equivalent — IR-controlled TVs and air conditioners, camera pan-tilt positions, anything you’ve configured as a scene inside Aqara Home.
Signal Sync bridges Aqara automation condition events — camera gesture recognition results, door lock fingerprint identifications, Aqara Cube actions, voice assistant triggers — into HA as virtual occupancy or binary sensor entities. When the condition triggers, the sensor state changes. HA automations can react to that state change.
Both features communicate over Matter’s local encrypted channel. No Aqara account credentials are involved after initial setup, and no data passes through Aqara’s servers to reach HA. The Matter path is end-to-end local, which is the whole point.
Aqara announced the feature globally on 9 April 2025. Accessing it requires Aqara Home App V5.1.4 or later and hub firmware V4.3.4 or later. Chinese tech media (IT之家 (ITHome), Tencent News) covered the rollout ahead of much of the English-language press, which is part of why many current English guides are thin on implementation specifics.
Supported Hubs and Firmware Requirements
Advanced Bridging launched on the Hub M3. Since then Aqara has expanded it to a broader set of hubs:
- Aqara Hub M3
- Hub M1S / M1S Gen 2
- Hub M2
- Hub E1
- Hub M100
- Camera Hub G5 Pro
- Camera Hub G3
- Doorbell Camera Hub G410
All require hub firmware V4.3.4 or later and Aqara Home App V5.1.4 or later. If your hub is on that list and both the firmware and app are current, the feature is accessible in the Aqara Home App settings.
One important caveat about the Camera Hub G3: after successful Matter pairing, the camera stream becomes unavailable. This is a known limitation documented in Chinese community tutorials. The hub is paired and functional as a Matter bridge, but you lose the camera feed in Aqara Home. If you need both the camera function and Advanced Bridging simultaneously, use the Hub M3 as your Matter gateway instead and keep the G3 as a camera-only device.
For the base Matter bridge setup this guide builds on, see our Aqara Hub M3 Matter bridge guide for Home Assistant.
Why This Matters for Local-First Home Assistant Setups
The most common frustration I hear from people running Aqara in HA is the gap between what they can do in the Aqara Home app and what they can automate in HA. The Aqara app has richer device support — particularly for IR-controlled appliances and camera functions — but the automations that run there are cloud-dependent. Move a trigger into HA, and you get local execution but lose access to those device types.
Advanced Bridging closes a specific slice of that gap. The Aqara app still handles the device control logic (firing the scene, interpreting the gesture); HA gets the signal that something happened, or the ability to trigger that scene. The handoff happens locally over Matter.
A concrete example from the Home Assistant community: the Aqara Cube T1 Pro has six gesture types (rotate, flip, shake, tap, push, hold). Cube gestures do not map to any Matter entity. But with Signal Sync, each gesture becomes a binary sensor state change in HA. You can build an automation that dims the lights on clockwise rotate, skips a media player track on flip-to-side, and runs a scene on shake — and that automation runs locally in HA, not in Aqara’s cloud. The Cube gesture is the trigger; HA is the controller.
This is meaningfully different from the cloud-dependent Aqara integration, where HA polls Aqara’s servers and actions have latency. With Matter, the signal travels hub-to-HA-controller over your LAN. I’ve run this pattern for a few weeks and gesture response in HA feels indistinguishable from a native Zigbee device trigger.
If you run your hub on a segmented IoT network, our Aqara and Xiaomi IoT VLAN guide for Home Assistant covers the firewall rules that keep Matter traffic flowing.
How to Set Up Scene Synchronization
Prerequisites
Your Aqara hub must already be added to Home Assistant as a Matter bridge. If it isn’t, do that first before attempting any Advanced Bridging configuration.
If you are setting up a hub as a Matter bridge for the first time, our Aqara Hub M100 Home Assistant Matter guide walks through the pairing flow.
The scenes you want to sync must already exist in Aqara Home. You cannot create new Aqara scenes from within HA — you build the scene in the Aqara app, then bridge it.
Steps in Aqara Home App
- Open Aqara Home App.
- Tap your profile picture (top-left corner) to open the Profile menu.
- Select “Connect to Ecosystems.”
- Tap “Home Assistant.”
- Under Home Assistant, tap “Scene Synchronization.”
- Select the scenes you want to expose. You can select multiple.
- Tap “Add to Matter.”
The app will sync the selected scenes to the Matter bridge. After a few seconds, new entities should appear in HA.
What Appears in Home Assistant
Scene Sync creates a virtual switch entity (HA may display it as a plug, depending on the Matter device type Aqara uses). The entity name will match your Aqara scene name. Turning the entity “on” fires the scene. Turning it “off” does nothing — scenes are one-shot triggers, not stateful.
Don’t let the plug/switch entity type confuse you. It’s not a real switch. It’s a trigger wrapped in the closest available Matter container. The HA community threads have several posts from people puzzled by why their “smart plug” doesn’t show power consumption — it’s because it isn’t one.
Using a Scene in an HA Automation
Once the entity exists, you can use it in an automation like any switch:
service: switch.turn_on
target:
entity_id: switch.aqara_scene_evening_lights
Or trigger it from a button press, a time condition, or any other HA automation trigger. The scene fires locally through the Matter bridge — no cloud hop.
How to Set Up Signal Synchronization
What Signal Sync Can Bridge
Signal Sync covers Aqara automation condition events that have no native Matter representation. The supported signal sources at launch include:
- Camera gesture recognition (from supported Aqara cameras)
- Door lock fingerprint identification events
- Aqara Cube gesture actions (rotate, flip, shake, tap, push, hold)
- Voice assistant trigger events
Steps in Aqara Home App
- Open Aqara Home App.
- Tap Profile → Connect to Ecosystems → Home Assistant.
- Tap “Signal Synchronization.”
- Select the signals you want to expose.
- Tap “Add to Matter.”
What Appears in Home Assistant
Signal Sync creates virtual occupancy sensors or binary sensors in HA, depending on the signal type. When the triggering event occurs — a Cube gesture, a fingerprint scan, a camera gesture — the sensor state changes to “detected” (occupied/on). HA automations can use that state change as a trigger.
The sensor will return to “clear” after a short period. The duration isn’t configurable from the HA side; it’s determined by the Aqara firmware.
Concrete Example: Aqara Cube T1 Pro Gestures to HA Automations
The Cube T1 Pro has multiple distinct gestures. With Signal Sync, each gesture maps to a separate binary sensor entity. An automation built around the “rotate clockwise” sensor trigger, for example, can control a media player volume or a light brightness with no cloud dependency:
alias: Cube Clockwise - Volume Up
trigger:
- platform: state
entity_id: binary_sensor.aqara_cube_rotate_cw
to: "on"
action:
- service: media_player.volume_up
target:
entity_id: media_player.living_room
The Cube itself connects to the Aqara hub via Zigbee. The hub interprets the gesture, fires the signal over Matter, HA sees the sensor state change. All local.
Known Limitations and Gotchas
The Ghost Device Problem
This one has burned a few people in both the English and Chinese-language HA communities. When you remove a previously paired Matter device from HA (either a scene switch or a signal sensor), the entity often persists in HA as unavailable rather than disappearing cleanly. This happens because the Matter Server doesn’t always flush stale nodes on removal.
The resolution requires a full Matter Server reinstallation and HA restart. Partial fixes (restarting only the Matter integration, or removing and re-adding the Aqara hub) don’t reliably clear the ghost devices. If you’ve accumulated several unavailable Matter entities after iterating on your scene and signal setup, that’s the fix.
Camera Hub G3 Stream Loss
As noted in the supported hubs section: using the Camera Hub G3 as your Matter gateway causes the camera stream to become unavailable after pairing. The workaround is to use a Hub M3 instead if you need camera function alongside Advanced Bridging. The G3 continues to work as a Matter bridge for other device types — you just lose the camera feed.
The Hub Must Stay Online in Aqara Home App
This is perhaps the least obvious requirement. The Aqara hub must remain active and connected in the Aqara Home App for Advanced Bridging to function. If you’ve set up the hub in Matter-only mode and removed it from the Aqara Home App, the Advanced Bridging features won’t work. The scenes and signals live in the Aqara ecosystem; the bridge is exactly that — a bridge, not a replacement.
This also means if Aqara’s servers go down, your ability to modify or add scenes and signals is affected. The Matter communication itself (executing an existing scene, responding to an existing signal) remains local. But building new bridges requires the Aqara app to be functional.
Device Scope
Advanced Bridging doesn’t help with standard Aqara Zigbee sensors. Those devices pair natively as Matter bridged devices when the hub is added to HA. Advanced Bridging is specifically for the gap cases: IR-controlled appliances, camera functions, gesture events, lock fingerprint events. Don’t expect it to change anything about your door sensors or temperature sensors — those already work directly.
Advanced Bridging vs. HomeKit Controller: Which Should You Use?
This comes up often enough to address directly. There are two common local-first paths for Aqara in HA: Matter bridging and the HomeKit Controller integration. Both are fully local. They serve different needs.
For the HomeKit-side alternative, see our explainer on Aqara HomeKit mode and local automations.
Use Matter + Advanced Bridging when:
– You want a single integration covering both native Matter devices and bridged scenes/signals
– You’re not running an Apple Home setup and don’t have HomeKit accessories
– You want the Matter path’s entity model (consistent device types, standard HA entity behavior)
– You need to bridge IR-controlled appliance scenes or Cube gesture signals
Use HomeKit Controller when:
– You’re already in the Apple HomeKit ecosystem and want HA to shadow your Apple Home setup
– You use HomeKit automations alongside HA automations and want them to stay in sync
– Your hub is the Hub M2, where the Matter entity coverage is thinner than HomeKit Controller’s (see our Aqara Hub M2 vs M3 comparison for Home Assistant)
– You prefer not to deal with Matter Server and its occasional stability issues (the ghost device bug, for example, is Matter-specific)
There’s no strong reason to run both simultaneously on the same hub. Pick one path per hub and keep it consistent. Mixed configurations produce confusing duplicate entities and complicate troubleshooting.
Is This Actually Local?
A question I see repeatedly in V2EX and HA community threads: users who moved from the Xiaomi cloud integration are rightly skeptical of any Aqara feature that still requires the Aqara Home app. Does the Matter path phone home?
The short answer: Matter communication between the hub and HA is local end-to-end encrypted traffic on your LAN. No Aqara account credentials or cloud sync are required for the Matter controller (HA) to communicate with the Matter bridge (your hub). Devices remain controllable during internet outages.
The longer answer: the Aqara Home app itself does connect to Aqara’s servers for hub management, OTA updates, and account sync. The scenes you build in the app are stored in Aqara’s cloud, not locally on the hub. If Aqara’s infrastructure goes down for an extended period, you can’t add or modify scenes — but you can still execute existing ones via the Matter bridge.
This is a reasonable tradeoff for most setups. If you need complete independence from Aqara’s infrastructure, the HomeKit Controller path with local automations in HA gets you closer — but even that path requires the Aqara app for initial hub configuration.
Run a packet capture if you want to verify the traffic profile on your own setup. The DNS check approach from our IoT VLAN guide applies here: watch for outbound connections to Aqara domains during Matter-triggered scene executions, and compare against baseline idle traffic from the hub. In my testing, scene executions via Matter don’t generate new outbound connections — the hub handles the physical device action locally and reports back to HA through the Matter channel.
Advanced Bridging fills a specific gap, and it fills it well. If you’ve been managing parallel workflows — Aqara app for anything involving scenes or gestures, HA for everything else — this gives you a way to consolidate trigger handling in HA while keeping Aqara’s app as the device control layer it’s actually good at.
Set up a scene, bridge it, verify the entity appears, test it in an automation. The configuration is a few taps in the Aqara Home app and a Matter refresh in HA. The ghost device issue is real but manageable if you know it’s coming.