Onboarding report: Qrevo S5V with Let's Encrypt

[Kruemmelkeks]

Since the QRevo S5V is still listed as "Not reported yet" in the tested vacuums: Works great with Let's Encrypt-Certificate!

I just finished the whole process. The biggest issue was to set up the server itself since I never had to set up a server with SSL-certifcate. The rest was pretty much going according to instructions.

Robot
Reportet as roborock.vacuum.a170, Firmware is 02.16.64 (most recent one).

Onboarding:
Had to do 3 cycles, plus one final cycle.

The only issue I see in the Local Server Log is that there are two steps that seem to be missing in the onboarding process:

As far as I can see that does not affect the robot's function. Everything else is fine and available. I do not use the Mobile App anymore though, just keeping it on Home Assistant, so no idea if anything there might be affected.

Documentation-Improvement:
I struggled a little bit to find the config folder for the Roborock Integration, because it was hidden. The File Editor Configuration hides this folder by default, so you cannot see it. You have to remove the highlighted ignore-pattern in the config first. Other Editors like VSCode Studio Server seem to do similiar things by default.

Maybe you can add a note to the information regarding that :)

If you need any more info, just let me know.

Thanks for the great work!

[hacsjalano]

I'm just starting out with this same exact model - did you have difficulties onboarding the robot? I have reset the wifi through several cycles, and I appear to be stuck - the onboarding script says the public key is generated, but it never claims to see the robot connect. Each time I reset the Wifi, it sits for about 4 minutes then finally announces verbally "wifi connected" but the script doesn't see anything.

The status on the server shows the robot is not connected, and it is also waiting for the same 2 steps to be completed that you showed in your screenshot - "region" and "nc_prepare".

[Kruemmelkeks]

Hm no, I dod not have any issues like that. I has to do the first cycle twice because I endet in a timeout, but after that each cycles gained some more progress.
For me it was also much faster than 4 minutes for reconnecting the wifi.
Do you have the same firmware version? And how did you set up the robot before trying to migrate to the local server?

[hacsjalano]

Okay, so it turns out this was due to something I did. Because I already have OPNsense running ACME and Lets Encrypt to get my wildcard SSL certificate, I run all of my HTTPS services through the Haproxy service on OPNsense and I was trying to avoid having another SSL certificate/ACME service possibly compete with that, so I tried sending the local server port 555 traffic and MQTT 8881 traffic through haproxy.

Haproxy can handle the 555 traffic just fine, but the MQTT 8811 traffic had some sort of issue that I could never work out, so I gave up and ended up using the built-in acme client. Now everything works.

My robot came firmware V02.09.70 out of the box and that's the version I'm using. So far I don't see any issues with it. I've hooked it up to Home Assistant via the Roborock integration and have the iPhone Roborock official app connected to the robot after doing the process outlined using MITM and Wireguard.