Xiaomi Vacuum no longer works in 0.57 #10343
Comments
|
I can not replicate this problem.. Are you able to discover it using https://github.com/rytilahti/python-miio ? |
|
@olskar Unfortunately, no. The device is definitely connected to the LAN:
...but when I run this command: $ mirobo --ip 192.168.1.130 --token xxxxxxxxxxxxxxxxxxxxxxxxxxxx...I get this output: ERROR:miio.vacuum_cli:Unable to read the stored msgid: [Errno 2] No such file or directory: '/tmp/python-mirobo.seq'
ERROR:miio.device:Unable to discover a device at address 192.168.1.130
Traceback (most recent call last):
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/bin/mirobo", line 11, in <module>
sys.exit(cli())
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/core.py", line 722, in __call__
return self.main(*args, **kwargs)
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/core.py", line 697, in main
rv = self.invoke(ctx)
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/core.py", line 1043, in invoke
return Command.invoke(self, ctx)
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/core.py", line 895, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/core.py", line 535, in invoke
return callback(*args, **kwargs)
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/decorators.py", line 17, in new_func
return f(get_current_context(), *args, **kwargs)
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/vacuum_cli.py", line 86, in cli
ctx.invoke(status)
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/core.py", line 535, in invoke
return callback(*args, **kwargs)
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/decorators.py", line 64, in new_func
return ctx.invoke(f, obj, *args[1:], **kwargs)
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/core.py", line 535, in invoke
return callback(*args, **kwargs)
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/vacuum_cli.py", line 116, in status
res = vac.status()
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/vacuum.py", line 99, in status
return VacuumStatus(self.send("get_status")[0])
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/device.py", line 165, in send
self.do_discover()
File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/device.py", line 118, in do_discover
raise DeviceException("Unable to discover the device %s" % self.ip)
miio.device.DeviceException: Unable to discover the device 192.168.1.130I've hard reset the device, but that didn't seem to change anything. |
|
Which FW version is running on the vacuum? |
|
EDIT: 3.3.9.003077 |
|
im on 3.3.9.003077, not sure if you are on higher version or its a typo (assuming the latter). |
|
Seems to be a bug in mirobo, not home assistant |
|
@ferdydek I had several sensors pulling data from the vacuum; currently, no values appear:
|
|
Got it figured it. At some point, it looks like the token changed on me; rediscovered it (using the instructions on the website) and everything started working again. Going to close. |
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (
hass --version):0.57.0
Python release (
python3 --version):3.6.1
Component/platform:
vacuum/xiaomi_miioDescription of problem:
With the upgrade to 0.57 (from 0.56.2), my vacuum's status is
unavailable. I cannot control the vacuum at all, nor can I see any data coming into it. I can confirm that it is connected to my LAN (given that I can still connect through the MiHome app). I can also confirm that my token is the same as always.Expected:
The opposite.
Problem-relevant
configuration.yamlentries and steps to reproduce:Traceback (if applicable):
The logs are filled with these messages:
Additional info:
This may be related to #10210; however, unlike that ticket, in this case, I cannot control my vacuum from HASS whatsoever.
CC: @rytilahti, @syssi
The text was updated successfully, but these errors were encountered: