Either download the one in post Xiaomi Robot Vacuum Binding (if you use this, please send me a debug log file so the issue can be better understood)
or disable the map channel & Cloud functionality (=no userId/password), which will make it behave as before the new functionality was introduced.
First I want to thank you for this great binding, now here comes the questions:
Is there a way to configure the binding username and password through config files rather than paperui?
EDIT: Why am I sometimes getting duplicated commands when clicking a switch:
2020-05-13 18:18:52.298 [nt.ItemStatePredictedEvent] - MiPowerPlugPower predicted to become OFF
2020-05-13 18:18:52.336 [vent.ItemStateChangedEvent] - MiPowerPlugPower changed from ON to OFF
2020-05-13 18:18:53.672 [vent.ItemStateChangedEvent] - MiPowerPlugPower changed from OFF to ON
2020-05-13 18:19:06.899 [vent.ItemStateChangedEvent] - MiPowerPlugPower changed from ON to OFF
This makes the switch on the basic ui pannel to “flicker” when I click on it.
Can I pair this plug directly to OpenHAB without the Xiaomi App? As currently I can’t discover it as a thing in PaperUI if I don’t have it paired on my phone with the Xiaomi App. EDIT: I guess not, as I saw the switch needs to be connected to WiFi first, and the only way to do that is through the Xiaomi App, correct?
This may happen if there are still unprocessed commands in the queue for the device. So if your device still has a properties refresh in the queue, executing that will cause the UI to switch back (the plug did not yet receive the command you executed), after that the command is executed, changing the switch state, the following refresh will update the UI to the new state that you were expecting.
Note that some of the powerplugs have rather poor wifi causing lot of connection losses and delayed execution. I’ve seen similar behavior indeed with my plug.
and indeed… there little possibility to connect without first using Xiaomi app.
(in theory you can, but you need to connect to your plug’s wifi, you could control it that way. If you are ready to experiment you can issue the commands to change the wifi settings and hope that the binding cloud connectivity picks up the new token… note: untested territory but probably possible)
I tried everything, but I don’t get my vacuum roborock s6 to work with the mi io binding.
The Thing shows the follwoing status no matter what I do.
Status: OFFLINE - COMMUNICATION_ERROR No Response from device
I already updated openhab from 2.4 to the latest 2.5.5 and reinstalled the mi io binding (2.5.5). (Because the roborock s6 was not listet in the binding version 2.4) I created the thing via paper ui, deleted that, created it via thing file… nothing works.
I took the token from an old mi home app version.
Anyone an idea? I read that a few of you get it to work with the s6…
Btw.: Via mobile the vac can be controlled as normal.
code 70016 = wrongs userID/Password. Double check your credentials.
@masterds163 try to get the right token via the cloud. Your error is typical for wrong token.
the S6 should be recognized as vacuum with the 2.5.5 binding.
If issues persist, share a debug log… bug again, if there are no responses, the token is wrong.