Damn perfekt - sorry for my bad english im from germany and no native speaker 
So that means if I tag all with alexa tags i could also say alexa clean my livingroom and it only clean the living room ? You have also an example for this ? Where can i find out the coordinates ?
I will order me a S1 and first of all it should create a map or ? Than I could find out anywhere the coordinates ?
Sure, that is what I do:
Switch XiaomiRobotVacuum1SStartStop_Proxy_WZ_Alexa "Staubsauger Wohnzimmer" { alexa="PowerController.powerState" }
rule "XiaomiRobotVacuum1SStartStop_Proxy_WZ_Alexa"
when
Item XiaomiRobotVacuum1SStartStop_Proxy_WZ_Alexa received command
then
if (receivedCommand==ON) {
XiaomiRobotVacuum1SActionsCommands.sendCommand("app_zoned_clean[[26200,24500,30000,28500,1],[24800,28500,30000,33300,1]]")
XiaomiRobotVacuum1SActionsFan.sendCommand(104)
}
else XiaomiRobotVacuum1SActionsCommands.sendCommand("app_charge")
end
My living room is not rectangle, it is kind of L shaped, so the best is to divide it into two rectangles.
I took a screenshot of that, opened it in Sketch and overlaid grids to draw out the x and y-axis. This provides a rough estimate for all the coordinates in the house.
Also sometimes the data received by the Air Purifier is wrong. Like 73 celsius degree inside 
Again a bundle refresh solves this…
You van try the option above, or you can install flolevac: https://xiaomi.flole.de/&ved=2ahUKEwi90dy-zurlAhU_wAIHHWmHB3cQFjAAegQIAxAB&usg=AOvVaw1djp8vh__TzZYAmBOcTsym that has the option to get the coordinates by clicking on a button;)
There were reports in another thread this does not work anymore … I can’t confirm as I did not try that.
Setting VSC to save in UTF-8 format solved all problems.
Is it possible to somehow combine actions#fan and status#fan_power into single item that both accepts command and show current value, so that it can be used as Selection on habPanel ? Or must I doit via rules and proxy item?
hi,
I got the same error as @fishi0x01 with the Roborock S6 fw 3.5.4_850
Do you have any idea how to fix this?
I run out of ideas
Cheers
Yannick
Command added to Queue {"id":49,"method":"miIO.info","params":[]} -> 192.168.1.10 (Device: XXXXXXX token: XXXXXXX Queue: 1)
2019-11-26 05:02:38.337 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping XXXXXXX (192.168.1.10)
2019-11-26 05:02:38.344 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping XXXXXXX (192.168.1.10) success
2019-11-26 05:02:53.421 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Communication error for Mi device at 192.168.1.10: Receive timed out
2019-11-26 05:02:53.422 [DEBUG] [nal.transport.MiIoAsyncCommunication] - No response from device XXXXXXX at 192.168.1.10 for command {"id":49,"method":"miIO.info","params":[]}.
2019-11-26 05:02:53.427 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping XXXXXXX (192.168.1.10)
2019-11-26 05:02:53.433 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping XXXXXXX (192.168.1.10) success
2019-11-26 05:02:53.436 [DEBUG] [internal.handler.MiIoAbstractHandler] - Received response for XXXXXXX type: MIIO_INFO, result: null, fullresponse: {"error":"No Response"}
2019-11-26 05:02:53.444 [DEBUG] [internal.handler.MiIoAbstractHandler] - Error received: "No Response"
2019-11-26 05:03:08.347 [DEBUG] [o.internal.handler.MiIoVacuumHandler] - Skipping periodic update for 'miio:vacuum:XXXXXXX' UID 'CONFIGURATION_ERROR'. Thing Status
Is the mihome app still working for you?
There are some reports that they are tying the robot’s to specific country servers, which means they are no longer responding to some of the commands.
In that case, you could try to tie the robot to mainland china server and it may work again.
note… it is a bit of a long shot. but miIO.info command is quite significant to have a response, as that is what the binding is using for some of the auto configuration.
hello marcel,
yes it works with the Mihome app
With my version of Mihome 5.4.54 the S6 or S5 doesn’t show on the mainland china Server, but it listed on all the other server.
I tried many servers, but I still got the same error.
tonight I’ll try the latest version of MiHome to see if there is any change.
Thank you for your help
my Roborock v1 goes online and few minutes later it goes offline and stays offline !?
how can i fix that ?
2019-11-29 01:21:58.297 [hingStatusInfoChangedEvent] - 'miio:vacuum:79fafdbd' changed from OFFLINE to ONLINE
2019-11-29 01:22:58.382 [DEBUG] [nding.miio.handler.MiIoVacuumHandler] - Periodic update for 'miio:vacuum:79fafdbd' (miio:vacuum)
2019-11-29 01:22:58.446 [hingStatusInfoChangedEvent] - 'miio:vacuum:79fafdbd' changed from ONLINE to OFFLINE (CONFIGURATION_ERROR)
2019-11-29 01:23:28.531 [DEBUG] [nding.miio.handler.MiIoVacuumHandler] - Skipping periodic update for 'miio:vacuum:79fafdbd' UID 'CONFIGURATION_ERROR'. Thing Status
2019-11-29 01:23:58.616 [DEBUG] [nding.miio.handler.MiIoVacuumHandler] - Skipping periodic update for 'miio:vacuum:79fafdbd' UID 'CONFIGURATION_ERROR'. Thing Status
Now:
Status: OFFLINE - CONFIGURATION_ERROR
@RiotMode this is a typical wrong token error…
The IP is right, but token not.
Use the hacked russian app to get the right token
thanks, but i dont have an android device here. only iphones, windows and mac.
i got the key out of the iPhone Backup
i used sqlite like in the post above, but maybe i am wrong there. i somewhere found a solution just with looking into the sql-file via TextEdit.app, but cant remember where. i see a lot in it, but i cant really spot the token, i somewhere found an explanation on how to get the token out of this text, but cant find it
EDIT:
OK i got it finally - thank you @marcel_verpaalen
just a little info, if you have 2 countries (servers) set up like me in mihome.app.
In my case China and Germany Server, you get just the current Devices and Tokens based on your server settings in your iPhone Backup. so i have redone my iphone backup with Germany-Server (mihome.app) and now i have the correct vaccuum token in my .sqlite File.
@Edit 2: @marcel_verpaalen
it was working, i’ve seen all values in my sitemap. and now again - Communication Error
ON / OFF/ SPOT / DOCK = still possible in OH but no values at all
Hi
I installed the binding yesterday to control my new Roborock S5 vacuum. I got the token and all and to my content it worked right off the bat. I installed it via Paper UI, created thing and items to control, check state and battery also via Paper UI and I also tested the control via Paper UI control tab. Later that day (like two hours later) control stopped working (without me even touching it) and state never updated. I tried removing everything including binding, reconfiguring again and same thing. Battery status updates but control doesn’t work and state stays the same.
I went through this thread to find some useful info so I tried logging and I found out that the binding is actually sending commands to robot, but only state requests (I guess that’s how it updates the battery level). But when I issued my command there was no communication from binding to vacuum at all. The log said the control item updated when I issued the command, then later it updated again to the previous state.
My guess is there is some issue with either item to thing or thing to binding communication. Any ideas I can try? Any debug I can run?
@marcel_verpaalen, Could you pay attention to my post above?
For customization, I use text files. Tell me, did I misconfigure something that I have so many informational messages? Why are things added to the inbox every time, because they are configured through text files?
ADD: For example, I use chromecast binding, also configured through text files. My chromecast is always hanging in my inbox (I don’t know if this is correct or not), but there are no messages at boot that it was added to my inbox.
Thanks!
Bindings supporting autodiscovery will scan for devices even it configured through text files.
That is the reason for the “Ignore” button in PaperUI. Just hit them for all devices where you have text files configured.
But these messages are not related to autodiscover (perhaps):
2019-12-01 16:53:19.887 [INFO ] [internal.handler.MiIoAbstractHandler] - Mi Device model yeelink.light.color1 identified as: Yeelight Color Bulb (yeelink.light.color1). Matches thingtype miio:basic
2019-12-01 16:53:19.891 [INFO ] [internal.handler.MiIoAbstractHandler] - Mi Device model yeelink.light.color1 identified as: Yeelight Color Bulb (yeelink.light.color1). Matches thingtype miio:basic
2019-12-01 16:53:19.896 [INFO ] [internal.handler.MiIoAbstractHandler] - Mi Device model yeelink.light.mono1 identified as: Yeelight White Bulb (yeelink.light.mono1). Matches thingtype miio:basic
2019-12-01 16:53:19.901 [INFO ] [internal.handler.MiIoAbstractHandler] - Mi Device model yeelink.light.mono1 identified as: Yeelight White Bulb (yeelink.light.mono1). Matches thingtype miio:basic
2019-12-01 16:53:19.899 [INFO ] [internal.handler.MiIoAbstractHandler] - Mi Device model yeelink.light.color1 identified as: Yeelight Color Bulb (yeelink.light.color1). Matches thingtype miio:basic
2019-12-01 16:53:19.898 [INFO ] [internal.handler.MiIoAbstractHandler] - Mi Device model yeelink.light.mono1 identified as: Yeelight White Bulb (yeelink.light.mono1). Matches thingtype miio:basic
2019-12-01 16:53:44.855 [INFO ] [internal.handler.MiIoAbstractHandler] - Mi Device model roborock.vacuum.s5 identified as: Mi Robot Vacuum v2 (roborock.vacuum.s5). Matches thingtype miio:vacuum
I’m trying to find out, maybe they say that I configured something wrong? What are these messages about? They are displayed at every restart of openHAB.
I did this, but after I physically disconnect the bulbs from the network and then turn them on again, things will again appear in the inbox not hidden. And in the journal there will be entries:
2019-12-01 17:48:15.505 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'miio:basic:0335FA38' to inbox.
2019-12-01 17:48:15.511 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'miio:basic:03360ED4' to inbox.
2019-12-01 17:48:15.513 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'miio:basic:0332CD19' to inbox.
2019-12-01 17:48:15.520 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'miio:basic:0335E030' to inbox.
2019-12-01 17:48:15.523 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'miio:basic:0335C499' to inbox.
2019-12-01 17:48:15.526 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'miio:basic:0335C161' to inbox.
If I click ignore (hide it in my inbox) on the chromecast, then unplug it from the wall outlet, plug it back into the network, it will not appear in my inbox, but will remain in the ignore status.
Update to my issue reported above, status is reported correctly. I ran vacuum today and both battery and status work. But commands are still not sent.
I’m seeing this for my manually added vacuum cleaner, too. As it is just an INFO message, I would not care about it as long as everything is working okay.
I cannot comment on this as I don’t physically disconnect my devices.