Xiaomi Robot Vacuum Binding

binding
vacuum
xiaomi
Tags: #<Tag:0x00007f0156cf6468> #<Tag:0x00007f0156cf6328> #<Tag:0x00007f0156cf61c0>

(marcel) #920

you can this a try as command
sunset

set_scene["cf",3,1,"50,1,16731392,1,360000,2,1700,10,540000,2,2700,100"]

sunrise

set_scene["cf",3,2,"50,2,2700,10,180000,2,1700,5,420000,1,16731136,1"]

and (havn’t tried it) I gues if you send the "cf",3,2,"50,2,2700,10,180000,2,1700,5,420000,1,16731136,1" to the channel miio:basic:CeilingBedRoom:customScene you most likely get the same…

Note check out https://www.domoticz.com/wiki/Yeelight ‘adding scenes’ section for some of the examples


(JustAProgrammer) #921

Has anyone ever got the set_music command to work on the Yeelights?
It needs to declare a Server + port for the signal income.
My first attempt was to plug a microphone into my Pi and start the command, but didn’t work sadly.
Would have been to easy.
I’ve read that something called “FFT” is needed to interpret frequencies.
Working on it but help is appreciated :slight_smile:


(Brian M. Pedersen) #922

like this:


I don’t get any responce… :confused:


(Adam Menzel) #923

Hi Guys

I have successfully changed from the Yeelight Binding to the MI IO Binding due to the Yeelight Binding not working reliably. Everything is working great except for one thing. At exactly the same time, 9:58pm within a few seconds everyday both of my Yeelight Strips turn off & back on in about half a second. I do have rules configured to reduce the brightness over the evening on both devices and there is a rule configured to run at 10:00pm which does run correctly.

I did not have this issue using the Yeelight Binding & i am using the same rules. There is nothing in the logs except the following which is not triggered by a rule:

2019-01-06 21:58:36.295 [vent.ItemStateChangedEvent] - MasterBedroomLEDStrip_Brightness changed from 70 to 50

I have set the default state to 50% so that the light does not come on at 100% when it powers off & on.

Running OpenHAB 2.4.0 on Windows 10

Any help would be great


(Simon) #924

Hey, since when do you have the problems?

Got the same phenomenom that all my yeelights periodically restart themselves.
Since i dont get any infos in the logs i assumed it would be a faulty firmware or any other local problem.

But since you seem to have the same problem. I think mine started with upgrading to 2.4 stable


(Denis) #925

Hello.

I have the same problem with a number of lamps I use in home automation:

  • philips.light.candle
  • philips.light.candle2
  • philips.light.downlight
  • yeelink.light.ceiling3
  • philips.light.bulb

