Update: the current firmware seems to have a bridge:
Analysis of the output from my Matter Inspector (click here)
This is a Matter device descriptor dump from the SmartThings Matter Inspector for the Aqara Camera Hub G350.
1. Device Identity & Basic Info
- Vendor: Aqara (Vendor ID
0x115F) - Product: Aqara Camera Hub G350 (Product ID
0x3013) - Firmware: 4.5.20
- Hardware version: 1000
- Serial number: 85cb71c055f8e5ca
- Node label: “Aqara G350”
- Scan stage: warning (not fully “ready”)
- Generation: 1 (but implements the newer Matter 1.5 camera specification)
Important note on the scan stage: The inspector shows explicit warnings (“timed out waiting for 6 inventory responses” and “6 inventory paths marked no-response”). This is normal and expected for this device. It is one of the very first Matter 1.5 cameras with brand-new, complex video/streaming clusters that many inspection tools are still catching up to. The core device structure was still discovered correctly.
2. Topology
This is a composed device with 3 endpoints (typical for a hub + camera combo):
- Endpoint 0 → Root Node (the “brain”)
- Endpoint 1 → Aggregator (hub/bridge functionality)
- Endpoint 2 → The actual camera
3. Endpoint Breakdown
Endpoint 0 – Root Node
- Device types: Root Node (
0x0016) - Role: root/utility
- Main clusters:
- Standard root clusters (Descriptor, Access Control, Basic Information, General Commissioning, Network Commissioning, etc.)
- Wi-Fi Network Diagnostics (
0x0036) - Time Synchronization (
0x0038)
- This endpoint handles commissioning, Wi-Fi setup, security, time sync, and overall device management.
Endpoint 1 – Aggregator (Bridge/Hub)
- Device types: Aggregator (
0x000E) - Role: aggregator
- Clusters: Identify + Descriptor
- Purpose: This endpoint makes the G350 act as a Matter bridge. It can expose other devices (especially Aqara Zigbee sensors, switches, etc.) into the Matter network so they appear natively in SmartThings, Apple Home, Google Home, etc.
Endpoint 2 – Camera
- Device types: Camera (
0x0142) ← This is the official Matter camera device type - Role: generic
- Clusters:
- Identify (
0x0003) – can make the camera LED flash for identification - Descriptor (
0x001D) - 0x0551 (main camera/AV cluster) – very rich (many attributes 0x0000–0x0020 and 8 supported commands). This is the primary video streaming / camera control cluster introduced in Matter 1.5.
- 0x0553 – additional camera-related cluster (some responses timed out)
- Client cluster 0x0554 – the camera can also act as a client to other video-related services
- Identify (
- Purpose: This is where the actual 4K dual-lens PTZ camera lives. It supports live streaming, two-way talk, pan/tilt/zoom, auto-tracking, and all the new Matter 1.5 camera features (secure video streaming across ecosystems without proprietary apps).
4. Overall Capabilities (Summary)
The Aqara G350 is a multi-function device:
Matter 1.5 Camera (world’s first certified) – 4K dual-lens, PTZ, 9× hybrid zoom, live view, two-way audio- Matter Bridge / Aggregator – exposes Aqara Zigbee devices into Matter ecosystems
- Zigbee Hub (built-in)
- Thread Border Router (mentioned in product specs)
- Full Matter security, commissioning, and OTA updates
It is not a simple on/off or sensor device. It is a sophisticated hub + camera that bridges legacy Aqara Zigbee products while providing native Matter video streaming.
5. Why the dump shows warnings / no-responses
- The new camera clusters (
0x0551,0x0553,0x0554) are very recent (Matter 1.5, late 2025). - The SmartThings Matter Inspector is still partially catching up → timeouts on some deep inventory reads are common on first-generation Matter cameras.
Bottom line: This is a fully functioning, correctly structured Aqara G350 Matter Camera Hub. The inspector discovered the root, aggregator (bridge), and camera endpoints properly. The warnings are harmless and typical for this cutting-edge device. It will work in SmartThings (and other Matter 1.5-supporting platforms) for both camera streaming and as a bridge for your other Aqara devices.
I have a follow-up question for the Aqara G350. One of the advertised features is the Matter bridge: “This camera doubles as a powerful Aqara Zigbee hub and Matter Controller as well as bridge, linking your Aqara devices to major ecosystems”.
But according to the CSA Compliance Document (PICS), the device doesn’t have a Matter bridge:
<picsItem>
<itemNumber>MCORE.BRIDGE</itemNumber>
<feature>**Does the DUT implement a Bridge**</feature>
<reference>44.1. DUT server - index.html[pdf]</reference>
<status>O</status>
<support>false</support>
</picsItem>
<picsItem>
<itemNumber>MCORE.BRIDGE.BatInfo</itemNumber>
<feature>Does the DUT have information on battery level of (at least some of) of its bridged devices</feature>
<reference>44.1. DUT server - index.html[pdf]</reference>
<status cond="MCORE.BRIDGE">O</status>
<support>false</support>
</picsItem>
<picsItem>
<itemNumber>MCORE.BRIDGE.OtherControl</itemNumber>
<feature>Does the DUT have means to change the state of (at least some of) of its bridged devices, e.g. through a manufacturer-provided app</feature>
<reference>44.1. DUT server - index.html[pdf]</reference>
<status cond="MCORE.BRIDGE">O</status>
<support>false</support>
</picsItem>
<picsItem>
<itemNumber>MCORE.BRIDGE.AllowDeviceRename</itemNumber>
<feature>Does the DUT have means to change the name of (at least some of) of its bridged devices, e.g. through a manufacturer-provided app</feature>
<reference>44.1. DUT server - index.html[pdf]</reference>
<status cond="MCORE.BRIDGE">O</status>
<support>false</support>
</picsItem>
<picsItem>
<itemNumber>MCORE.BRIDGECLIENT</itemNumber>
<feature>Does the DUT support a Bridge</feature>
<reference>44.2. DUT client - index.html[pdf]</reference>
<status>O</status>
<support>false</support>
</picsItem>
Is this a planned feature?
