From 1fa1f29faa7a9e214c91167291c1320be579f705 Mon Sep 17 00:00:00 2001 From: frazierjason Date: Fri, 11 Sep 2026 08:37:03 -0700 Subject: [PATCH] Clarify SSL.com entry for QRevo Master vacuum Updated SSL.com column to specify Sectigo issuance for clarity. Added compatibility for Qrevo Master, this tested successfully on firmware 02.28.26. I am using a SSL.com issued Sectigo Public Server Authentication CA DV R36, via a *.domain wildcard). Onboarding process worked, TLS accepted, /region completed. Uses the v1 /region flow; no version header sent, unsupported: false The robot onboarded successfully behind Traefik (HTTPS) + ServiceLB (MQTT) on k3s, with a workarounded issue that MQTT first-connect adoption fails when HTTP and MQTT arrive via different proxies, but this is unrelated to certificate trust. --- docs/tested_vacuums.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tested_vacuums.md b/docs/tested_vacuums.md index 94a1798..424b985 100644 --- a/docs/tested_vacuums.md +++ b/docs/tested_vacuums.md @@ -42,7 +42,7 @@ Legend: - Cross: reported not working - Question mark: not reported yet -| Vacuum | Firmware | ZeroSSL / Cloudflare | Actalis | Let's Encrypt | SSL.com | +| Vacuum | Firmware | ZeroSSL / Cloudflare | Actalis | Let's Encrypt | SSL.com (Sectigo) | |---|---:|---:|---:|---:|---:| | Roborock S5 Max | Not reported | ❌ | ✅ | ❌ | ❓ | | Roborock S7 | Not reported | ❓ | ✅ | ❌ | ✅ | @@ -54,7 +54,7 @@ Legend: | Roborock G30U | `02.52.32` | ✅ | ❓ | ❓ | ❓ | | Roborock Qrevo S5V | Not reported | ❓ | ❓ | ❓ | ❓ | | QRevo MaxV | Not reported | ✅ | ❓ | ✅ | ❓ | -| QRevo Master | `02.28.26` | ❓ | ❓ | ✅ | ❓ | +| QRevo Master | `02.28.26` | ❓ | ❓ | ✅ | ✅ | | QRevo Plus | Not reported | ✅ | ❓ | ❓ | ❓ | ## Unlisted Vacuums