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.
In your discover does it have the things " with token" in the description. If no, the cloud connectivity is not working yet for you. You either need to get the cloud info setup right or get the tokens with alternative methods.
If it has, and you went throught the suggestions in the binding readme FAQ, share a debug log, than maybe it is possible to detect what’s going on.
Thanks for your persistance Marcel!
You were right and the FAQ helped!
Indeed my device was previously registered in CN, and without paying attention, with my new phone i registered in BE (server DE hence). After updating the binding config to use only DE servers, and restarting openhab (it was giving an error while adding the thing otherwise), it works like a charm!
Nah, that has not been discussed earlier. (cropped yes, but as this graphics programming is not really my area of expertise I did not dive into that yet)
Might be a good idea indeed. Would be great if you could try it out and make a PR
