Problems with Matter and Roborock Robotic Vacuum Cleaner (S8 MaxV Ultra)

Matze89x · May 15, 2025, 7:09am

Hello to you,

I have finally received the update for Matter for the Roborock S8 MaxV Ultra a few weeks ago. I integrated it directly into Home Assistant, but it is not working correctly.

Status is wrong. - When cleaning, ‘Fehler’ appears in German as an error as a status message
I can’t operate it, no function
Error in the Matter protocol (Node)

2025-05-15 08:59:06.357 WARNING (MainThread) [matter_server.client] Could not determine network_interface info for Node 22, is it missing the GeneralDiagnostics/NetworkInterfaces Attribute?

2025-05-15 09:02:34.417 WARNING (MainThread) [matter_server.client] Could not determine network_interface info for Node 22, is it missing the GeneralDiagnostics/NetworkInterfaces Attribute?

2025-05-15 09:02:34.424 WARNING (MainThread) [matter_server.client] Could not determine network_interface info for Node 22, is it missing the GeneralDiagnostics/NetworkInterfaces Attribute?

2025-05-15 09:08:09.134 WARNING (MainThread) [matter_server.client] Could not determine network_interface info for Node 22, is it missing the GeneralDiagnostics/NetworkInterfaces Attribute?

2025-05-15 09:08:09.137 WARNING (MainThread) [matter_server.client] Could not determine network_interface info for Node 22, is it missing the GeneralDiagnostics/NetworkInterfaces Attribute?

It works perfectly in Apple Home.

Does anyone have the same problems or a solution for me?

here my old posting:

lencyforce · May 17, 2025, 6:14am

I got exactly the same problem on another model (G30) of the Roborock cleaner, which also got the firmware upgrade to support matter protocol recently. The status display is incorrect (cleaning is showing as error). “Change cleaning mode” works, “identify” works (which makes the robot make a sound about where it is), but “start” and “return to dock” do not work.

I added the cleaner to Apple Home first, and then shared it to Home Assistant. It works fine in Apple Home.

RRR · May 23, 2025, 3:16pm

I got the Matter code in the Roborock app for my QRevo Edge, but it fails in the add Matter device, not sure if you need to put it in a setup mode somehow?

lencyforce · May 26, 2025, 12:14pm

I tried a lot of things before it finally succeed. Such as enabled IPV6 on my router, connected my phone to the same 2.4G WIFI as the robot and restarted the robot before trying to add the device to Apple Home…don’t know which one worked…

Matze89x · May 30, 2025, 8:34am

Hello to you, nice to hear that you are also haunted by the bug. It drives off as an error… well…

I was able to integrate it without any problems.
However, the error is still there now that a lot of updates have been released. Where else can you report the problem?

/edit: Matter - Roborock Robotic Vacuum Cleaner - State - (S8 MaxV Ultra) · Issue #145884 · home-assistant/core · GitHub

lboue · August 26, 2025, 9:49am

It should be fixed now, right?

github.com/home-assistant/core

Matter - Roborock Robotic Vacuum Cleaner - State - (S8 MaxV Ultra)

opened 08:42AM - 30 May 25 UTC

closed 01:23PM - 25 Jun 25 UTC

Matze89x

integration: matter

