I can reproduce this behavior. It happens every time you create a vacuum thing, and change the suggested UID thing name to a custom one.
I am not on the marketplace version of the binding, but on the official 5.1.0 release version and I reproduced it with an saros 10R.
Hi Paul, All my channels are read or written. Even the routine mapping and the floor mapping. Thiis is the only channel which remains empty (NULL). I f I look in the trace logs, this is the one closest to what you describe:
org.openhab.binding.roborock.internal.RoborockVacuumHandler
Received MQTT message: {“t”:1768141230,“dps”:{“102”:“{“id”:20475,“result”:[[16,“8694029”,13],[17,“8694028”,6],[18,“8693296”,12],[19,“9693435”,12]]}”}}
You are right. When I change the name of the vacuum thing to the DUID, it is working. At least I get values for most of the channels. That’s however not the way I prefer to name my things. Did someone already create an issue on github for that?
[roborock] Set 'representation-property' correctly in things.xml to prevent items being rediscovered by psmedley · Pull Request #20028 · openhab/openhab-addons · GitHub will fix this once approved.
https://smedley.id.au/tmp/org.openhab.binding.roborock-5.2.0-SNAPSHOT.jar contains the latest fixes.
Let me check behaviour on my S7 Pure. Confirmed this is broken….. Working on a fix, it’s funky code so bear with me…
Edit: [roborock] Fix Room mapping channel by psmedley · Pull Request #20046 · openhab/openhab-addons · GitHub is the fix, URL in post previous to this has the fix.
Hi,
my whole setup is very declarative (all in files,if possible no interaction with the UI). I configured the roborock integration like that:
Bridge roborock:account:account \[ email="<my_mail>.com", twofa=“123456” \] {
roborock:vacuum:QrevoS \[ refresh=5, duid=“<duid data>” \]
}
Unfortunately, it does not allow setting the twofa via file. In the UI it is then displayed as blank and sends another verification mail. I always try my files from a fresh installation. Anything I am missing?
It’t working via files, that’s what I did to. First create the Bridge with only the e-mail. When you get the mail add the “twofa” and it should become online (maybe you have to stop and start the thing via the UI for that). After that add the vacuum thing.
but it does not work stateless. I am not sure if this is a limitation of the roborock API or the implementation.
Scenario that does not work:
The token file is stored in /var/lib/openhab/json-db (or something like that). Moving this file across as well as the things file should work provided the thing-id is kept the same.
Hi!
perhaps a stupid question, but is the Q10 S5 also supported by the binding?
cheers
Andreas
Not a stupid question - the Q7 and Q10 series use different protocols to other vacuums. Support for this is planned (time permitting) once the Homie and/or python-roborock implementations are complete.
Hi,
I‘m trying to build a Dashboard for cleaning different rooms of my house in different cleaning modes. I‘m thinking about some switches in my Main UI to configure what the robot has to clean, and finally send commands via „executeCommand“ to the robot.
As I figured out in this thread, there is a command called „app_segment_clean“ which tells the robot which rooms should be cleaned. I‘m looking for commands for changing the active map and for selecting the cleaning mode like „vac&mop“ or only „vac“.
Is there a documentation about the available commands or a tutorial? Or has maybe anyone figured out which commands I have to send e. g. for the following scenario:
Regards,
Boris