All the listed lamps periodically reboot, and, if they were turned on, a short flash may occur. A reset is also indicated by a decrease of uptime (network#life channel).
It was experimentally observed by me that the periodicity of the reset depends on the refresh interval of the lamps. If the refresh interval is carried out every 15 seconds, then the reboot occurs once an hour. If the survey is once a minute, then reboot once every 3 hours.


(Adam Menzel) #926

Hi Simal

Mine are definitely playing up & restarting randomly with this binding. Twice last night at different times. This did not happen with the Yeelight binding on 2.4.0 but is with the MI IO binding.


(marcel) #927

The only think I can think of that may trigger this behaviour would be that the auto incrementing msg id gets to big for the lamps and it resets them…
If anyone has good log when this happens it would be nice to better understand what goes wrong


(Denis) #928

Yes, Marcel, you are right. A reboot occurs when the message id becomes greater than 1000.
Here is the part of the log with the moment of reboot in 2019-01-11 08:49:08

2019-01-11 08:48:53.410 [DEBUG] [inding.miio.handler.MiIoBasicHandler] - Periodic update for 'miio:basic:0579FB3D' (miio:basic)
2019-01-11 08:48:53.410 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:48:53.414 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:48:53.415 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Command added to Queue {"id":994,"method":"get_prop","params":["power","bright","cct","snm","dv"]} -> 192.168.192.141 (Device: 0579FB3D token: 940727BFACFFB98CF172A4DFA58698D7 Queue: 1)
2019-01-11 08:48:53.416 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:48:53.418 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:48:53.419 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Command added to Queue {"id":995,"method":"get_prop","params":[]} -> 192.168.192.141 (Device: 0579FB3D token: 940727BFACFFB98CF172A4DFA58698D7 Queue: 2)
2019-01-11 08:48:53.419 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:48:53.422 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:48:53.423 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Command added to Queue {"id":996,"method":"miIO.info","params":[]} -> 192.168.192.141 (Device: 0579FB3D token: 940727BFACFFB98CF172A4DFA58698D7 Queue: 3)
2019-01-11 08:48:53.423 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:48:53.426 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:48:53.448 [DEBUG] [ing.miio.handler.MiIoAbstractHandler] - Received response for 0579FB3D type: GET_PROPERTY, result: ["off",30,1,0,0], fullresponse: {"result":["off",30,1,0,0],"id":994}
2019-01-11 08:48:53.455 [DEBUG] [ing.miio.handler.MiIoAbstractHandler] - Received response for 0579FB3D type: GET_PROPERTY, result: [], fullresponse: {"result":[],"id":995}
2019-01-11 08:48:53.469 [DEBUG] [ing.miio.handler.MiIoAbstractHandler] - Received response for 0579FB3D type: MIIO_INFO, result: {"life":9201,"token":"940727bfacffb98cf172a4dfa58698d7","mac":"7C:49:EB:3A:19:38","fw_ver":"1.3.0_0021","hw_ver":"ESP8266","uid":2147483647,"model":"philips.light.downlight","wifi_fw_ver":"1.5.0-dev(7f7a714)","ap":{"rssi":-34,"ssid":"B.S.O.D.","bssid":"DC:9F:DB:8D:85:6C"},"netif":{"localIp":"192.168.192.141","mask":"255.255.255.0","gw":"192.168.192.254"},"mmfree":4128}, fullresponse: {"result":{"life":9201,"token":"940727bfacffb98cf172a4dfa58698d7","mac":"7C:49:EB:3A:19:38","fw_ver":"1.3.0_0021","hw_ver":"ESP8266","uid":2147483647,"model":"philips.light.downlight","wifi_fw_ver":"1.5.0-dev(7f7a714)","ap":{"rssi":-34,"ssid":"B.S.O.D.","bssid":"DC:9F:DB:8D:85:6C"},"netif":{"localIp":"192.168.192.141","mask":"255.255.255.0","gw":"192.168.192.254"},"mmfree":4128},"id":996}
2019-01-11 08:48:58.427 [DEBUG] [inding.miio.handler.MiIoBasicHandler] - Periodic update for 'miio:basic:0579FB3D' (miio:basic)
2019-01-11 08:48:58.427 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:48:58.432 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:48:58.432 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Command added to Queue {"id":997,"method":"get_prop","params":["power","bright","cct","snm","dv"]} -> 192.168.192.141 (Device: 0579FB3D token: 940727BFACFFB98CF172A4DFA58698D7 Queue: 1)
2019-01-11 08:48:58.433 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:48:58.435 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:48:58.436 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Command added to Queue {"id":998,"method":"get_prop","params":[]} -> 192.168.192.141 (Device: 0579FB3D token: 940727BFACFFB98CF172A4DFA58698D7 Queue: 2)
2019-01-11 08:48:58.437 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:48:58.439 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:48:58.488 [DEBUG] [ing.miio.handler.MiIoAbstractHandler] - Received response for 0579FB3D type: GET_PROPERTY, result: ["off",30,1,0,0], fullresponse: {"result":["off",30,1,0,0],"id":997}
2019-01-11 08:48:58.495 [DEBUG] [ing.miio.handler.MiIoAbstractHandler] - Received response for 0579FB3D type: GET_PROPERTY, result: [], fullresponse: {"result":[],"id":998}
2019-01-11 08:49:03.440 [DEBUG] [inding.miio.handler.MiIoBasicHandler] - Periodic update for 'miio:basic:0579FB3D' (miio:basic)
2019-01-11 08:49:03.441 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:49:03.443 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:49:03.444 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Command added to Queue {"id":999,"method":"get_prop","params":["power","bright","cct","snm","dv"]} -> 192.168.192.141 (Device: 0579FB3D token: 940727BFACFFB98CF172A4DFA58698D7 Queue: 1)
2019-01-11 08:49:03.444 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:49:03.449 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:49:03.450 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Command added to Queue {"id":1000,"method":"get_prop","params":[]} -> 192.168.192.141 (Device: 0579FB3D token: 940727BFACFFB98CF172A4DFA58698D7 Queue: 2)
2019-01-11 08:49:03.451 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:49:03.453 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:49:03.514 [DEBUG] [ing.miio.handler.MiIoAbstractHandler] - Received response for 0579FB3D type: GET_PROPERTY, result: ["off",30,1,0,0], fullresponse: {"result":["off",30,1,0,0],"id":999}
2019-01-11 08:49:03.521 [DEBUG] [ing.miio.handler.MiIoAbstractHandler] - Received response for 0579FB3D type: GET_PROPERTY, result: [], fullresponse: {"result":[],"id":1000}
2019-01-11 08:49:08.454 [DEBUG] [inding.miio.handler.MiIoBasicHandler] - Periodic update for 'miio:basic:0579FB3D' (miio:basic)
2019-01-11 08:49:08.454 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:49:08.457 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:49:08.457 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Command added to Queue {"id":1001,"method":"get_prop","params":["power","bright","cct","snm","dv"]} -> 192.168.192.141 (Device: 0579FB3D token: 940727BFACFFB98CF172A4DFA58698D7 Queue: 1)
2019-01-11 08:49:08.458 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:49:08.460 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:49:08.461 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Command added to Queue {"id":0,"method":"get_prop","params":[]} -> 192.168.192.141 (Device: 0579FB3D token: 940727BFACFFB98CF172A4DFA58698D7 Queue: 2)
2019-01-11 08:49:08.461 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:49:08.464 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:49:08.539 [DEBUG] [ing.miio.handler.MiIoAbstractHandler] - Received response for 0579FB3D type: GET_PROPERTY, result: ["off",30,1,0,0], fullresponse: {"result":["off",30,1,0,0],"id":1001}
2019-01-11 08:49:13.465 [DEBUG] [inding.miio.handler.MiIoBasicHandler] - Periodic update for 'miio:basic:0579FB3D' (miio:basic)
2019-01-11 08:49:23.555 [DEBUG] [nal.transport.MiIoAsyncCommunication] - No response from device 0579FB3D at 192.168.192.141 for command {"id":0,"method":"get_prop","params":[]}.
2019-01-11 08:49:23.555 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:49:23.556 [DEBUG] [ing.miio.handler.MiIoAbstractHandler] - Received response for 0579FB3D type: GET_PROPERTY, result: null, fullresponse: {"error":"No Response"}
2019-01-11 08:49:23.558 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:49:23.559 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Command added to Queue {"id":1,"method":"get_prop","params":["power","bright","cct","snm","dv"]} -> 192.168.192.141 (Device: 0579FB3D token: 940727BFACFFB98CF172A4DFA58698D7 Queue: 1)
2019-01-11 08:49:23.559 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:49:23.562 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:49:23.562 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Command added to Queue {"id":2,"method":"get_prop","params":[]} -> 192.168.192.141 (Device: 0579FB3D token: 940727BFACFFB98CF172A4DFA58698D7 Queue: 2)
2019-01-11 08:49:23.563 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Sending Ping 0579FB3D (192.168.192.141)
2019-01-11 08:49:23.565 [DEBUG] [nal.transport.MiIoAsyncCommunication] - Ping 0579FB3D (192.168.192.141) success
2019-01-11 08:49:23.664 [DEBUG] [ing.miio.handler.MiIoAbstractHandler] - Received response for 0579FB3D type: GET_PROPERTY, result: ["off",30,1,0,0], fullresponse: {"result":["off",30,1,0,0],"id":1}
2019-01-11 08:49:23.674 [DEBUG] [ing.miio.handler.MiIoAbstractHandler] - Received response for 0579FB3D type: GET_PROPERTY, result: [], fullresponse: {"result":[],"id":2}

(Denis) #929

I will correct myself. Reboot occurs when a command with id 0 comes to the device.

data: 21310050000000000579fb3d00002400a86449b828ddf6b7a685b8bb161591d32a915cf8ea212c6c31971073ea76d9e393a4889047ab5565d4d4839951cb8b48d4c6aaef00d5a6beed2b4403e7c0f974
decoded data: {"id":0,"method":"get_prop","params":[]}

I also noticed one oddity - before each request for data, the exchange of hello-packages occurs three times.

21310070000000000579fb3d000023fbbabfc609e3fbce0cea939cab7060953bd93b41af0bef4b233d88ca77e14fe2096531f6a4a0e79edb2b77759f7e271b7f95cfad5e26332990d51938f264873bc504a5332cfec05f9fcbd709b99cfa05cee84134fa79cad14a290e1f09e5914052
21310050000000000579fb3d000023fb88bfe46b1425807551a824e97c132486c0450b535685a9fe975abe57a41df13d0bfa7960e17292b72ea1ef1403a13d12dce2dadf3ec5c596240fa2ce64c3e7da
21310050000000000579fb3d000023fb504b5f42c9cb59b2364e7f4a3971de5cc712963513e745bf23cfa32e1ed1d06c55cdf3c41ea6a4984cc6b9d518414d91d925e8dd5d0f57f03b0e3393b1758277
21310040000000000579fb3d000023fb86e2e9c45c8b5f1c04e7e809887a792adca0347a32c9e892b85ecf9f9b3873817052d37caf574674cbc1e4df6c44b954
21310020ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
21310020000000000579fb3d0000240000000000000000000000000000000000
21310020ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
21310020000000000579fb3d0000240000000000000000000000000000000000
21310020ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
21310020000000000579fb3d0000240000000000000000000000000000000000
21310070000000000579fb3d0000240097edc892e18417c86e7b3b7ba5d360dd25874e812e59c192a8a3b254baa11a6411c4bd852069b14468d9b55c91c3787ee81a10465a4562c1baef39cd0f48e0c0cb1d2e0c983b5711ed7b5a9470208249a5ae5175a1c77bd9e69874142a06eaea
21310050000000000579fb3d000024002e577e4c2f7ab44ee94de5c617a7758fc0450b535685a9fe975abe57a41df13d0bfa7960e17292b72ea1ef1403a13d126e21e78c6ec9f957cfc7fa400861d94c
21310050000000000579fb3d00002400a86449b828ddf6b7a685b8bb161591d32a915cf8ea212c6c31971073ea76d9e393a4889047ab5565d4d4839951cb8b48d4c6aaef00d5a6beed2b4403e7c0f974
21310020ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
21310020000000000579fb3d0000000f00000000000000000000000000000000
21310020ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
21310020000000000579fb3d0000000f00000000000000000000000000000000
21310020ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
21310020000000000579fb3d0000000f00000000000000000000000000000000
21310070000000000579fb3d0000000f6837d449a100c33bd35de07b07b16b6c6f988e6605fc6a0069c6ebe32f873476055bd1da6f307a98761a352e10bc24bac767a9338d4e55281b97b1e749c43649e82060d0b24d5abb5f33b58115167fac1d3a59305ee666133de71dbe5f502351
21310050000000000579fb3d0000000f6a1098680688034acb760166a9b5ecafc0450b535685a9fe975abe57a41df13d0bfa7960e17292b72ea1ef1403a13d1281a014dd416ff2e3c6cbf4c9ed1260e4
21310050000000000579fb3d0000000f9aa1af5b96928a15e69ac5dbb8333af61a25457e2b58e7a050dc4f3256bc082300d22bd3925c3e66e2a8abfbadd81b12e90ea837b216cd4e7b5c61f8e79332f6
21310040000000000579fb3d0000000f1bbd2999382824feae795d3825fd7157dca0347a32c9e892b85ecf9f9b3873818ab02f2fec488340bf6316b534ba87ba
21310020ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
21310020000000000579fb3d0000001400000000000000000000000000000000
21310020ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
21310020000000000579fb3d0000001400000000000000000000000000000000
21310020ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
21310020000000000579fb3d0000001400000000000000000000000000000000
21310070000000000579fb3d000000143f7a579e9440abbb5344e4db9804ed3cd8901650e1f2e65fb1f8c4f5b70200c24524900d0182e33218dc94066d8128fcc4a6dbed535552ef159142e30fa9484d07606d43ee312198b3c996d0fbfb9bbcb4abbb99d7f8082240e7e431d2e0700c
21310050000000000579fb3d0000001473228c32e56e056f19eccf410bfa9595c0450b535685a9fe975abe57a41df13d0bfa7960e17292b72ea1ef1403a13d1240ed8e84b3542258c851ff201e2861e3
21310050000000000579fb3d00000014933e3e3cdb6ded4bba2e536afe9f1d6343487f4b2f5ce15a5fd84401330f72c9ddbf09afa4968e9705301380d49d30f6ed8fc6b8b4799bf4ce8711fb3c26e9bb
21310040000000000579fb3d000000145ad90c15aa0bf67663e74aef9150ddb0dca0347a32c9e892b85ecf9f9b387381726d5ced10a744a7b047f67f3747f5d6

(Denis) #930

After I changed the queueCommand() function in the MiIoAsyncCommunication class:

id.set(-1);

to

id.set(0);

lamp reboots have stopped.

I suggest you make this change in the next release.
Thank.


(JohnD) #931

2019-01-11 21:32:12.893 [WARN ] [nal.transport.MiIoAsyncCommunication] - Could not parse '{"result":["on"net],"id":151}' <- {"id":151,"method":"get_prop","params":["power","bright","ambstatus","ambvalue","dvalue"]} (Device: 032B2AD1) gave error com.google.gson.stream.MalformedJsonException: Unterminated array at line 1 column 17 path $.result[1]

what’s the matter?


(marcel) #932

Thanks for testing… I’ve submitted the PR for this.


(marcel) #933

Your device gave indeed a strange response:
{"result":["on"net],"id":151} is indeed not valid json. what sort of device is it?


(Denis) #934

I get similar errors (no more than once every three days):

2018-12-26 20:32:13.861 [WARN ] [nal.transport.MiIoAsyncCommunication] - Could not parse '{"result":{"life":652431,"token":"e3dc7618a4880ef26f48f3b09b3e3584","mac":"34:CE:00:AA:BB:CC","fw_ver":"1.6.2","hw_ver":"MTK7697","uid":"4152651":"DC:9F:DB:XX:Yimi.humidifier.ca1","mcu_fw_ver":"1029","wifi_fw_ver":"20180702211408","ap":{"rssi":-64,"ssid":"MyWifiSsid","bssid":"DC:9F:DB:XX:YY:ZZ"},"netif":{"localIp":"192.168.192.112","mask":"255.255.255.0","gw":"192.168.192.254","gw_mac":"34:CE:00:DD:EE:FF"},"mmfree":65232},"id":660}' <- {"id":660,"method":"miIO.info","params":[]} (Device: 03B84D27) gave error com.google.gson.stream.MalformedJsonException: Unterminated object at line 1 column 147 path $.result.uid

Here is a Json string that cannot parse:

{"result":{"life":652431,"token":"e3dc7618a4880ef26f48f3b09b3e3584","mac":"34:CE:00:AA:BB:CC","fw_ver":"1.6.2","hw_ver":"MTK7697","uid":"4152651":"DC:9F:DB:XX:Yimi.humidifier.ca1","mcu_fw_ver":"1029","wifi_fw_ver":"20180702211408","ap":{"rssi":-64,"ssid":"MyWifiSsid","bssid":"DC:9F:DB:XX:YY:ZZ"},"netif":{"localIp":"192.168.192.112","mask":"255.255.255.0","gw":"192.168.192.254","gw_mac":"34:CE:00:DD:EE:FF"},"mmfree":65232},"id":660}

Here is the answer from the same device at regular time:

{"result":{"life":139848,"token":"e3dc7618a4880ef26f48f3b09b3e3584","mac":"34:CE:00:AA:BB:CC","fw_ver":"1.6.2","hw_ver":"MTK7697","uid":"4152651639","model":"zhimi.humidifier.ca1","mcu_fw_ver":"1029","wifi_fw_ver":"20180702211408","ap":{"rssi":-64,"ssid":"MyWifiSsid","bssid":"DC:9F:DB:XX:YY:ZZ"},"netif":{"localIp":"192.168.192.112","mask":"255.255.255.0","gw":"192.168.192.254","gw_mac":"34:CE:00:DD:EE:FF"},"mmfree":65544},"id":91}

(Adam Menzel) #935

Hi Marcel

Where can I download the latest build of the binding to test if it resolves my issue with my Yeelights?


(marcel) #936

It is merged now, so if you update to the latest snapshot version of the binding it should be in.


(marcel) #937

@pitonmd indeed seems that the response is invalid as the ,"model": part between the uid and the model is lost for the lines that gave a json error.

I think this is a firmware issue rather than a binding issue (as I would be surprised the string in java gets corrupted on the way, and this string is what is being decrypted)


(Giovanni Guadagnini) #938

Hi, I extracted the token from my Xiaomi Roborock S50 in this way:

After getting the token I tryed to set the token inside the openHAB page. In the first time it seems working but after two minutes from ONLINE the message become OFFLINE - CONFIGURATION_ERROR. How can I fix this?
Thank you in advance.


(marcel) #939

@Giovanni_GuadagniniActually you could have used OH to get the token that way. It will do it for you.
However, this method is not really useful anymore for most devices. The token will change as soon as you connect it to the regular network with the app.

The best way to get the token in Android is to use either the hacked mihome app, or downgrade to old version and pull it from the app database. Or use the IOS app database.