core: Xiaomi vacuum: errors in log but device working properly

Home Assistant release with the issue: 0.89.1 Last working Home Assistant release (if known): n/a Operating environment (Hass.io/Docker/Windows/etc.): Debian / venv Component/platform: vacuum/vacuum.xiaomi_miio

Description of problem: In log there are errors showing up every 15 minutes. Device is despite that working 101% perfect, no connectivity issues (vacuum is less than one meter away from AP) and no unavailability in HA

Problem-relevant configuration.yaml entries and (fill out even if it seems unimortant):

vacuum:
  - platform: xiaomi_miio
    host: !secret xiaomi_vacuum_host [ip]
    token: !secret xiaomi_vacuum_token [token]
    name: 'Mi Robot'

Traceback (if applicable):

Update of vacuum.mi_robot is taking over 10 seconds
Unable to discover a device at address 192.168.x.x
Got exception while fetching the state: Unable to discover the device 192.168.x.x

Additional information: no internet is blocked, vacuum is seen properly in HA and app

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 53 (24 by maintainers)

Commits related to this issue

xiaomi_miio/vacuum: log exception warnings/errors only when the device was previously available * The vacuum will now also be correctly marked as unavailable when the update fails * Related to #21899 — committed to rytilahti/home-assistant by rytilahti 4 years ago

Most upvoted comments

same issue i think that solution shoul look like this ( like icinga or other monitoring)

  - platform: xiaomi_miio
    host: xxx:xxx:xxx:xxx
    token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    name: something
    max_check_attempts: 3
    retry_interval: 1m

if message appears, it doesnt go to log untill the some number of checks from max_check_attempts was done, and between check was time from retry_interval

fufar on May 27, 2020

I have just updated 0.103 to 0.105.3 and still the same. It’s like 70-80% of my warnings/errors 😦

ipatalas on Feb 14, 2020

Still present in 0.99.2 (not a surprise, as no commits regarding this platform). Maybe it would be possible to silent it with some switch or change log level to notice?

andriej on Sep 20, 2019

Merged, issue seems to be solved (logs only one error)

andriej on Jan 26, 2021