### The problem From here: https://community.home-assistant.io/t/problems-with-…matter-and-roborock-robotic-vacuum-cleaner-s8-maxv-ultra/889524 Hello to you, I have finally received the update for Matter for the Roborock S8 MaxV Ultra a few weeks ago. I integrated it directly into Home Assistant, but it is not working correctly. Status is wrong. - When cleaning, ‘Fehler’ appears in German as an error as a status message I can’t operate it, no function Error in the Matter protocol (Node) ``` 2025-05-15 08:59:06.357 WARNING (MainThread) [matter_server.client] Could not determine network_interface info for Node 22, is it missing the GeneralDiagnostics/NetworkInterfaces Attribute? 2025-05-15 09:02:34.417 WARNING (MainThread) [matter_server.client] Could not determine network_interface info for Node 22, is it missing the GeneralDiagnostics/NetworkInterfaces Attribute? 2025-05-15 09:02:34.424 WARNING (MainThread) [matter_server.client] Could not determine network_interface info for Node 22, is it missing the GeneralDiagnostics/NetworkInterfaces Attribute? 2025-05-15 09:08:09.134 WARNING (MainThread) [matter_server.client] Could not determine network_interface info for Node 22, is it missing the GeneralDiagnostics/NetworkInterfaces Attribute? 2025-05-15 09:08:09.137 WARNING (MainThread) [matter_server.client] Could not determine network_interface info for Node 22, is it missing the GeneralDiagnostics/NetworkInterfaces Attribute? ``` ![Image](https://github.com/user-attachments/assets/7b13a8e6-9ae4-44bd-a3e3-fd6d27ae2f55) It works perfectly in Apple Home. Does anyone have the same problems or a solution for me? here my old posting: https://community.home-assistant.io/t/homekit-vacuum-entity-support/771548/31 ### What version of Home Assistant Core has the issue? core-2025.5.3 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Matter ### Link to integration documentation on our website https://www.home-assistant.io/integrations/matter ### Diagnostics information [matter-548bbe1ba33190a5ff84c764e8d997ea-Robotic Vacuum Cleaner-1ae902334643cc32ee3045ba07b3a2a6.json](https://github.com/user-attachments/files/20517628/matter-548bbe1ba33190a5ff84c764e8d997ea-Robotic.Vacuum.Cleaner-1ae902334643cc32ee3045ba07b3a2a6.json) ### Example YAML snippet ```yaml ``` ### Anything in the logs that might be useful for us? ```txt ``` ### Additional information _No response_

AndrewF6 · December 18, 2025, 9:03am

Did you ever get this to work, I just blindly bought the Qrevo Edge without realising it wasn’t natively support by HA. And matter doesn’t want to connect, logs point to failing the attestation

orange-assistant · December 18, 2025, 9:14am

Other people computers (cloud) says no

308CISOdude · July 4, 2026, 10:37am

I also bought the Qrevo Edge (after ensuring there is a Roborock integration in HA). The cloud integration works as desired and the hardware is solid quality.
As HA users, we naturally prefer local integrations over "other people computers" (AKA cloud - thanks orange-assistant ) integrations. I hit the same error over and over again when trying to connect the vacuum via Matter.
After analysing the HA logs with Claude, Claude pointed out the exact spot in the Roborock firmware where the bug is:

Excellent — this is now crystal clear. Confidence: very high.

The exact failure, every single time:

Attestation finding (error): ValidationError Offset is outside the bounds of the DataView
Attestation rejected

The commissioning itself goes well — PASE pairing succeeds, the vacuum is found and reachable at 192.168.107.9. It fails at step 10.1: Device Attestation, specifically when parsing the PAI certificate (Product Attestation Intermediate) returned by the vacuum.

The PAI cert (type 2) the vacuum returns is suspiciously short: 4686e8ae8724 — that's only 6 bytes. A valid X.509 PAI cert should be hundreds of bytes. The @matter/general DER codec then tries to parse this truncated blob and crashes with a buffer overread. This is identical across all four of your attempts — same broken cert every time.

Root cause: Bug in Roborock's firmware PAI certificate implementation. The vacuum is returning a malformed/truncated PAI cert. This is not a Home Assistant config problem, not a network problem, not anything you can fix on your end.

I sent this to the Roborock support, along with all needed information to address this issue (exact model, serial number, most current firmware version 02.29.22 - and this is where the real fail begun.

During the upcoming back and forth conversation via mail, I kindly asked the Roborock support 3 times to please send my message to the firmware development, they should know how to handle it.

First, Roborock support replied something about vacuum spare parts.
The second answer requested the invoice number.
The third answer says:
"Dear Customer,
We apologize, but our official product does not promote or support Home Assistant. Therefore, we are unfortunately unable to provide you with any helpful information regarding your inquiry.
We recommend that you use officially supported voice control platforms such as Google Home, Alexa, or Apple Home."

While I ultimately give up on this ticket, I genuinely feel sorry for the poor dudes at Roborock support. Even with crystal clear language pointing out the exact error and the department to forward it to, they completely failed to even understand the issue. Since even with the free plan, ChatGPT or Claude immediately understand the error and provide the solution, these guy's jobs will be the first to be completely replaced by AI in the near future. There's no way around that. So sad...