Got my robot cleaner (Ver 2) yesterday. At first didn’t notice that I need version 5.0.19 to get the token so i’ve wasted some time trying to get it …
After switching to version 5.0.19, I’ve got the token immediately (didn’t need to use main china land, other works fine).
As I am defining all things only via configuration files (and not using paperUI), it took me some time to find the Thing definition and now IT IS WORKING
Is “miio:basic:…” the right word for the item or can i also use other words? Maybe “light”? Is this only cosmetic or is there a functional difference also?
@halloween miio:basic: is indeed the right thingtype.
The basic type is for all devices that have their definition coming from the database entries.
The 3rd part of the thingId you can make whatever you like, it does not need to be the number which you have right now ( e.g. miio:basic:strip1:power)
Can I somehow enable Air Purifier 2S (this is newer version os AP 2 with PM2.5 sensor and OLED screen). Currently it is discovered as Unsupported device. I hope that interface is the same as for old version at least beside the PM sensor readout. I would be happy to control 2S just like 2.
You can add it manually as basic device and update the model string in the config to one of the older models which is supported e.g. to zhimi.airpurifier.v6
You can try different models to see which best match your device.
Let me know which one it it and your exact model string then I can add it to the db
AirPurifier 2S is detected as zhimi.airpurifier.ma2. Adding basic device and configuring it as zhimi.airpurifier.v6 worked like a charm. Even LED control turns on/off the OLED screen. Thank you very much for solution.
I cannot add link to miio:basic:e208e4cf:bright and miio:basic:e208e4cf:filterlife, but it’s not a problem. Everything else seams to work fine.
Let me know if and how I could help in adding 2S officially.
I took a quick look at the code. It may be something as simple as closing clientSocket in stopReceiverThreat instead of (or in addition to) the calls to interrupt/join. I think that will cause an IOException in receiveData, which is caught and will cause the receiver thread to exit.
I’ve running the binding now for months and it worked really fine. Yesterday i switched my openhab to docker an now i can’t control my vaccuum and i get no state updates. The paper ui shows me that everything is online. Nothing can be seen in the logs.
Any ideas how i can find out whats going wrong?
How would this look like for every single consumable?
I’ld like to reset the brush, the sensors , etc. individually for my vacuum cleaner. Is this possible?
I updated to latest Mi Home and latest Mi firmware as this enables zone cleaning also in my v1 vacuum. However, now I lost control of the cleaner in openhab. Is there any way to use openhab even with latest firmware, e.g, without going back to 5.0.19?
i had a working wifi plug which ai lost contact with. It still worked in the mi home app, the only thing out of place i noticed was the IP address had changed. I have removed it and readded it in the mi home app and also removed from OH. It is no longer discovered - anyone have any ideas?
Also wondering if the token issue people are seeing in Android is a probelm for IOS users?