Check this page alongside Installation and Onboarding if you are trying to confirm whether your model is expected to work.
For most users, start with ZeroSSL. Actalis is mainly recommended for older vacuums or for models that already have reports showing better compatibility with the Actalis chain. Results below apply to the reported firmware and certificate chain; other versions or chains may behave differently.
If you're looking to buy a Roborock, consider using one of my affiliate links on the Support This Project page. It doesn't cost you anything extra and helps keep this project going!
The following vacuums are not supported and may never be supported.
- Roborock Q10 X5 / X5+
- Roborock Q7 M5 / M5+
- Roborock Q7 L5
- Roborock Q10 s5/ s5+
These models have not yet been confirmed working. Version 1.1.0 adds V2
onboarding support; please report your model, firmware, and certificate chain
if you try one.
- Roborock Qrevo Curv 2 Pro
- Roborock Qrevo S Pro
- Qrevo Curv 2 Flow
- Saros Z70
Failing reports made before 1.1.0 need retesting on those devices and firmware versions.
These reports remain unresolved:
| Vacuum | Firmware | Result | Report |
|---|---|---|---|
| Roborock Q7 TF+ | Not reported | Onboarding fails; uses a different protocol from the V2 models supported in 1.1.0. |
#48 |
The following vacuums are confirmed working:
Legend:
- Check mark: reported working
- Cross: reported not working with that certificate setup
- Question mark: certificate result not reported
Cloudflare can provide DNS validation for several certificate issuers. Its use alone does not establish which issuer was tested. Working reports without a named issuer retain question marks in the certificate columns.
| Vacuum | Firmware | ZeroSSL | Actalis | Let's Encrypt | SSL.com | Reports |
|---|---|---|---|---|---|---|
| Roborock S5 Max | Not reported | ❌ | ❓ | ❌ | ❓ | #3 |
| Roborock S5 Max | 02.16.62 |
❓ | ✅ | ❓ | ❓ | #3 |
| Roborock S7 | Not reported | ❓ | ✅ | ❌ | ✅ | #3 |
| Roborock S7 MaxV | Not reported | ❓ | ❓ | ✅ | ❓ | — |
| Roborock S7 MaxV | 2.59.36 |
✅ | ❓ | ❓ | ❓ | #49 |
| Roborock S7 Max Ultra | 02.26.80 |
❓ | ❓ | ✅ | ❓ | #79 |
| Roborock S7 Pro Ultra (a62) | Not reported | ❓ | ✅ | ❌ | ❓ | #65 |
| Roborock S8 (a51) | 02.14.48 |
❌ | ❓ | ✅ | ❌ | #46 |
| Roborock S8 (a51) | 02.17.42 |
✅ | ❓ | ✅ | ❓ | #46 |
| Roborock S8+ (a51) | 02.17.42 |
❓ | ❓ | ✅ | ❓ | #66 |
| Roborock S8 MaxV Ultra | 02.37.38 |
✅ | ❓ | ❓ | ❓ | #49 |
| Roborock S8 Pro Ultra (a70) | Not reported | ❓ | ❓ | ❓ | ❓ | — |
| Roborock Saros 10R | 02.50.56 |
❓ | ❓ | ❓ | ❓ | #78 |
| Roborock Saros 10R | 02.52.32 |
✅ | ❓ | ✅ | ❓ | — |
| Roborock Saros 10R (a144) | 02.52.86 |
❓ | ❓ | ✅ | ❓ | #57, #61 |
| Roborock Saros 20 Complete (a288) | 02.55.44 |
✅ | ❓ | ❓ | ❓ | #98 |
| Roborock Saros 20 Sonic (a279) | 02.42.52 |
✅ | ❓ | ❓ | ❓ | #84 |
| Roborock Saros 20X (a288) | 02.55.44 |
✅ | ❓ | ✅ | ❓ | #114 |
| Roborock G30U | 02.52.32 |
✅ | ❓ | ❓ | ❓ | — |
| Roborock Q5 Pro | 02.04.66 |
❌ | ❓ | ✅ | ❓ | #56, #97 |
| Roborock Q8 Max | 02.06.86 |
❓ | ❓ | ✅ | ❓ | #70 |
| Roborock Qrevo C (a170) | 02.16.64 |
❓ | ❓ | ❓ | ❓ | #95 |
| QRevo | 02.20.60 |
✅ | ❓ | ✅ | ❓ | #75, #94 |
| QRevo Curv | 02.28.60 |
❓ | ❓ | ✅ | ❓ | #60 |
| QRevo Curv (a135) | 02.28.92 |
❓ | ❓ | ✅ | ❓ | #110 |
| QRevo CurvX | 02.35.88 |
✅ | ❓ | ❓ | ❓ | #64 |
| QRevo Edge | 02.22.52 |
❓ | ❓ | ✅ | ❓ | #90 |
| QRevo Edge 2 Set (a298) | 02.15.44 |
❓ | ❓ | ✅ | ❓ | #84, #59 |
| QRevo MaxV | Not reported | ✅ | ❓ | ✅ | ❓ | — |
| QRevo Master (a117) | 02.28.26 |
❓ | ❓ | ✅ | ✅ | #57, #82 |
| QRevo Plus (a123) | 02.03.28 |
✅ | ❓ | ❓ | ❓ | #112 |
| QRevo S5V (a170) | 02.09.70 |
❓ | ❓ | ❓ | ❓ | #52 |
| QRevo S5V (a170) | 02.16.64 |
❓ | ❓ | ✅ | ❓ | #52 |
| QX Revo Plus (Costco version) | Not reported | ❓ | ❓ | ✅ | ❓ | #89 |
Setup notes:
- S7 Pro Ultra: the Actalis success used an RSA-2048 certificate. The Let's Encrypt failure was reported with an R3/E1 chain.
- Saros 10R
02.50.56: the reported pfSense/HAProxy setup used provided certificates and the MITM redirect fix in PR #77. - Saros 20X: confirmed working with both ZeroSSL and Let's Encrypt on server v1.2.0. The reporter noted the vacuum attempts direct DNS queries to 8.8.8.8 until WAN access is blocked at the router, after which it correctly uses local DHCP DNS.
- Q5 Pro: ZeroSSL was attempted and failed (MQTT broken pipe), while Let's Encrypt succeeded.
- Qrevo C: confirmed working with a GoDaddy-issued certificate and tested with the LocalRock Android app.
- QRevo Curv: the reporter worked around an app redirect port issue, also tracked by PR #77.
- QRevo Master: the SSL.com result used a Sectigo Public Server Authentication CA DV R36 chain and a workaround for the proxy MQTT onboarding issue in #83.
If your model is not listed, start with ZeroSSL unless it is an older model that is likely to need a different trusted chain. If onboarding fails after the DNS and server checks pass, try Actalis or a provided certificate and report the result.
Use the compatibility report form to share your exact model, firmware, server version, certificate issuer, and what worked or failed. Include any workarounds. You can also open a pull request updating this page with a link to your report.