Update on Matter Support | X50 Ultra

We already know the story. Dreame advertised Matter support across their X50 product pages, while their support team kept insisting certification wasn’t complete.

I went straight to the source and spoke with the CSA, the body that actually certifies these devices. Turns out the entire X50 line has been certified since 10 November. Here’s the listing for anyone who wants to have a look:
https://csa-iot.org/csa_product/dreame-robot-vacuum-and-mop-102

Given that, software support should be right around the corner. And of course, under CSA rules, Dreame shouldn’t have been marketing the product as Matter-supporting before certification was finalised. Hopefully everyone involved, particularly Dreame, has taken the right lessons from this.

Hello,

Thank you for your feedback and understanding. We recognise the importance of not promoting a product's support features before its certification is complete. We are working diligently to release software support as soon as possible, ensuring compliance with all relevant regulations.

We hope to learn valuable lessons from this process and remain committed to providing you with high-quality products and services. Should you have any further questions or require additional assistance, please feel free to contact us at any time.

Hi all,

  Quick update for this thread: Matter support is now active on the X50 Ultra.
  I commissioned mine on May 8, 2026 (firmware 4.3.9_3684, hardware tag
  "VERSION_SUPPORT_MATTER", Matter spec 1.4). It paired into Home Assistant
  in the end, but only after some workarounds — details below.

  That's the broad picture. The not-so-good news is that the current firmware
  exposes a very minimal subset of what the Matter spec actually allows for
  Robotic Vacuum Cleaners, and several clusters that *are* exposed are
  returning null for their core attributes. I'd love to see a follow-up
  firmware that fixes commissioning and fills in the missing data — sharing
  the technical details below in the hope it helps Dreame's team prioritize.

  ## Commissioning is still rough

  QR-code pairing failed for me in two of the three controllers I tried:
  - **Home Assistant Companion app (iOS)** — QR scan via the native iOS Matter
    "Add device" flow failed. The device was discovered but pairing did not
    complete.
  - **Google Home** — same thing: QR scan recognized the device but
    commissioning aborted.
  - **Home Assistant directly (manual code entry)** — this is what worked.
    I had to skip the iOS-native "Add Matter Accessory" path entirely and
    paste the 11-digit setup code into Home Assistant's Matter integration
    instead. After that, commissioning completed cleanly.

  So the device is reachable and Matter-spec-compliant enough to commission,
  but something in the QR flow / iOS-native pairing path is broken. Worth a
  look on Dreame's side — most users will give up before falling back to
  manual code entry.

  ## What's working once it's paired

  Endpoint 1 (DeviceType 0x0074 = Robotic Vacuum Cleaner) currently exposes:
  - Identify (0x0003)
  - RVC Run Mode (0x0054) — Idle / Cleaning / Mapping
  - RVC Clean Mode (0x0055) — Quick / Auto / Deep Clean / + 2 more
  - HEPA Filter Monitoring (0x0061) — partial, see below
  - Service Area (0x0150) — partial, see below

  That's enough for basic start/stop/pause and clean-mode selection from any
  Matter controller. Good baseline.

  ## Issues with what's already implemented

  **HEPA Filter Monitoring (0x0061):**
  - Attribute 0 `Condition` returns null → users can't see filter % remaining
  - Attribute 1 `DegradationDirection` returns null
  - ChangeIndication (attr 3) and InPlaceIndicator (attr 4) ARE populated,
    so the cluster is half-wired

  **Service Area (0x0150):**
  - `SupportedAreas` (attr 0) is correctly populated with rooms (kitchen,
    bedroom, etc.) and `SupportedMaps` (attr 1) lists "Main floor" /
    "Upper floor" — great, this is the right structure
  - BUT `CurrentArea` (attr 3) returns null → controllers can't display
    which room the robot is currently in
  - And `SelectedAreas` (attr 2) is always [] → room-targeted cleaning
    commands don't reflect

  ## Clusters the Matter 1.4 spec defines for RVCs but the X50 doesn't expose

  These would be huge wins if added in a future firmware:

  1. **Power Source (0x002F)** — battery percentage, charge state, time
     remaining, low-battery alerts. Currently there is no way at all to see
     battery level over Matter. This is probably the #1 missing feature.

  2. **Operational State (0x005E)** — proper running/paused/stopped/error/
     docked/seekingCharger plus CountdownTime and OperationalError events.
     Today, Home Assistant has to derive a degraded operational state from
     RunMode alone.

  3. **Activated Carbon Filter Monitoring (0x0062)** — same shape as the
     HEPA cluster but for the side brush / secondary filter consumables.

  4. **Boolean State (0x0045)** — for things like "dustbin full", "mop
     installed", "water tank empty" — all of which already exist in the
     cloud integration and would map cleanly here.

  ## What this means for HA / Apple Home / Google Home users

  Today, anyone using the X50 Ultra purely over Matter sees roughly 4
  entities (vacuum, run mode, clean mode, operational state). The same
  device through the Dreame cloud integration in Home Assistant exposes
  ~200 entities. The gap isn't all on Matter — Service Area covers rooms
  nicely if `CurrentArea` were populated, and PowerSource covers battery —
  so a chunk of that gap is closable on the device side.

  ## Summary for the Dreame team, if you're reading

  Two distinct issues worth investigating:
  1. QR-code commissioning broken via iOS-native Matter pairing
     (Home Assistant Companion + Google Home both fail). Manual 11-digit
     code entry into Home Assistant directly works as a workaround.
  2. The exposed cluster set is minimal, and within it `Condition`
     (HEPA filter) and `CurrentArea` (Service Area) are returning null even
     though their parent clusters are otherwise wired up.

I've attached a sanitized Matter diagnostics dump below (identifiers,
  network info and fabric credentials redacted; cluster structure and
  attribute values preserved). The link will remain available until
  June 10, 2026, after which I'll take it down. Happy to share the full
  unredacted version with Dreame's engineering team via DM or email if
  it helps  Home assistant diagnostic raw dump

  Thanks for getting Matter shipped on this device — the foundation is
  there, it just needs the commissioning path fixed and the consumable /
  state data plumbed through.

Was support for matter brought in?