Xiaomi Mi Vacuum - Unavailable Status

ltoolio · January 13, 2018, 10:01pm

Hey all -
Just got my V1 Xiaomi and am trying to set it up in Home Assistant.

I have it all setup with the Mi Home App so all good there.

I’ve extracted the Token from my phone and have verified it to be consistent across two computers - one Win 10 machine and one Ubuntu Machine.

I’m pretty sure I have the right info in my configuration.yaml file:

vacuum:
  - platform: xiaomi_miio
    name: 'R2D2'
    host: 192.168.86.36
    token: AbUnChOfNuMbErSaNdLeTtErS

But no joy…it keeps showing up in the HA UI as Unavailable:
Screenshot from 2018-01-13 15-56-27

And in the logs it shows issues with connecting and fetching the state:

I’ve found a few bug reports related to the vacuum, but they don’t seem to be the same as what I’m experiencing. Anyone have any idea what’s up?

ulesin · February 2, 2018, 7:04am

Hi!

Did you find the solution? How do you have set the configuration.yaml and groups.yaml? Thanks so much!

Skeletorjus · February 2, 2018, 7:46am

Unsure if OPs issue is related, but there have been some issues with Miio that made vacuums unavailable.
I fixed this by manually editing device.py in the miio-folder (where this is depends on your mode of installation) to reflect these changes: https://github.com/rytilahti/python-miio/pull/192/commits/9368d8b766bb811a6308c39fe0b6fd217942b6a4
Others have downgraded construct and made it work that way.
Some more info here: 61.1 seems to have broken xiaomi_miio

ltoolio · February 2, 2018, 9:14pm

I fixed it with the info in this link.

TraktorS2 · June 3, 2019, 12:31am

Hi mate, is that with hassio? The solution I saw has a pip command. Assuming that means it won’t work on hassbian.

I’ve got the same problem of unavailable and cannot work to how to fix it

DonNL · June 23, 2019, 8:36am

Hello everyone, sorry to bring up an old topic but I can’t seem to get my Roborock S50 back running in HASSIO.

I think it started after I used DHCP addon on HASSIO (since my router only allows 10 ip reservations). Since then I updated HASSIO to the lastest version.

I noticed my vacuum didn’t work anymore in HASS, since it wouldn’t respond to the commands given to Google home anymore.

I’ve did several resets, a wifi reset, factory reset and every time took the token from the device with MiToolkit 1.6. Using SSH HASSIO can ping the roborock, but in the logs it still states
“Got exception while fetching the state: Unable to discover the device 192.168.1.249”

What could be wrong? Fairly frustrated here…

Information:
Home Assistant 0.94.4

Roborock:
3.3.9_001768

Corky876 · June 25, 2019, 3:52pm

Any luck? I just upgraded to 0.94.4 and now getting Unavailable constantly. I am running 3.3.9_001768 as well but didnt have any issues until updating HA

ltoolio · June 25, 2019, 9:05pm

I’m getting that, too. However, all my automations via NodeRed all continue to work as expected.

Corky876 · June 26, 2019, 3:54am

So for some reason my token changed. Not sure why that happened, but back to working now that I corrected config to new token.

DonNL · June 26, 2019, 4:43am

Nope… Still nothing… Will try again today…

DonNL · June 27, 2019, 7:15pm

Got it to work. I’m still not sure what was wrong in my settings, but when I reset my Pi’s connection and requested a new ip from the router (switching dhcp server shortly) it worked.
Just modified the connection in ssh to make it static and it works again. So it had something to do with the connection setup on the Pi…

mr-varga · January 15, 2021, 4:41pm

Same problem, unaviable… New for solve it?

2021-01-15 19:16:20 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:16:40 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:17:00 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:17:20 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:17:40 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:18:00 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:18:20 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:18:40 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:19:00 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:19:20 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:19:40 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:20:00 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:20:20 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:20:40 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:21:00 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:21:20 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:21:40 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:22:00 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:22:20 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:22:40 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:23:00 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:23:20 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:23:40 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:24:00 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:24:20 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:24:40 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

2021-01-15 19:25:00 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds

mr-varga · January 21, 2021, 9:27am

I find the solution… I have two device with the same IP.

a.setzer · January 27, 2021, 8:22pm

Hey,

The Xiaomi Integration for my Vac Mop Pro is unavailable, at the moment!
Do you know any issue/changes side of Xiaomi?

I took the token with the Windows token_extractor.exe and yes, i’ve definitly the right local IP adress

grafik

kriss13 · March 20, 2021, 6:56am

I have exactly the same problem.

homelord · June 2, 2021, 1:32am

Ditto on the same problem. Was working now shows as unavailable.

homelord · June 2, 2021, 7:49pm

I solved this for myself.

My IP address changed and even though I changed it in the config, it was still showing as unavailable. To resolve this, I deleted the current integration under config/integrations, and rebooted. Fixed.

Proche72 · August 30, 2021, 7:15pm

Hey, my roborock is changing IP quite often (after reboot and also when there is wifi problem) and I have to change in HA and do a lot of things (such as deleteing the integration as mentioned in #16) any way how to set up roborock to use static IP to avoid this?

sedin · November 22, 2021, 10:23pm

A bit late but login to your router and set it’s DHCP-server to bind the Roborock MAC-address to a fixed IP-address that is outside of the dynamic assigned IP-range

Proche72 · November 23, 2021, 5:19am

Thanks man, I did that few weeks back and it works perfectly since then👍