Xiaomi Vacuum error/warning in logs

Configuration
1

Xiaomi vacuum component is using the latest configuration syntax in my config and everything works But I am getting these… Anyone else get this or know why?

2017-10-15 22:02:48 ERROR (SyncWorker_14) [mirobo.device] Unable to discover a device at address 192.168.0.102
2017-10-15 22:02:48 WARNING (MainThread) [homeassistant.components.vacuum.xiaomi_miio] Got exception while fetching the state: Unable to discover the device 192.168.0.102
2017-10-15 22:15:24 ERROR (SyncWorker_3) [mirobo.device] Got error when receiving: timed out
2017-10-15 22:15:24 WARNING (SyncWorker_3) [mirobo.device] Retrying with incremented id, retries left: 3
2017-10-15 22:17:51 ERROR (SyncWorker_8) [mirobo.device] Unable to discover a device at address 192.168.0.102
2017-10-15 22:17:51 WARNING (MainThread) [homeassistant.components.vacuum.xiaomi_miio] Got exception while fetching the state: Unable to discover the device 192.168.0.102
2017-10-15 23:26:05 ERROR (SyncWorker_11) [mirobo.device] Unable to discover a device at address 192.168.0.102
2017-10-15 23:26:05 WARNING (MainThread) [homeassistant.components.vacuum.xiaomi_miio] Got exception while fetching the state: Unable to discover the device 192.168.0.102
2

Getting exactly the same errors.
I’ve just created and issue for this https://github.com/home-assistant/home-assistant/issues/10210

3

Same situation for me and a friend of mine with HA 0.57.3 on hass.io and on normal HA install.

4

Yeah I’m still just ignoring logs…

5

Since a few hours I get the below error messages instead. It’s filling up the logfile. I turned off the DND in the and restarted HA but nothing changed. Strange thing is that I didn’t change anything aport from installing appdeamon and pihole addon.

/usr/lib/python3.6/site-packages/homeassistant/components/vacuum/xiaomi_miio.py:203: DeprecationWarning: Call to deprecated function dnd (Use vacuum's dnd_status() instead, which is more accurate).
  STATE_ON if self.vacuum_state.dnd else STATE_OFF,

Someone having similar errors?