From e9100401b918246ecd3542064ad1ef40574cd769 Mon Sep 17 00:00:00 2001 From: Luke Date: Sun, 15 Nov 2026 15:20:43 -0500 Subject: [PATCH 1/2] docs: reconcile compatibility reports and camera validation --- docs/camera.md | 56 ++++++ docs/compatibility_reports.md | 319 ++++++++++++++++++++++++++++++++++ docs/home_assistant.md | 8 + docs/known_limitations.md | 6 +- docs/onboarding.md | 34 ++++ docs/tested_vacuums.md | 53 +++++- mkdocs.yml | 1 + 7 files changed, 465 insertions(+), 12 deletions(-) create mode 100644 docs/compatibility_reports.md diff --git a/docs/camera.md b/docs/camera.md index 737ff75..fb70864 100644 --- a/docs/camera.md +++ b/docs/camera.md @@ -4,6 +4,12 @@ Camera-capable robots can stream to a local WebRTC consumer such as [go2rtc](https://github.com/AlexxIT/go2rtc) with a `roborock://` source. Camera bootstrap, authentication and TURN all need to work. +The camera bootstrap/TURN implementation was merged in +[PR #144](https://github.com/Python-roborock/local_roborock_server/pull/144) and +[PR #155](https://github.com/Python-roborock/local_roborock_server/pull/155), after +the `v1.2.1` tag. Results below identify development/custom builds where reported; +repulling the `v1.2.1` image does not add this implementation. + ## Bootstrap DNS, ports and certificates Bootstrap depends on firmware. The tested Saros 10R (`roborock.vacuum.a144`, @@ -21,6 +27,12 @@ For example, onboarding server `api-vac.cc:555` produces `token.r = vac.cc:555/` Camera domain `api-vac.cc` produces `country_domain = api-vac.cc/`. Qrevo requires DNS, trusted TLS and routing for `vac.cc:555`; Saros requires `api-vac.cc:443`. Explicit ports are retained; inputs without a port use 443. + +Do not infer the bootstrap source from the product family alone. The tested +Saros 20X uses `token.r`, unlike the Saros 10R above. A Qrevo Master report says +that putting a hostname in `country_domain` prevented onboarding; that setup used +a short `token.r` and a normal region instead. + After device selection, onboarding checks the observed input for a87 and a144. For an unknown model or a new vacuum whose model is not known yet, it checks both inputs conservatively; configure both endpoints or first identify the model. @@ -124,6 +136,42 @@ The tested Saros 10R required two-key activation: set the remote-view PIN the two-key request bits set and monitor bit off, then press Power on the robot within about 60 seconds. Activation varies by model. +A Qrevo Master report observed `set_camera_status` values `[417]` then `[4513]` +from an initial status of `385`, followed by a robot-reported status of `8613`, +without the Saros-style physical activation. An a226 report started at `257` and +observed `[385]`, `[417]`, then `[4513]`; setting the PIN alone had not enabled +remote viewing. These are captured sequences for those devices, not universal +values to copy onto another model. First-time cloud-free PIN setup remains +unverified for the Edge 2 Flow in +[#256](https://github.com/Python-roborock/local_roborock_server/issues/256). + +## Reported camera results + +The table records what each source tested. **TURN enabled** does not by itself +prove that media used the relay. A direct LAN stream, a packet-captured relay +stream, and a forced-relay test are different observations. Current onboarding +preflight does not automatically recognize every model in this table. + +| Model / firmware | Bootstrap and setup | Confirmed scope and limits | Source | +|---|---|---|---| +| Saros 10R (a144), `02.33.88` US | `country_domain`; coturn and activated remote view | go2rtc received frames after activation; physical activation is model-specific. | [#18](https://github.com/Python-roborock/local_roborock_server/issues/18#issuecomment-6082544593) | +| Qrevo MaxV (a87), firmware not stated here | `token.r`, including explicit port | Existing validation recorded frames in a forced-relay preview. | [#155](https://github.com/Python-roborock/local_roborock_server/pull/155) | +| Saros 20X (a288), `02.55.44` EU | `token.r`; server `c3b3284`, provided TURN, patched Android 4.74.04 | Official-app video after shortening the name; reporter also applied HEAD/product-ID fixes. Existing pattern accepted without additional robot activation. | [#18 follow-up](https://github.com/Python-roborock/local_roborock_server/issues/18#issuecomment-6153351361) | +| Qrevo Master (a117), `02.28.26` | Short `token.r`, normal country region | Official-app video and activation sequence reported; a hostname in `country_domain` broke onboarding. | [#173](https://github.com/Python-roborock/local_roborock_server/pull/173) | +| Qrevo Curv 2 Flow, firmware not reported in comment | Short `token.r`, existing wildcard, TURN | Official app and LocalRock video; activation already enabled. Tested third-party client needed a modified SDP offer. | [#173 follow-up](https://github.com/Python-roborock/local_roborock_server/pull/173#issuecomment-6329081772) | +| S7 MaxV (a27), `02.59.36` | `token.r`, normal `eu` region, server base `c3b3284`, provided Let's Encrypt RSA-2048 and coturn | 640×480 H.264; 240 frames over 20 seconds with a test-only forced-relay go2rtc build. Audio/driving untested here. Proposed `--camera` preflight flag belongs to the open PR. | [#185](https://github.com/Python-roborock/local_roborock_server/pull/185) | +| S7 MaxV (a27), `02.59.36` | Short bootstrap name; Actalis RSA-2048, Nginx, custom scheduling build, provided TURN | Official iOS video, Call and remote driving; bulk media observed directly across LAN/VLANs, not forced relay. | [#215](https://github.com/Python-roborock/local_roborock_server/issues/215#issuecomment-6508919416) | +| S7 MaxV (a27), `02.59.36` | ZeroSSL automatic base/wildcard, HA add-on/HAProxy; both onboarding fields use the short name | SD preview with WAN blocked and packet-captured relayed media. Server version unspecified in follow-up. | [#215 follow-up](https://github.com/Python-roborock/local_roborock_server/issues/215#issuecomment-6836429054) | +| S8 MaxV Ultra (a97), `02.39.60` US | Short `token.r` including port 555, normal `us` region, provided ZeroSSL SAN and TURN | Official iOS video on LAN with existing PIN; HA, maps and rooms continued to work. | [#185 follow-up](https://github.com/Python-roborock/local_roborock_server/pull/185#issuecomment-6358124198) | +| Qrevo Edge 2 Pro / cloud alias Curv 2 Pro (a226), `02.43.62` | Short `token.r`, Let's Encrypt, custom product/plugin fixes | Official iOS and go2rtc video; two-way audio when microphone stream starts the producer. Cloud-app activation; relay versus direct media untested. | [#223](https://github.com/Python-roborock/local_roborock_server/issues/223) | +| Qrevo Edge 2 Pro (a226), `02.43.62` | Custom apex-host/bootstrap server, Let's Encrypt, custom L01 bridge and modified go2rtc | Fresh video/two-way audio with WAN blocked, recovery after host reboot. Controls/maps and first-time cloud-free activation untested. | [#239](https://github.com/Python-roborock/local_roborock_server/issues/239) | +| China P20 (a184), factory `02.22.56` | Custom certificate/interception setup; see [partial results](tested_vacuums.md#partial-compatibility-and-custom-setups) | Local camera reported; the mangled-hostname/SAN result does not establish a normal owned-domain certificate path. | [#229](https://github.com/Python-roborock/local_roborock_server/issues/229), [#230](https://github.com/Python-roborock/local_roborock_server/issues/230) | + +The ordinary short-hostname setup above remains the documented path for publicly +issued certificates on domains you control. The a184 report reached a longer, +mangled hostname using a compromised-intermediate certificate; it does not mean +that a normal certificate for the API hostname covers that destination. + ## Troubleshooting and tested behavior - Bootstrap falls back: inspect the actual hostname, port and path in server logs. @@ -132,6 +180,14 @@ within about 60 seconds. Activation varies by model. - Preview rejected: check the existing PIN and the model's activation flow. - Bootstrap succeeds without frames: check authenticated TURN allocation, UDP mappings, firewall rules and the advertised address. +- Repeated `get_device_sdp` replies of `retry`: the Curv 2 Flow report succeeded + with audio first (`sendrecv`, Opus/telephone-event), H.264 receive-only video + with its associated RTX/RED/ULPFEC, no `extmap-allow-mixed`, and an offer sent + before ICE candidates. Several properties changed together, so the reporter + did not isolate one as the cause; this is not a universal SDP requirement. +- Video works but microphone does not: in #223, starting the go2rtc producer with + `media: video,audio,microphone` worked, while switching an existing listen-only + producer to that stream did not send microphone audio. Saros 10R completed a WebRTC handshake with coturn and go2rtc received frames. Qrevo MaxV completed a forced-relay preview with frames after configuring the diff --git a/docs/compatibility_reports.md b/docs/compatibility_reports.md new file mode 100644 index 0000000..5fbcac2 --- /dev/null +++ b/docs/compatibility_reports.md @@ -0,0 +1,319 @@ +# Compatibility report details + +These notes reconcile the open compatibility reports and their follow-up comments +as of 15 November 2026. They supplement the [tested-vacuums table](tested_vacuums.md), +which retains earlier results. Observations are attributed to their reports; +they are not independent hardware tests by the documentation author. + +Keep firmware, certificate chain, client, and server build together when comparing +results. A successful MQTT connection does not establish working controls, maps, +camera, or every Home Assistant entity. A later success with another chain or +firmware does not invalidate an earlier failure. An open PR's hardware report +does not mean its proposed implementation is in a release. + +## Older S-series models + +### S6 Pure (a08), firmware 02.13.68 + +On server **v1.2.1**, Docker Compose with the embedded broker and no reverse proxy, +Actalis RSA-2048 worked using TLS 1.0. The reported chain was Actalis Domain +Validated TLS Server RSA CA 2025 → Actalis TLS Server RSA Root CA 2025 → Actalis +Authentication Root CA. Four GUI pairing cycles recovered the key and connected. +HA status, controls, both floor maps and room targeting worked. Water-box-attached +and mop-mode entities available through the cloud were absent locally; mop intensity +remained available. The official app was not tested after onboarding. +[#191](https://github.com/Python-roborock/local_roborock_server/issues/191) + +A second unit on the same firmware rejected a Let's Encrypt ECDSA chain +YE1 → Root YE → ISRG Root X2 → ISRG Root X1, but accepted a provided Actalis +RSA-2048 certificate issued through Certbot. Both reporters found that their +Actalis 90-day EAB credentials had issuance quota while their 1-year credentials +did not. One reporter changed a manually entered Bucharest POSIX timezone to +auto-filled Berlin settings before traffic started; the report does **not** isolate +the timezone from a malformed CST string as the cause. +[Follow-up](https://github.com/Python-roborock/local_roborock_server/issues/191#issuecomment-6431411331) + +### S6 MaxV (a10), firmware 02.33.88 and 02.62.46 + +On **v1.2.1**, `02.33.88` worked with Actalis after Let's Encrypt and ZeroSSL +attempts failed. Docker ran in a Proxmox LXC with Caddy managing certificates. +HA and LocalRock controls/maps worked after three or four pairing cycles. Camera +setup remained unresolved and an authenticated external Mosquitto broker could +not be used; the reporter used the embedded broker instead. +[#231](https://github.com/Python-roborock/local_roborock_server/issues/231) + +The newer `02.62.46` accepted **ZeroSSL** through the v1.2.1 HA add-on's ACME +flow. LocalRock onboarding and HA/LocalRock controls worked with Pi-hole DNS. +The official app did not work in that setup. This is firmware-specific evidence, +not a reason to overwrite the older certificate failures. +[#236](https://github.com/Python-roborock/local_roborock_server/issues/236) + +### S7 MaxV (a27), firmware 02.59.36 + +Actalis RSA-2048, issued by Actalis Domain Validated TLS Server RSA CA 2025, +worked on a **custom scheduling build** in Docker on Linux Mint. Nginx terminated +HTTPS on 443 and MQTT TLS on 8881, forwarding to `external_tls` listeners. After +a firewall correction, three LocalRock pairing attempts completed onboarding. +Later tests confirmed official-iOS-app video, Call and remote driving with an +existing remote-view PIN. TURN had to be enabled, but the observed bulk media +was direct across the LAN/VLANs; that test did not prove forced-relay operation. +[#215](https://github.com/Python-roborock/local_roborock_server/issues/215#issuecomment-6508919416) + +A separate HA add-on/HAProxy setup on the same firmware used automatically +provisioned **ZeroSSL** base-domain/wildcard certificates. With WAN blocked, +the reporter observed camera bootstrap, TURN allocation and relayed SD video +using published UDP 3478 and 49160–49179. The precise server version was not given +in that follow-up. See the [camera results](camera.md#reported-camera-results) for +the separate Let's Encrypt and forced-relay test from PR #185. +[ZeroSSL follow-up](https://github.com/Python-roborock/local_roborock_server/issues/215#issuecomment-6836429054) + +### S7 Pro Ultra and QX Revo Ultra 2 + +The S7 Pro Ultra (a62) Actalis RSA-2048 result and Let's Encrypt R3/E1 rejection +are already in the table. Its firmware was not reported. The reporter observed +the connection closing after the TLS handshake but before HTTP/MQTT application +traffic with the rejected certificate. That symptom warrants checking the exact +chain **and hostname**; it does not prove a universally incompatible CA. +[PR #65](https://github.com/Python-roborock/local_roborock_server/pull/65) + +QX Revo Ultra 2 (a298), `02.15.44`, was reported on **v1.2.1**, unmodified Docker +Compose, with Actalis: maps and cleaning/docking acknowledgements worked, and +the reporter observed five days of local operation. Recovery used header samples +while query samples stayed at zero. Idle reconnects were reported on this setup; +do not use that observation to dismiss command failures or stalled TLS listeners +on other models. The table keeps Actalis as the only established issuer for this +report. Proposed camera tooling in the PR is separate from that compatibility result. +[PR #194](https://github.com/Python-roborock/local_roborock_server/pull/194) + +## Saros models + +### Saros 20X (a288), firmware 02.55.44 + +The reported working setup used **v1.2.0**, Podman, LocalRock cloud-import +onboarding and HA controls, with both Let's Encrypt and ZeroSSL. Caddy supplied +certificate files but did not proxy the server. Earlier v1.1.0 attempts failed. +Increasing the container's constrained CPU/memory allocation helped; public-key +recovery can be expensive. The robot attempted DNS directly to `8.8.8.8` until +WAN access was blocked, then used DHCP-provided local DNS. See +[network troubleshooting](onboarding.md#network-and-resource-checks). +[#114](https://github.com/Python-roborock/local_roborock_server/issues/114) + +### Saros 20 Neo (a296), firmware 02.27.04 and 02.29.56 + +`02.27.04` worked on **main at `94bffa7`**, Docker/Proxmox behind Traefik with +Let's Encrypt YR2 → Root YR → ISRG Root X1. The `02.29.56` follow-ups used +**v1.2.1**, both direct TLS with an ECDSA P-384 chain +YE1 → Root YE → ISRG Root X2 → ISRG Root X1 and Traefik with a YR2 chain. +HA maps, status and controls worked. One follow-up recovered the key from header +samples in about two minutes; WAN blocking before onboarding was needed in those +follow-ups. EU cloud import incorrectly selected the US region for one reporter; +explicit `base_url = https://euiot.roborock.com` returned the inventory. +[#139 and follow-ups](https://github.com/Python-roborock/local_roborock_server/issues/139) + +Remaining model/client limitations: HA displays Vacuum then Mop as unknown; +`set_wash_towel_mode` was rejected in one setup. Another reporter found +`set_custom_mode` accepted only 101, while combined `set_clean_motor_mode` +accepted 102/103/104/105/106/110; mop-only used fan power 105. Mop modes 300 and +303 worked, 301 did not. `get_recover_maps` returned `unknown_method`. HA map +editing worked inside `start_edit_map` / `end_edit_map`. These are observations +on `02.29.56`, not universal command recipes for other firmware. +[Command details](https://github.com/Python-roborock/local_roborock_server/issues/139#issuecomment-6247548897) + +### Saros 20 Sonic (a279), firmware 02.58.82 + +On the **v1.2.1 HA add-on with ZeroSSL**, the initial report had successful +onboarding and telemetry but no replies to commands. The reporter later confirmed +working operation after deleting/recreating server state and performing three +fresh pairing cycles. The suspected link to an intervening firmware update was +not established. Record this as a resolved setup report, not proof of a general +firmware-update fix or a recommendation to delete server data as a first step. +[#217 resolution](https://github.com/Python-roborock/local_roborock_server/issues/217#issuecomment-6504895070) + +## Qrevo models + +### Qrevo Curv (a135), firmware 02.28.92 + +On **v1.2.0**, Docker behind Nginx/SWAG with Let's Encrypt, HA worked. The +reporter manually backed up maps to the robot before migration; LocalRock did +not display carpet surfaces or custom room names. An admin-password UI change +was also requested. Recording the compatibility result does not implement those +UI improvements. +[#110](https://github.com/Python-roborock/local_roborock_server/issues/110) + +### QV 35A (a168) and QX Revo Plus (reported a168) + +QV 35A `02.49.24` worked on the **v1.2.0 HA add-on**, using ZeroSSL via Cloudflare +DNS-01, local dnsmasq DNS, and three script pairing cycles. HA and LocalRock +commands were confirmed. The requested `external_tls` option remains unavailable +in the HA add-on; that mode is for standalone/Docker deployments. +[#119](https://github.com/Python-roborock/local_roborock_server/issues/119) + +QX Revo Plus `02.27.40`, reported model identifier a168, worked on **v1.2.1 +Docker** with a ZeroSSL/Sectigo/USERTrust chain. HA connected and a cleaning +routine ran; ACME timeouts were reported during setup. Keep this retail name and +firmware distinct from other QX Revo Plus entries. +[#248](https://github.com/Python-roborock/local_roborock_server/issues/248) + +### Qrevo S5V (a170) and QRevo 5AE + +S5V `02.33.88` onboarded after four to six cycles on **v1.2.0 Docker with +Let's Encrypt**, but map saving was disabled. A follow-up enabled `lab_status` +through HA's `vacuum.send_command` with `set_lab_status` and +`[{"lab_status": 1}]`. A later LocalRock zone-cleaning coordinate problem remains +unresolved; the workaround does not establish that zone cleaning is fixed. +[#148](https://github.com/Python-roborock/local_roborock_server/issues/148) + +QRevo 5AE `02.33.88` was reported working through HA and the Roborock app using +**ZeroSSL**, with the same map-saving workaround. The server version was entered +as `v1.1.2` in the report and has not been verified; the model identifier was not +given. Do not infer an a170 identifier from the shared workaround. +[#218](https://github.com/Python-roborock/local_roborock_server/issues/218) + +### Qrevo S Pro (a326), firmware 02.49.24 + +On **v1.2.1-1-gc177a76**, Let's Encrypt RSA-2048 with +YR1 → ISRG Root YR → ISRG Root X1 worked. HA retrieved status and maps after +re-authentication. Pi-hole initially ignored queries from the routed IoT subnet; +allowing that subnet's DNS requests resolved it. The onboarding PC also needed +a hosts-file entry and routing adjustment while attached to the robot hotspot. +HA's local re-authentication asks for the configured PIN under the label +"verification code"; it sends no email. Stale MQTT credentials can be logged +until this step completes. See [HA setup](home_assistant.md#existing-roborock-integration-repointing-from-cloud). +[#156](https://github.com/Python-roborock/local_roborock_server/issues/156) + +### QRevo Pro (a101), firmware 02.15.26 + +The **v1.2.1** Let's Encrypt/Caddy layer-4 setup had working HA but misleading +missing Region/NC Prepare messages in the admin page. A separate direct-TLS +Docker setup used a **ZeroSSL ECDSA P-256 wildcard** and completed NC Prepare +after three GUI cycles, with HA/LocalRock maps and controls working. Both blocked +WAN traffic. These are separate profiles, not evidence that the first status +problem was fixed. +[#171](https://github.com/Python-roborock/local_roborock_server/issues/171), +[ZeroSSL result](https://github.com/Python-roborock/local_roborock_server/issues/171#issuecomment-6589792705) + +### QRevo 2 Pro / ProX (a294) + +The **v1.2.1 HA add-on** with provided Let's Encrypt certificates (HA Let's +Encrypt add-on, Porkbun DNS-01) supported cloud-free initial onboarding, maps, +controls and room cleaning. HA reported firmware `02.33.88`, while device OTA +telemetry reported `02.37.80`; the report does not resolve that discrepancy. +On server 1.2.0, control failed with `rrcheck access denied` after about 48 hours; +1.2.1 worked after a fresh `/f/c` exchange. LocalRock room splitting worked but +room renaming did not. The first map saved after a completed run returned to dock. +[#192](https://github.com/Python-roborock/local_roborock_server/issues/192) + +On `02.40.54`, a ProX carrying a294 worked with **v1.2.1**, rootless +Podman Compose and Let's Encrypt certificates copied from Nginx Proxy Manager. +HA and LocalRock controls were confirmed. The report's public-port workaround is +not a prerequisite for compatibility; use local DNS and reachable LAN endpoints +as described in [Installation](installation.md). +[#242](https://github.com/Python-roborock/local_roborock_server/issues/242) + +### Qrevo S (a104), firmware 02.07.14 + +**v1.2.1 Docker**, with Let's Encrypt at a reverse proxy, worked without reported +functional limitations. Three attempts collected two samples and a fourth completed +pairing; repeated cycles alone were not evidence of incompatibility. +[#219](https://github.com/Python-roborock/local_roborock_server/issues/219) + +### Qrevo Edge 2 Pro / Curv 2 Pro + +Edge 2 Pro **a226, `02.33.88`** worked on the **v1.2.1 HA add-on with ZeroSSL**. +HA and LocalRock connected after fixing VLAN MQTT access and inconsistent DNS +answers from a Technitium forwarding/wildcard setup. The unpatched official app +could not log in on GrapheneOS; the reporter used fresh local onboarding instead. +Restarting LocalRock made the new vacuum appear. Resuming interrupted onboarding +was requested as a usability improvement. +[#237](https://github.com/Python-roborock/local_roborock_server/issues/237) + +The **a226, `02.43.62`** reports are explicitly +[custom-build results](tested_vacuums.md#partial-compatibility-and-custom-setups). +In #223, the cloud called the product Curv 2 Pro (numeric product ID 199). +Let's Encrypt YR1 → Root YR → ISRG Root X1 worked on Kubernetes with a server at +`6030080` plus product/plugin patches. Initial blind onboarding and HA control +worked. Camera activation subsequently used the official cloud app; re-onboarding +after cloud import hit the stale identity/credentials problem in #222. The +official iOS app needed the #221 plugin changes and the MITM/WireGuard tunnel +disabled after login. For go2rtc two-way audio, the microphone-enabled stream +had to establish the producer first; switching from an existing listen-only +producer did not enable the microphone. +[#223](https://github.com/Python-roborock/local_roborock_server/issues/223) + +In #239, a **custom ARM64 build at `02a1770`** on a Pi 5 used an apex-host opt-in, +camera-bootstrap patches, a custom L01 bridge and modified go2rtc at `990f4de`. +Let's Encrypt YE2 → Root YE → ISRG Root X2 → ISRG Root X1 covered the apex. +Video/audio worked with WAN blocked and resumed after a host reboot (about +8.5 minutes to reconnect). Camera access/PIN had been enabled in the cloud app. +No cleaning, maps, HA or post-migration official-app control was tested. +[#239](https://github.com/Python-roborock/local_roborock_server/issues/239) + +Curv 2 Pro **`02.45.78`** also has a separate **v1.2.1** success report with a +provided Let's Encrypt RSA-4096 wildcard, YR1 → ISRG Root YR, exported from +Traefik. Two onboarding cycles were needed, with about 20 minutes waiting after +the first. The report does not identify the model code or explicitly validate +camera/audio; do not carry the custom a226 camera results forward to this firmware. +[#233](https://github.com/Python-roborock/local_roborock_server/issues/233) + +### Qrevo Edge 3 Pro and Edge 2 Flow + +Edge 3 Pro, **a296 as reported, `02.32.54`**, worked through LocalRock on the +**v1.2.1 HA add-on**. Three or four cycles recovered the key and connected even +though query samples stayed at zero. The issuer was entered as **unknown**; +`cloudflare_acme` and `zerossl` settings alone do not verify the served chain. +[#246](https://github.com/Python-roborock/local_roborock_server/issues/246) + +Edge 2 Flow, **a328 as reported, `02.33.88`**, worked on the **v1.2.1 HA add-on** +with Let's Encrypt issued by the separate HA add-on using DNS-01. It had never +been connected to the official app/cloud, and mopping worked. Camera remains +unverified: the reporter could not set the PIN and received a parameter error. +Do not copy camera success from the differently named Curv 2 Flow. +[#256 and follow-ups](https://github.com/Python-roborock/local_roborock_server/issues/256) + +## Q8 Max+ + +Firmware **02.07.60** onboarded using the HA add-on and ZeroSSL via Cloudflare +DNS-01. Four signature samples across repeated cycles recovered the key; the +official HA integration connected using Manual region. pfSense supplied local +DNS, there was no reverse proxy, and no Internet port forwarding was used. +The entered server version `18.2` is unverified and must not be treated as a +local-server release number. The report confirms onboarding/HA connection rather +than an exhaustive feature test. +[#216](https://github.com/Python-roborock/local_roborock_server/issues/216) + +## China firmware and B01: keep experimental results separate + +The China G30 **a146, 02.43.88**, on **v1.2.1-3-g5b99e93**, onboards using +ZeroSSL but rejects control with `rrcheck access denied`; a China VPN did not +resolve that setup. Separate a143 and a96 failures are listed in +[Known failures](tested_vacuums.md#known-failures). +[#161](https://github.com/Python-roborock/local_roborock_server/issues/161) + +For China P20 **a184, factory 02.22.56**, #228 reports a startup `/f/c` call to +a hardcoded cloud hostname as well as renewal through `/devices/{did}/sh`. +A TLS failure before HTTP can therefore leave no `/f/c` entry in the local +server's logs. #229 reports camera hostname validation after the handshake. +#230 reports commands, map editing, schedules, camera and daily renewal checks +working in a custom intercepted setup using compromised-intermediate certificates. +That setup was never online and never updated. It establishes neither a standard +owned-domain certificate path nor a fix for already region-locked units. +[#228](https://github.com/Python-roborock/local_roborock_server/issues/228), +[#229](https://github.com/Python-roborock/local_roborock_server/issues/229), +[#230](https://github.com/Python-roborock/local_roborock_server/issues/230) + +Q7 TF+ onboarding failure in #48 remains distinct from newer experimental sc05 +results. PR #96 reports B01 bootstrap/inbound decoding on Q7 M5+, while its TF+ +follow-up uses cloud pairing and custom interception. Neither makes all Q7/Q10 +models supported. The PR discussion also contains a Q7 L5 bootloop report during +OTA probing, not successful local onboarding of that model. +[#48](https://github.com/Python-roborock/local_roborock_server/issues/48), +[PR #96](https://github.com/Python-roborock/local_roborock_server/pull/96) + +## Follow-up work remains separate + +Recording a result does not implement the requested fixes. In particular, the +admin-password UI (#110), HA external TLS (#119), Saros 20 Neo import/mode issues +(#139), zone coordinates (#148), onboarding status (#171), missing HA entities +(#191), room renaming (#192), and Edge 2 Flow camera/PIN setup (#256) remain +separate from the compatibility rows. Custom plugin and identity workarounds +(#221/#222 referenced by #223) are not stock-release guarantees. diff --git a/docs/home_assistant.md b/docs/home_assistant.md index cea2c29..68ed61b 100644 --- a/docs/home_assistant.md +++ b/docs/home_assistant.md @@ -158,6 +158,14 @@ If you would like to avoid deleting the integration, you must update the URLs in 6. Save the file and restart Home Assistant. 7. Re-enable the Roborock integration. If prompted to re-authenticate, enter your 6-digit `protocol_login_pin` as the code. +The re-authentication form calls this field **verification code**, but the local +server expects the configured `protocol_login_pin`; it does not send an email. +Until re-authentication finishes, HA can still attempt MQTT login with its old +cloud credentials and produce `invalid_mqtt_credentials` in the server logs. +If that continues after accepting the local PIN, use the troubleshooting below. +This distinction was reported in +[#156](https://github.com/Python-roborock/local_roborock_server/issues/156). + ### Troubleshooting #### Invalid MQTT Credentials diff --git a/docs/known_limitations.md b/docs/known_limitations.md index d81d24b..e6e8fcb 100644 --- a/docs/known_limitations.md +++ b/docs/known_limitations.md @@ -2,8 +2,8 @@ I have tried to copy over most functionality into this server, but some is not 100% completed. There are a few features I know are not currently working -- Vacuum camera live streaming — supported with a TURN relay and a short camera bootstrap hostname; see [camera.md](camera.md). Verified on the Saros 10R and Qrevo MaxV; other camera models may bootstrap differently and need validation. +- Vacuum camera live streaming — available with the camera/TURN implementation on `main`; see the [model-specific results](camera.md#reported-camera-results). Bootstrap, activation and audio support vary by firmware, and some reports require custom builds. The camera implementation was merged after the `v1.2.1` tag. - Firmware Updates - Schedules (Routines/Scenes do work though) -- China-market devices do not work outside of China. Their firmware checks the region they are used in (via `rrcheck`), and after local onboarding they reject ordinary commands such as `get_status` with `-10002 / rrcheck access denied`. See [#81](https://github.com/Python-roborock/local_roborock_server/issues/81). - - Some users have gotten China-market vacuums working outside China on the official cloud by routing the robot's traffic through a VPN that exits in China (the robot's WAN IP is what matters, not the phone's). See [this comment](https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum/issues/842#issuecomment-1736230673). This has not been tested with this local server yet, so it may or may not help. +- China-market devices have model/firmware-specific region and access-renewal restrictions. Unresolved a143/a146/a96 reports reject ordinary commands with `-10002 / rrcheck access denied` after local onboarding. See [known failures](tested_vacuums.md#known-failures). Factory-firmware a184 success was reported with custom interception and compromised-intermediate certificates; it does not establish support through the standard setup or resolve those other reports. + - Some users report success with the official cloud through a China-exit VPN; see [this comment](https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum/issues/842#issuecomment-1736230673). A China VPN did not resolve the G30 local-server report [#161](https://github.com/Python-roborock/local_roborock_server/issues/161), so it is not an established general workaround here. diff --git a/docs/onboarding.md b/docs/onboarding.md index 4b8e9bf..406485e 100644 --- a/docs/onboarding.md +++ b/docs/onboarding.md @@ -177,6 +177,40 @@ Everything in "What To Expect" above still applies. Some vacuums need 2-4 cycles - **The UI is stuck on "Polling...".** Give it the full five-minute timeout. Some vacuums are especially slow on the final cycle after the public key is already ready. If nothing changes, check the log pane for errors, then click Retry or Pick another vacuum. - **Server stalls or hangs during key recovery without errors.** Check your container host's resource usage. If running with tight CPU/memory limits, cryptographic recovery can max out resources and hang. Ensure the container has at least 1 CPU core and 1 GB RAM allocated. On lower resource machines, be prepared to wait longer for the public key to be determined. +### Network and resource checks + +Successful Wi-Fi association or ping does not prove that the robot can resolve +or reach the server. Recent reports identified these distinct setup problems: + +- **DNS from the robot's VLAN:** check the resolver's query log. In + [#156](https://github.com/Python-roborock/local_roborock_server/issues/156), + Pi-hole ignored queries from a routed IoT subnet. Allow queries from the intended + LAN/VLAN, keeping the resolver inaccessible from the Internet. +- **Public DNS bypass:** Saros 20X and Saros 20 Neo reporters saw no useful local + traffic until WAN access was blocked before onboarding. The Saros 20X tried + `8.8.8.8` directly. Keep local DNS, time service and the server reachable while + isolating the robot. See [#114](https://github.com/Python-roborock/local_roborock_server/issues/114) + and [#139](https://github.com/Python-roborock/local_roborock_server/issues/139). +- **Inconsistent answers or routes:** ensure the onboarding computer and robot + resolve the API hostname to the intended endpoint. Check MQTT as well as HTTPS + across VLANs. [#237](https://github.com/Python-roborock/local_roborock_server/issues/237) + had both DNS forwarding/wildcard mistakes and blocked MQTT. In #156 the computer + needed a hosts-file entry and route adjustment while connected to the hotspot. +- **Key-recovery resources:** watch CPU and memory rather than repeatedly starting + over. Increasing constrained Podman resources helped #114. A zero query-sample + counter is not itself a failure on firmware using header signatures; watch key + recovery and NC/MQTT progress as well. +- **TLS closes before HTTP or MQTT:** verify the exact served hostname and full + certificate chain against the model/firmware report. A completed TLS handshake + can still be followed by a client-side rejection before application traffic; + [PR #65](https://github.com/Python-roborock/local_roborock_server/pull/65) + reports this on S7 Pro Ultra. An empty HTTP log alone cannot identify the cause. + +Use the [report details](compatibility_reports.md) to compare firmware, chain and +deployment, rather than assuming the same retail model name implies identical +behavior. Prefer another Wi-Fi pairing cycle when prompted; successful reports +with several cycles do not imply that a full factory reset is required. + --- ## Alternative: Onboarding Via LocalRock diff --git a/docs/tested_vacuums.md b/docs/tested_vacuums.md index fc53f9c..3d3f426 100644 --- a/docs/tested_vacuums.md +++ b/docs/tested_vacuums.md @@ -4,19 +4,30 @@ Check this page alongside [Installation](installation.md) and [Onboarding](onboa 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. +A working row means the functions described in its report worked, not that every +feature was tested. See [Compatibility report details](compatibility_reports.md) +for server versions, certificate chains, setup workarounds, and remaining problems. +Camera results are tracked separately in [Camera](camera.md#reported-camera-results). +Model identifiers can be shared by several retail names; do not assume that their +firmware or certificate results are interchangeable. + ## Buying a New Vacuum? If you're looking to buy a Roborock, consider using one of my affiliate links on the [Support This Project](support.md) page. It doesn't cost you anything extra and helps keep this project going! ## Unsupported Vacuums -The following vacuums are not supported and may never be supported. +The following vacuums are not supported by the standard onboarding flow. - Roborock Q10 X5 / X5+ - Roborock Q7 M5 / M5+ - Roborock Q7 L5 - Roborock Q10 s5/ s5+ +Experimental B01 bootstrap and custom interception results are described under +[Partial compatibility](#partial-compatibility-and-custom-setups). They do not +establish support in a released, unmodified server. + ## Potentially Supported These models have not yet been confirmed working. Version `1.1.0` adds V2 onboarding support; please report your model, firmware, and certificate chain @@ -33,7 +44,19 @@ 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](https://github.com/Python-roborock/local_roborock_server/issues/48) | -| Roborock G30 China (a146, Saros 10 equivalent) | `02.43.88` | Onboards and connects over MQTT, but the vacuum rejects commands with `-10002 rrcheck access denied`. The region-locked vacuum is not in the cloud import. | [#161](https://github.com/Python-roborock/local_roborock_server/issues/161), [#182](https://github.com/Python-roborock/local_roborock_server/issues/182) | +| Roborock G30 China (a146, Saros 10 equivalent) | `02.43.88` | Onboards and connects over MQTT, but the vacuum rejects commands with `-10002 rrcheck access denied`. The region-locked vacuum is not in the cloud import. | [#161](https://github.com/Python-roborock/local_roborock_server/issues/161) | +| Roborock G20S Ultra China (a143) | `02.52.78` | HTTPS/MQTT onboarding works, but status requests return `-10002 rrcheck access denied`. Needs model/firmware-specific retesting after access-renewal changes. | [#81](https://github.com/Python-roborock/local_roborock_server/issues/81) | +| Roborock G20S China (a96) | Unknown | Some identity RPCs work, but status RPCs return `-10002` followed by `unknown_method`; reported on server 1.0.2. This is a different model from a146. | [#182](https://github.com/Python-roborock/local_roborock_server/issues/182) | + +## Partial compatibility and custom setups + +| Vacuum / firmware | Tested scope | Limits and source | +|---|---|---| +| Qrevo Edge 2 Pro / cloud alias Qrevo Curv 2 Pro (a226), `02.43.62` | Let's Encrypt accepted; onboarding and HA control, official iOS video, and go2rtc two-way audio reported. | Custom server at `6030080` with product/plugin patches; activation used the cloud app. Forced-relay media was not verified. [#223](https://github.com/Python-roborock/local_roborock_server/issues/223) | +| Qrevo Edge 2 Pro (a226), `02.43.62` | Let's Encrypt accepted; fresh camera startup, video and two-way audio with WAN blocked, including recovery after host reboot. | Custom server at `02a1770`, apex-host/bootstrap changes, modified go2rtc and a custom L01 bridge. Cleaning, docking, maps, HA and official-app control after migration were not tested. [#239](https://github.com/Python-roborock/local_roborock_server/issues/239) | +| China P20 (a184), factory `02.22.56` | Commands, maps/editing, schedules and camera reported working fully local without initial cloud registration. | Custom interception using certificates derived from a compromised intermediate, not a normal publicly issued certificate for an owned domain. Factory firmware, never updated. This does not resolve the a143/a146/a96 failures above. [#228](https://github.com/Python-roborock/local_roborock_server/issues/228), [#229](https://github.com/Python-roborock/local_roborock_server/issues/229), [#230](https://github.com/Python-roborock/local_roborock_server/issues/230) | +| Q7 M5+ (sc05), firmware not reported | Experimental B01 bootstrap, MQTT connection and inbound decoding. | Unmerged [PR #96](https://github.com/Python-roborock/local_roborock_server/pull/96); outbound commands/maps and the alternate RSA request branch are outside its reported scope. | +| Q7 TF+ (sc05), `03.01.80` | Local operation including HA reported after initial cloud pairing. | Custom HTTPS/MQTT interception with compromised-intermediate certificates; not the standard onboarding flow. [PR #96 follow-up](https://github.com/Python-roborock/local_roborock_server/pull/96#issuecomment-6428123943) | ## Supported Vacuums @@ -54,14 +77,15 @@ Cloudflare can provide DNS validation for several certificate issuers. Its use a | Roborock S5 Max | `02.16.62` | ❓ | ✅ | ❓ | ❓ | [#3](https://github.com/Python-roborock/local_roborock_server/issues/3#issuecomment-5450368775) | | Roborock S5 Max (s5e) | `02.16.68` | ❓ | ✅ | ❓ | ❓ | [#146](https://github.com/Python-roborock/local_roborock_server/issues/146) | | Roborock S6 | `02.33.88` (`3.5.8_2700`) | ❓ | ✅ | ❓ | ❓ | [#158](https://github.com/Python-roborock/local_roborock_server/issues/158) | -| Roborock S6 Pure (a08) | `02.13.68` | ❓ | ✅ | ❓ | ❓ | [#191](https://github.com/Python-roborock/local_roborock_server/issues/191) | +| Roborock S6 Pure (a08) | `02.13.68` | ❓ | ✅ | ❌ | ❓ | [#191](https://github.com/Python-roborock/local_roborock_server/issues/191), [chain-specific follow-up](https://github.com/Python-roborock/local_roborock_server/issues/191#issuecomment-6431411331) | | Roborock S6 MaxV (a10) | `01.58.02` | ✅ | ❓ | ❌ | ❓ | [#122](https://github.com/Python-roborock/local_roborock_server/issues/122) | | Roborock S6 MaxV (a10) | `01.60.52` | ❓ | ❓ | ❌ | ✅ | [#177](https://github.com/Python-roborock/local_roborock_server/issues/177) | | Roborock S6 MaxV (a10) | `02.33.88` | ❌ | ✅ | ❌ | ❓ | [#231](https://github.com/Python-roborock/local_roborock_server/issues/231) | +| Roborock S6 MaxV (a10) | `02.62.46` | ✅ | ❓ | ❓ | ❓ | [#236](https://github.com/Python-roborock/local_roborock_server/issues/236) | | Roborock S7 | Not reported | ❓ | ✅ | ❌ | ✅ | [#3](https://github.com/Python-roborock/local_roborock_server/issues/3) | | Roborock S7 (a15) | `02.16.12` | ❓ | ✅ | ❓ | ❓ | [#257](https://github.com/Python-roborock/local_roborock_server/pull/257) | | Roborock S7 MaxV | Not reported | ❓ | ❓ | ✅ | ❓ | — | -| Roborock S7 MaxV (a27) | `02.59.36` | ✅ | ❓ | ✅ | ❓ | [#49](https://github.com/Python-roborock/local_roborock_server/issues/49), [#118](https://github.com/Python-roborock/local_roborock_server/issues/118), [#129](https://github.com/Python-roborock/local_roborock_server/issues/129) | +| Roborock S7 MaxV (a27) | `02.59.36` | ✅ | ✅ | ✅ | ❓ | [#49](https://github.com/Python-roborock/local_roborock_server/issues/49), [#118](https://github.com/Python-roborock/local_roborock_server/issues/118), [#129](https://github.com/Python-roborock/local_roborock_server/issues/129), [#215](https://github.com/Python-roborock/local_roborock_server/issues/215) | | Roborock S7 Max Ultra | `02.26.80` | ❓ | ❓ | ✅ | ❓ | [#79](https://github.com/Python-roborock/local_roborock_server/issues/79#issuecomment-5637657592) | | Roborock S7 Pro Ultra (a62) | Not reported | ❓ | ✅ | ❌ | ❓ | [#65](https://github.com/Python-roborock/local_roborock_server/pull/65) | | Roborock S8 (a51) | `02.14.48` | ❌ | ❓ | ✅ | ❌ | [#46](https://github.com/Python-roborock/local_roborock_server/issues/46#issuecomment-5456737057) | @@ -81,31 +105,38 @@ Cloudflare can provide DNS validation for several certificate issuers. Its use a | Roborock Saros 20 Neo (a296) | `02.27.04` | ❓ | ❓ | ✅ | ❓ | [#139](https://github.com/Python-roborock/local_roborock_server/issues/139) | | Roborock Saros 20 Neo (a296) | `02.29.56` | ❓ | ❓ | ✅ | ❓ | [#139](https://github.com/Python-roborock/local_roborock_server/issues/139#issuecomment-6154525857), [#139](https://github.com/Python-roborock/local_roborock_server/issues/139#issuecomment-6247548897) | | Roborock Saros 20 Sonic (a279) | `02.42.52` | ✅ | ❓ | ❓ | ❓ | [#84](https://github.com/Python-roborock/local_roborock_server/pull/84#issuecomment-5701936113) | +| Roborock Saros 20 Sonic (a279) | `02.58.82` | ✅ | ❓ | ❓ | ❓ | [#217 resolved follow-up](https://github.com/Python-roborock/local_roborock_server/issues/217#issuecomment-6504895070) | | Roborock Saros 20X (a288) | `02.55.44` | ✅ | ❓ | ✅ | ❓ | [#114](https://github.com/Python-roborock/local_roborock_server/issues/114) | | Roborock G30U | `02.52.32` | ✅ | ❓ | ❓ | ❓ | — | | Roborock Q5+ (a34) | `02.06.56` | ❌ | ✅ | ❌ | ❓ | [#117](https://github.com/Python-roborock/local_roborock_server/issues/117) | | Roborock Q5 Pro | `02.04.66` | ❌ | ❓ | ✅ | ❓ | [#56](https://github.com/Python-roborock/local_roborock_server/issues/56), [#97](https://github.com/Python-roborock/local_roborock_server/issues/97) | | Roborock Q8 Max | `02.06.86` | ❓ | ❓ | ✅ | ❓ | [#70](https://github.com/Python-roborock/local_roborock_server/issues/70) | +| Roborock Q8 Max+ | `02.07.60` | ✅ | ❓ | ❓ | ❓ | [#216](https://github.com/Python-roborock/local_roborock_server/issues/216) | | Roborock QV 35A (a168) | `02.49.24` | ✅ | ❓ | ❓ | ❓ | [#119](https://github.com/Python-roborock/local_roborock_server/issues/119) | | Roborock Qrevo C (a170) | `02.16.64` | ❓ | ❓ | ✅ | ❓ | [#95](https://github.com/Python-roborock/local_roborock_server/issues/95) | | QRevo | `02.20.60` | ✅ | ❓ | ✅ | ❓ | [#75](https://github.com/Python-roborock/local_roborock_server/pull/75), [#94](https://github.com/Python-roborock/local_roborock_server/issues/94) | -| QRevo 2 Pro (a294) | `02.33.88` | ❓ | ❓ | ✅ | ❓ | [#192](https://github.com/Python-roborock/local_roborock_server/issues/192) | -| QRevo 2 Pro (a294) | `02.40.54` | ✅ | ❓ | ❓ | ❓ | [#160](https://github.com/Python-roborock/local_roborock_server/issues/160) | +| QRevo 2 Pro (a294) | `02.33.88` in HA; `02.37.80` in device telemetry | ❓ | ❓ | ✅ | ❓ | [#192](https://github.com/Python-roborock/local_roborock_server/issues/192); version discrepancy unresolved | +| QRevo 2 Pro / ProX (a294) | `02.40.54` | ✅ | ❓ | ✅ | ❓ | [#160](https://github.com/Python-roborock/local_roborock_server/issues/160), [#242](https://github.com/Python-roborock/local_roborock_server/issues/242) | +| QRevo 5AE | `02.33.88` | ✅ | ❓ | ❓ | ❓ | [#218](https://github.com/Python-roborock/local_roborock_server/issues/218) | | QRevo 3 Pro (a296) | `02.27.04` | ✅ | ❌ | ❌ | ❓ | [#170](https://github.com/Python-roborock/local_roborock_server/issues/170) | | QRevo Curv | `02.28.60` | ❓ | ❓ | ✅ | ❓ | [#60](https://github.com/Python-roborock/local_roborock_server/issues/60) | | QRevo Curv (a135) | `02.28.92` | ❓ | ❓ | ✅ | ❓ | [#110](https://github.com/Python-roborock/local_roborock_server/issues/110) | -| QRevo Curv 2 Pro | `02.45.78` | ❓ | ❓ | ✅ | ❓ | [#128](https://github.com/Python-roborock/local_roborock_server/issues/128) | +| QRevo Curv 2 Pro | `02.45.78` | ❓ | ❓ | ✅ | ❓ | [#128](https://github.com/Python-roborock/local_roborock_server/issues/128), [#233](https://github.com/Python-roborock/local_roborock_server/issues/233) | | QRevo Curv 2 Flow | `02.33.88` | ❓ | ❓ | ✅ | ❓ | [#141](https://github.com/Python-roborock/local_roborock_server/issues/141) | | QRevo Curv 2 Flow (a245) | `02.35.52` | ❓ | ❓ | ✅ | ❓ | [#187](https://github.com/Python-roborock/local_roborock_server/issues/187) | | QRevo CurvX | `02.35.88` | ✅ | ❓ | ❓ | ❓ | [#64](https://github.com/Python-roborock/local_roborock_server/issues/64) | | QRevo Edge | `02.22.52` | ❓ | ❓ | ✅ | ❓ | [#90](https://github.com/Python-roborock/local_roborock_server/issues/90) | | QRevo Edge | `02.28.60` | ❓ | ❓ | ✅ | ❓ | [#198](https://github.com/Python-roborock/local_roborock_server/issues/198) | | QRevo Edge 2 Set (a298) | `02.15.44` | ❓ | ❓ | ✅ | ❓ | [#84](https://github.com/Python-roborock/local_roborock_server/pull/84#issuecomment-5684924538), [#59](https://github.com/Python-roborock/local_roborock_server/issues/59#issuecomment-5848488145) | +| Qrevo Edge 2 Pro (a226) | `02.33.88` | ✅ | ❓ | ❓ | ❓ | [#237](https://github.com/Python-roborock/local_roborock_server/issues/237) | +| Qrevo Edge 2 Flow (a328 as reported) | `02.33.88` | ❓ | ❓ | ✅ | ❓ | [#256](https://github.com/Python-roborock/local_roborock_server/issues/256) | +| QRevo Edge 3 Pro (a296 as reported) | `02.32.54` | ❓ | ❓ | ❓ | ❓ | [#246](https://github.com/Python-roborock/local_roborock_server/issues/246); issuer unknown, ZeroSSL configured | | QRevo Edge 5V1 / S5A (a187) | `02.29.08` | ❓ | ❓ | ✅ | ❓ | [#172](https://github.com/Python-roborock/local_roborock_server/issues/172) | | QRevo MaxV | Not reported | ✅ | ❓ | ✅ | ❓ | — | | QRevo Master (a117) | `02.28.26` | ❓ | ❓ | ✅ | ✅ | [#57](https://github.com/Python-roborock/local_roborock_server/issues/57), [#82](https://github.com/Python-roborock/local_roborock_server/pull/82) | | QRevo Plus (a123) | `02.03.28` | ✅ | ❓ | ❓ | ❓ | [#112](https://github.com/Python-roborock/local_roborock_server/issues/112) | -| QRevo Pro (a101) | `02.15.26` | ❓ | ❓ | ✅ | ❓ | [#171](https://github.com/Python-roborock/local_roborock_server/issues/171) | +| QRevo Pro (a101) | `02.15.26` | ✅ | ❓ | ✅ | ❓ | [#171](https://github.com/Python-roborock/local_roborock_server/issues/171), [ZeroSSL follow-up](https://github.com/Python-roborock/local_roborock_server/issues/171#issuecomment-6589792705) | +| Qrevo S (a104) | `02.07.14` | ❓ | ❓ | ✅ | ❓ | [#219](https://github.com/Python-roborock/local_roborock_server/issues/219) | | QRevo S5V (a170) | `02.09.70` | ❓ | ❓ | ❓ | ❓ | [#52](https://github.com/Python-roborock/local_roborock_server/issues/52#issuecomment-4826867624) | | QRevo S5V (a170) | `02.16.64` | ❓ | ❓ | ✅ | ❓ | [#52](https://github.com/Python-roborock/local_roborock_server/issues/52) | | QRevo S5V (a170) | `02.33.88` | ❓ | ❓ | ✅ | ❓ | [#148](https://github.com/Python-roborock/local_roborock_server/issues/148) | @@ -115,6 +146,7 @@ Cloudflare can provide DNS validation for several certificate issuers. Its use a | QRevo Slim | `02.43.38` | ✅ | ❓ | ❓ | ❓ | [#175](https://github.com/Python-roborock/local_roborock_server/issues/175) | | QX Revo Plus (Costco version) | Not reported | ❓ | ❓ | ✅ | ❓ | [#89](https://github.com/Python-roborock/local_roborock_server/pull/89) | | QX Revo Plus (Costco version) | `02.49.24` | ✅ | ❓ | ❓ | ❓ | [#147](https://github.com/Python-roborock/local_roborock_server/issues/147) | +| QX Revo Plus (a168 as reported) | `02.27.40` | ✅ | ❓ | ❓ | ❓ | [#248](https://github.com/Python-roborock/local_roborock_server/issues/248) | | QX Revo Ultra 2 (a298) | `02.15.44` | ❓ | ✅ | ❓ | ❓ | [#193](https://github.com/Python-roborock/local_roborock_server/issues/193) | Setup notes: @@ -142,13 +174,16 @@ Setup notes: - QRevo Curv: the reporter worked around an app redirect port issue, also tracked by [PR #77](https://github.com/Python-roborock/local_roborock_server/pull/77). - QRevo Curv 2 Pro: the map initially failed to load; regenerating the server public key and re-onboarding restored it. - QRevo Curv 2 Flow: the vacuum only supports 2.4 GHz Wi-Fi. -- QRevo Pro: Home Assistant worked, but the admin page kept showing Region and NC Prepare as missing onboarding messages. +- QRevo Pro: the Let's Encrypt report had working HA but missing Region/NC Prepare in the admin page. A separate ZeroSSL ECDSA P-256 report completed NC Prepare and worked with HA/LocalRock maps; it does not establish a fix for the original status-display problem. - QRevo S Pro `02.36.38`: the successful report used an RSA-2048 Let's Encrypt certificate. An [earlier attempt](https://github.com/Python-roborock/local_roborock_server/issues/67) on the same firmware stopped before Wi-Fi configuration was sent. - QRevo S5V `02.33.88`: maps were not saved because `lab_status` was off and the LocalRock toggle was greyed out. Sending `set_lab_status` with `[{"lab_status": 1}]` from Home Assistant's `vacuum.send_command` enabled it. - QRevo Slim: the certificate was issued through Pangolin (Traefik) and reported as ZeroSSL. - 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](https://github.com/Python-roborock/local_roborock_server/issues/83). - QX Revo Ultra 2: shares its model code and firmware with the QRevo Edge 2 Set. Public key recovery used header samples while query samples stayed at 0, which is expected. +The [report details](compatibility_reports.md) retain the newer setup profiles, +camera qualifications, and unresolved requests behind these results. + ## Unlisted Vacuums 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. diff --git a/mkdocs.yml b/mkdocs.yml index 9bcc256..7dd2153 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -62,6 +62,7 @@ nav: - Known Limitations: known_limitations.md - Scene Validity Reports: scene_validity.md - Tested Vacuums: tested_vacuums.md + - Compatibility Report Details: compatibility_reports.md - Reverse Proxy: reverse_proxy.md - Custom MQTT: custom_mqtt.md - Custom Certificate Management: custom_cert_management.md From c2b50ca84b155211ec9669f54e3ad1ab70bd2f9d Mon Sep 17 00:00:00 2001 From: Luke Date: Sun, 15 Nov 2026 15:26:07 -0500 Subject: [PATCH 2/2] docs: simplify camera availability wording --- docs/camera.md | 6 ------ docs/compatibility_reports.md | 4 ++-- docs/known_limitations.md | 2 +- 3 files changed, 3 insertions(+), 9 deletions(-) diff --git a/docs/camera.md b/docs/camera.md index fb70864..4402ec6 100644 --- a/docs/camera.md +++ b/docs/camera.md @@ -4,12 +4,6 @@ Camera-capable robots can stream to a local WebRTC consumer such as [go2rtc](https://github.com/AlexxIT/go2rtc) with a `roborock://` source. Camera bootstrap, authentication and TURN all need to work. -The camera bootstrap/TURN implementation was merged in -[PR #144](https://github.com/Python-roborock/local_roborock_server/pull/144) and -[PR #155](https://github.com/Python-roborock/local_roborock_server/pull/155), after -the `v1.2.1` tag. Results below identify development/custom builds where reported; -repulling the `v1.2.1` image does not add this implementation. - ## Bootstrap DNS, ports and certificates Bootstrap depends on firmware. The tested Saros 10R (`roborock.vacuum.a144`, diff --git a/docs/compatibility_reports.md b/docs/compatibility_reports.md index 5fbcac2..bc9b715 100644 --- a/docs/compatibility_reports.md +++ b/docs/compatibility_reports.md @@ -1,6 +1,6 @@ # Compatibility report details -These notes reconcile the open compatibility reports and their follow-up comments +These notes reconcile compatibility reports and their follow-up comments as of 15 November 2026. They supplement the [tested-vacuums table](tested_vacuums.md), which retains earlier results. Observations are attributed to their reports; they are not independent hardware tests by the documentation author. @@ -100,7 +100,7 @@ WAN access was blocked, then used DHCP-provided local DNS. See ### Saros 20 Neo (a296), firmware 02.27.04 and 02.29.56 -`02.27.04` worked on **main at `94bffa7`**, Docker/Proxmox behind Traefik with +`02.27.04` worked on **server build `94bffa7`**, Docker/Proxmox behind Traefik with Let's Encrypt YR2 → Root YR → ISRG Root X1. The `02.29.56` follow-ups used **v1.2.1**, both direct TLS with an ECDSA P-384 chain YE1 → Root YE → ISRG Root X2 → ISRG Root X1 and Traefik with a YR2 chain. diff --git a/docs/known_limitations.md b/docs/known_limitations.md index e6e8fcb..b7b8c59 100644 --- a/docs/known_limitations.md +++ b/docs/known_limitations.md @@ -2,7 +2,7 @@ I have tried to copy over most functionality into this server, but some is not 100% completed. There are a few features I know are not currently working -- Vacuum camera live streaming — available with the camera/TURN implementation on `main`; see the [model-specific results](camera.md#reported-camera-results). Bootstrap, activation and audio support vary by firmware, and some reports require custom builds. The camera implementation was merged after the `v1.2.1` tag. +- Vacuum camera live streaming — available; see the [model-specific results](camera.md#reported-camera-results). Bootstrap, activation and audio support vary by firmware, and some reports require custom builds. - Firmware Updates - Schedules (Routines/Scenes do work though) - China-market devices have model/firmware-specific region and access-renewal restrictions. Unresolved a143/a146/a96 reports reject ordinary commands with `-10002 / rrcheck access denied` after local onboarding. See [known failures](tested_vacuums.md#known-failures). Factory-firmware a184 success was reported with custom interception and compromised-intermediate certificates; it does not establish support through the standard setup or resolve those other reports.