logs please and I’ll confirm
Installed manually because no device appears during scanning.
Unfortunately, it is not possible to adjust the log settings under Add-on Settings, as nothing is displayed there.
Yes, absolutely. I’ll give it another try sometime during the next days 
Thanks!
Thanks for pointing that out. Infact I also did this previously when using the miio binding. But since Paul’s binding is using the cloud at the moment (hopefully he can implement local connection soon ), right now probably not needed.
Thanks!
You can adjust the log level of the binding in the karaf console, e.g.:
log:set TRACE org.openhab.binding.roborock
It’s definitely on the to-do list for a rainy day, however, my preference is to first make sure the cloud connection is stable and works for multiple people, and get that code accepted into the OH repository, then raise purther PR’s for other incremental improvements.
1 Like
I mainly may this as I didn’t think through how the marketplace worked when I was added the git checksum to the filename, and got caught out myself on one of my systems.
Something like:
sudo find / -name org.openhab.binding.roborock*.jar
on a *nix box will find any possible variations.
Hey!
Thanks for the usefull binding! Got it working and my S8 is found via UI-Scan.I managed to setup channels and the information within the channels is updated.But, and sorry this might be a stupid question, how can I trigger the robot to start cleaning from openHAB?
- For my understanding the actions#command channel is used to send commands to my device. I’m executing:
openhab:send actionCommand app_start
The value of the item referencing the channel is updated, but nothing more is happening…
My first problem is to figure out which commands are supported, I read through the MIIO Binding, but I cant find commands for the Roborock’s.
I’d love if someone can explain how to start to robot from openHAB the same way as pressing the play button in the Android App.
I’m not sure the ‘plumbing’ is there yet for actions#command, I’ll take a look in the morning
There is a Channel called ‘Control Vacuum’ this is presets for Vacuum, Pause, Dock and Spot Clean.
A WIP Readme is at https://github.com/psmedley/openhab-addons/blob/roborock/bundles/org.openhab.binding.roborock/README.md
Thank you! This was exactly what I’m looking for.
I red the page you linked here, but didn’t find any of the command values.
But this will be good to add in the docs I guess.
Not sure what you mean by ‘command values’?
The values of the command (Vacuum, dock, …)
ahhh. They should be visible in the GUI - in my sitemap, I just have:
Switch item=Roborock_Qrevo_S_Control_Vacuum label="Downstairs Qrevo S”
and the GUI correctly shows me the available options…
btw I fixed this so it works now. Previously, only the rpc (ie cloud) command was ‘plumbed in’.
For now, both the command and rpc command do the same thing, ie send commands via the cloud.
1 Like
here are the logs:
20250816_Log_Roborock.txt (11.8 KB)
Looks like an authentication issue:
08:44:16.661,"TRACE","org.openhab.binding.roborock.internal.RoborockWebTargets","JSON response: '{""msg"":""username or password error"",""data"":null,""code"":2012}'"
you ARE using an email/password from the Roborock app and not one from the Xiaomi Home app?
A bit embarrassing. It was the wrong password.
But now another challenge:
Logs:
Restart has already been done, just in case.
Maybe try clearing cache?
I’ve also fixed the code to detect a failed login and go offline (and report the message).
Okay. I found it!
That maybe a way to receive this information. But this are fix values, so why not document them?
I’m expecting possible variable values in the documentation.
Anyway, the binding is running great and its very usefull to me. Thank you so much for your effort, I was waiting such a long time to use the Roborock in openHAB as well. Now it works so well.
1 Like