@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…
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.
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
No was just checking if i missed something
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.
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
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!
@marcel_verpaalen : Thank you for your support
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
Thanks Marcel for the advice
i tried, multiple time. removing all previous xiaomi devices from openhab. adding from discovery and also manually. same problem.