Indeed, thanks,
Note that it may be a more generic issue somehow as I can see also
Hi all, I just upgraded my roborock sw to 3.3.9_001702 version, but the binding is no longer able to control or retrieve data from robot. Where’s the problem? How can I have a look to the binding logs? Thanks in advance.
To look at the logs
execute these in the karaf console:
log:set debug org.openhab.binding.max
log:tail org.openhab.binding.max
bundle:restart org.openhab.binding.max
I can just say, that I got my first roborock s50 yesterday with the same firmware. works like a charm. maybe your token changed?
1 Like
beginner question: do I see this correctly that the DND (do not disturb) function cannot be set via any channel? It seems the channels are READ-ONLY
Indeed, it is not supported by the binding. If you want to switch on/off the DND you can do so by making a rule and send the right command via the command channel
e.g. set_dnd_timer [22,0,8,0] [start hour, start minutes, end hour, end minutes]
1 Like
thanks a lot, but this goes beyond my expertise. I know how to write rules but what is “set_dnd_timer”? In general I wonder myself where I can find more information about available commands?
see the Sending custom commands in the very first topic for some more info on sending commands and which commands are known. In this (long) topic you find several examples of folks writing rules for it
1 Like
fantastic! wouldn’t it make sense to copy/paste this to the binding documentation?
using the instructions and links above I noticed that the fan modes are differnet for my vacuumer.
Doc says:
| Mode | Level |
|---|---|
| Quiet | 38 |
| Balanced | 60 |
| Turbo | 75 |
| Max | 100 |
| Mob | 105 |
But in my case (Roborock S50) it’s
| Mode | Level |
|---|---|
| Quiet | 101 |
| Balanced | 102 |
| Turbo | 103 |
| Max | 104 |
| Mob | 105 |
Is this a “known issue”?
1 Like
You were right. Thanks. For an unknown reason the token changed 
1 Like
I cant add this item ‘items/XiaomiMiRoborockVacuum_Cleaning_CleaningFinished’ with an invalid item type ‘Boolean’ because it i preset as an boolean
@StefanH yes, more or less. Though I did not have the correct mapping confirmed though.
My understanding is that the above 100 values are the mobbing modes, where the vacuum is actually slower than in the ‘usual modes’. Is that correct?
not sure I can follow. As far as I could see, I can just control fan power, not speed. In the original Mi Home app this is called Cleanup Mode. The different fan settings are named like MAX or Mob. In Mob setting, the fan is just turned off. This way the roborock will make no noise, just mob
Hi all, I noticed a slowdown in the reactivity of the vacuum to the commands sent through the binding with the latest fw update. Do you notice the same issue?
Hi,
i got this aqara camera hub.
https://www.gearbest.com/ip-cameras/pp_978606.html
It has the device id lumi.camera.aq1
guys at python miio seem to have integrated it allready:
https://python-miio.readthedocs.io/en/latest/miio.html#module-miio.aqaracamera
could you add support for this camera?
Does anybody know how to resume a cleaning or zoned cleaning?
Did you ever find out how to do this? Or does anyone else know how to resume a zone cleaning?
1 Like
@Simsal looks indeed like it could be supported as a basic device.
Maybe you can give it a try and attempt to create a database file for it see the linked example
For me, with the version 3.3.9_001720 of the fw of the robot, this binding sometimes does not work and sometimes is very slow.
Sorry, my fault. Misconfiguration of the subtype parameter roborock.vacuum.s5 that caused a bad configuration error.