Xiaomi Robot Vacuum Binding

@JP_hess To enter your cloud details go to the bindings page, click the Xiaomi Mi IO binding and than configure.

in the page, enter your userID /passwd and county(s) or leave the countries servers blank.

@YaroKasear you first need to enter the device details manually or configure the bidning to discover the device via the cloud *which is not the default( see above the screesnhows how to get there. Als indeed in the thing you’ll need to set the communicaiton to cloud.
Note this cloud setup / communication is still immature so your milage may vary.

I’m happilly accepting your documentation improvements for the readme to explain this better for novice users…

@marcel_verpaalen: Great! It works…
I have not seen the config-button on the binding page
Thx for your support

I do not have the “Cloud Discovery Mode” selection thing on the binding configs. Is that for some development branch of the binding? I’m using the binding you can install from the add-ons page on the Paper UI.

xxaomi

it is only there from OH3 onwards. You’ll need to update to have this working.
If you’re on OH2.5 I think your only option is to move OH & the device to the same subnet

hello elfrico, where did you get the coordinates from (zKueche # type = room
zKueche # coordinates = 16

zToilette # type = room
zToilette # coordinates = 17

zLarder # type = room
zLarder # coordinates = 18

z Wardrobe # type = room
z Wardrobe # coordinates = 19

zLiving room # type = room
zLiving room # coordinates = 20

zFlur # type = room
zFlur # coordinates = 21

zPainting room # type = room
zPainting room # coordinates = 22
)

I have created rooms in my Xiaomi app and assigned them a sequence from 1 to 7.

1 Flur
2 Wohn- Esszimmer
3 Küche
4 Schlafzimmer
5 Gästezimmer
6 Badezimmer
7 WC

do you have an idea for me here?

many Greetings
Christian

Is it possible to get the number of the room the vacuum currently is cleaning?

I’m not aware that this is in the status messages.
Is it something you see visible in the mihome app?

No was just checking if i missed something :slight_smile:
Will do a request to Xiaomi and see if we can get it in to the API.
Would be really nice in the new UI to se where it is.

Unfortunately I have encountered a problem with my Robot Vaccum V1 after updating to OH 3.

Robot goes offline after the few seconds.

  • discovery delivers two results for the robot

  • took the Xiaomi Mi Device rockrobo-vacuum-v1_miio

  • put in the token

  • pressed saved

  • robot goes online

  • after a while it goes offline

  • every time I press the save button - the same

2021-01-29 12:31:54.351 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘miio:vacuum:046C6CA9’ changed from OFFLINE (CONFIGURATION_ERROR) to OFFLINE

2021-01-29 12:32:04.365 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘miio:vacuum:046C6CA9’ changed from OFFLINE to ONLINE

2021-01-29 12:33:04.454 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘miio:vacuum:046C6CA9’ changed from ONLINE to OFFLINE (CONFIGURATION_ERROR)

2021-01-29 12:34:04.544 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘miio:vacuum:046C6CA9’ changed from OFFLINE (CONFIGURATION_ERROR) to OFFLINE

2021-01-29 12:34:14.543 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘miio:vacuum:046C6CA9’ changed from OFFLINE to ONLINE

2021-01-29 12:35:14.634 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘miio:vacuum:046C6CA9’ changed from ONLINE to OFFLINE (CONFIGURATION_ERROR)

Have you checked the faq in the binding readme?
This sounds like token issue or multiple entries for the same vacuum

Does someone know if the new GUANGCAN YLXD50YL will work with the MI IO Binding?
I didn’t find information which Device model it is. I expect it to be ‘yeelink.light.ceiling10/19/20.ambi’ but I really don’t know. I actually just need a working #actions channel, the rest I can programm myself…
Does someone know? Thanks in advantage :slight_smile:

If it has wifi, and if not supported, it will still have a command channel.

As the yeelights are very similar, to controlo you almost always find a similar model substitute that will work for you.

Okay allright, I will do my best and leave some feedback if it works or not!
Thanks again marcel :slight_smile:

i have the exact same problem as @BigMountainSki.
also running last openhab3. and it worked before.

i got a new phone, so i had to repair the device in my xiaomi app on my phone and thought it was linked to this. but reading this, i guess it is not the case.

i have only one entry with this token.

could it be, by any chance, linked to this mdns issue ?

What you can try is to remove the thing and add it again. Make sure your vacuum is online and do a new discovery.
Suggest to add the entry without _miio

Yes, if not supported, be sure to try the ’ add experimental support’ switch as that will build a dB file for your device based on the responses from it

Thank you!
I think the token should be alright - because it’s the old one and if I use the other generic device in the inbox it shows the token.
Will it show online for a short time with an invalid token?
And yes I’ve checked the FAQ - but the App changed a bit - I was not able to cross check the token!

Invalid token will be online for bit (as it can detect the device at the right IP) than goes to offline-configuration error (as it con’t communicate)

@marcel_verpaalen : Thank you for your support :grinning:
it was my fault…What i did to get it running - may be for others:

  • install the binding
  • configure the binding - enter my xiaomi accoutdata: username and password and server, chose dicovery online for supported devs
    (configuration is a bit hidden on the bottom - so you have to look for it…)
  • go to the inbox
  • choose the Xiaomi Mi Device … rockrobo-vacuum-v1_miio… with token
  • easy peasy :+1:
  • no need to extract the token anywhere
1 Like

Thanks Marcel for the advice :slight_smile:
i tried, multiple time. removing all previous xiaomi devices from openhab. adding from discovery and also manually. same problem.