The tokens for both Xiaomi product that I access via this binding are of exactly the same length, I’ve replaced some numbers in letters in the original and posted it below.
What is strange is that it used to work previously, and even yesterday, after my first post where I stated the problem, it kinda sorted itself out. But today the same error returned without me doing anything.
Dear all,
I am somehow lost and hope you can help me:
The thread is called “Xiaomi Robot Vacuum Binding” while the openhab docu calls it “Xiaomi Mi IO Binding”. Is it the same thing with different names or are the two different bindings?
The official docu states the option for cloud connection but using version 2.5 (the latest one) this is not shown in paper UI - any hint?
Hallo @Matthias_Kaufmann it is the same thing…
The binding started only with vacuums, later the basic part was added and it became miio binding.
The current release 2.5.4 and 2.5.5-snapshot have cloud functionality. Go to the binding list in paperUI and you see the possibility to enter your credentials.
Look in this thread about 2 months back and you see some screenshots of it.
Hello, the mapping does not appear in openhab. I’ve seen cloud related topics in previous comments but I can’t get them to work. Can you help me? Thanks in advance.
2020-04-30 21:55:18.724 [WARN ] [nal.transport.MiIoAsyncCommunication] - Error while polling/sending message
java.lang.ArrayIndexOutOfBoundsException: null
at java.lang.System.arraycopy(Native Method) ~[?:1.8.0_211]
at org.openhab.binding.miio.internal.MiIoCrypto.iv(MiIoCrypto.java:52) ~[bundleFile:?]
at org.openhab.binding.miio.internal.MiIoCrypto.encrypt(MiIoCrypto.java:74) ~[bundleFile:?]
at org.openhab.binding.miio.internal.transport.MiIoAsyncCommunication.sendCommand(MiIoAsyncCommunication.java:257) ~[bundleFile:?]
at org.openhab.binding.miio.internal.transport.MiIoAsyncCommunication.sendMiIoSendCommand(MiIoAsyncCommunication.java:173) ~[bundleFile:?]
at org.openhab.binding.miio.internal.transport.MiIoAsyncCommunication$MessageSenderThread.run(MiIoAsyncCommunication.java:232) [bundleFile:?]
for me it helped changing the token in my *.things file (changing a letter, saving, changing back and saving)
I had the issue after update to 2.5.4
thank you for the information.
I went through some learnings I want to share in case they are relevant for others:
You have to use Mi Home app, Roborock app is not supported (check out the difference of the apps here)
I was not aware that openhab 2.5.4 (or later) is required for the cloud functionality. I had 2.5.0 and upgraded. This brought up the cloud config parameter in paper Ui that have been missing before
All vacuums use the same channels. Look for the v1 example
Dnd channel is a read only channel at the moment, so indeed changing will not send anything to your vacuum. If I recall well it is due to the fact it requires you to send the time in the command, not simply on or off
thank you for the hint. I got my roborock S5 Max working via cloud and use the advanced command quite a lot to set volume, read room ids, send the robot for room specific cleaning etc. I use this page as you linked it at the beginning of the thread.
Trying to activate and deactivate DND is use the DND timer. Interestingly there are just times, no enabling itself.
So I tried the following three command, all with a OK response but when checking the DND status afterwords, the old values (8 to 22) are sent:
[12,01,12,00] => as documented
[0,12,01,12,00] => adding a 0 for deactivation at the beginning as this is the response format (just trying it out)
[12,01,12,00,0] => adding a 0 for deactivation at the end as this is part of the response I receive (see this: {“result”:[{“start_hour”:22,“start_minute”:0,“end_hour”:8,“end_minute”:0,“enabled”:0}],“id”:8126})
That is nothing to worry about. It just means that the binding itself is not knowing the command, however as you can see your vacuum respond with something 201. Don’t know what it means, but that is the water_box_custom_mode it seems
the binding seems to have stopped working (with the last OH update, i think) for my Mi Air Purifier 2S. I’ve checked the token hasn’t changed (it hasn’t).
if you are using text config, add the model= to your config. Something seems to have changed in the OH framework that it now does no longer work without.
@marcel_verpaalen something is wrong with my yeelights color v1.As soon as i changed brightness from number to dimmer i have this problem: by moving the brightness slider at PaperUi i can dim and bright from 1 to 99 and back .If i try to do it using a rule i can dim ,for example from 99 to 20 but i can not bright from 20 to 99.I give a sendCommand(99) to brightness but nothing happens and at log i get
2020-05-05 21:06:08.645 [vent.ItemStateChangedEvent] - YeelightColorBulb1_Brightness changed from 20 to 99
2020-05-05 21:06:08.918 [vent.ItemStateChangedEvent] - YeelightColorBulb1_Brightness changed from 99 to 20
