Support for viomi.vacuum.v10

[yogiee]

Please add support for viomi.vacuum.v10 device.

[merdok]

Should be straight forward! Will add support for that vacuum in the next update!

[merdok]

@yogiee can you tell me what the official name of that vacuum is?

[yogiee]

@yogiee can you tell me what the official name of that vacuum is?

It's called Mi Robot Vacuum Mop P.

https://www.mi.com/in/mi-robot-vacuum-mop-p/

[merdok]

Perfect! Thanks!

[merdok]

Added in version 0.9.4. Please try it out and let me know if everything works.

[yogiee]

Awesome, will test it out.

[yogiee]

Okay, so the device shows up in the homekit as it did before, but still not functional. Initially it shows battery low (robovac is on the charging dock and full battery), when powered on, following error is generated in Homebridge log. Also attaching the screenshots from homekit app.

[6/20/2021, 2:56:18 AM] [miot] [Mi Robovac] Poll failed 4 times in a row! Stopping polling and trying to reconnect! [6/20/2021, 2:56:18 AM] [miot] [Mi Robovac] Connected to device: viomi.vacuum.v10 [6/20/2021, 2:56:18 AM] [miot] [Mi Robovac] Setting up device! [6/20/2021, 2:56:18 AM] [miot] [Mi Robovac] Doing device specific setup [6/20/2021, 2:56:18 AM] [miot] [Mi Robovac] Doing initial property fetch [6/20/2021, 2:56:18 AM] [miot] [Mi Robovac] Device setup finished! Device ready, you can now control your device! [6/20/2021, 2:56:40 AM] [miot] [Mi Robovac] Poll failed 4 times in a row! Stopping polling and trying to reconnect! [6/20/2021, 2:56:40 AM] [miot] [Mi Robovac] Connected to device: viomi.vacuum.v10 [6/20/2021, 2:56:40 AM] [miot] [Mi Robovac] Setting up device! [6/20/2021, 2:56:40 AM] [miot] [Mi Robovac] Doing device specific setup [6/20/2021, 2:56:40 AM] [miot] [Mi Robovac] Doing initial property fetch [6/20/2021, 2:56:40 AM] [miot] [Mi Robovac] Device setup finished! Device ready, you can now control your device!

[merdok]

You need to provide a homebridge debug log, ideally with the deepDebugLog property enabled. Without that there is no way for me to know what is wrong...

[yogiee]

deepDebugLog

I enabled deep debug log, but not sure where exactly to find it? I'm running homebridge in docker setup and I checked the volume where homebridge settings are stored. I could only find standard homebridge log file.

[merdok]

deepDebugLog will only work when you start homebridge in debug mode. So you need to start your homebridge as described in the README with the -D flag: homebridge -D

[yogiee]

Yeah, figured that out while exploring homebridge settings. Here's the log.

log file

[merdok]

Seems like the device is most probably not a miot device but a an older miio device, for that reason you need to use MiCloud. You need to specify your MiCloud credentials, the country where your device is located and enable the "Force MiCloud connection" button. If that will work, then i will mark your device as a MiCloud device in the next update.

[yogiee]

Seems like the device is most probably not a miot device but a an older miio device, for that reason you need to use MiCloud. You need to specify your MiCloud credentials, the country where your device is located and enable the "Force MiCloud connection" button. If that will work, then i will mark your device as a MiCloud device in the next update.

Aha, I see. Checked MiCloud connection, however, my country (in, and i2) is not listed in the supported countries on this plugin.

[merdok]

You would need to temporary move your vacuum to the china server then and test it out.

[yogiee]

You would need to temporary move your vacuum to the china server then and test it out.

Cool, will try that out and report. Thanks.

[merdok]

Just let me know if it works. If it will then i will mark the device as a MiCloud device and add the in (i suppose India?) server to the list.

[yogiee]

Just let me know if it works. If it will then i will mark the device as a MiCloud device and add the in (i suppose India?) server to the list.

Yes, there are two listings that I saw in token_extracter app. in should be India, but by default the devices were added to i2 servers.

[merdok]

What country are the i2 servers in? A secondary India server?

[yogiee]

What country are the i2 servers in? A secondary India server?

Apparently both in and i2 are for India region, according to OpenHAB doc.

https://www.openhab.org/addons/bindings/miio/#country-servers

[merdok]

👍 Makes sense

[yogiee]

So apparently even after your update and trying to jump between regions in my Mi Home app, I couldn't get the Robovac working. However, I noticed that now by Robovac is listed on 3 different servers (CN, US and i2).

Sorry for the off-topic question, but is there any way to remove devices from different region servers (if not, just remove everything and start over)?

[merdok]

As far as I know adding the device to one server, should remove it from another. Not sure if you can remove all device from a server... maybe in the xiaomi home app?

[yogiee]

So after lot of tinkering and meddling with region, I'm happy to report that I've finally managed to get it working with MiCloud connection option and while the options are limited just a simple starting and stopping the vacuuming run works just fine and should be more than enough to map to HomeAssistant server to set automation schedules. Thanks a lot mate for quick update to the plugin.

[merdok]

Thanks for the info! Good to hear! You should also be able to enable modes with the modeControl property. Anyway in that case I will mark the device as a MiCloud device on the next update!

[merdok]

The device is now marked as MiCloud required as of version 0.9.6!