xiaomi vaccum cleaner not responding

[btrial]

Hi,

I am using your mirobo library to start and stop my xiaomi mija vacuum cleaner. It works great, except the case when the vacuum is not being called for longer period of time (day/two).

Then when I try to start the cleaner using your library I get following errors.
If I try about 3 times in a row, it start to work again, and works fine.
It looks like the vacuum goes to sleep maybe ?

Executing command: sudo mirobo --ip 192.168.1.25 --token 33795a47547535596d6a526e3563434c start
Response from command execution: 1
ERROR:mirobo.device:Unable to discover a device at address 192.168.1.25
Traceback (most recent call last):
File "/usr/local/bin/mirobo", line 11, in
sys.exit(cli())
File "/usr/lib/python3/dist-packages/click/core.py", line 716, in call
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 696, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1060, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 889, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 534, in invoke
return callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in new_func
return ctx.invoke(f, obj, *args[1:], **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 534, in invoke
return callback(*args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/mirobo/vacuum_cli.py", line 152, in start
click.echo("Starting cleaning: %s" % vac.start())
File "/usr/local/lib/python3.5/dist-packages/mirobo/vacuum.py", line 27, in start
return self.send("app_start")
File "/usr/local/lib/python3.5/dist-packages/mirobo/device.py", line 121, in send
self.do_discover()
File "/usr/local/lib/python3.5/dist-packages/mirobo/device.py", line 73, in do_discover
raise DeviceException("Unable to discover the device %s" % self.ip)
mirobo.device.DeviceException: Unable to discover the device 192.168.1.25

[rytilahti]

Unfortunately I have no solution for this problem, but let's keep it open for now.

[MaxRei-dev]

same here:

`DEBUG:miio.protocol:Unable to decrypt, returning raw bytes.
DEBUG:miio.device:Got a response: Container:
data = Container:
data = (total 0)
length = 0
value = (total 0)
offset2 = 32
offset1 = 32
header = Container:
data = !1\x00 \x00\x00\x00\x00\x03L\xf1+Y\xef(\xdf (total 16)
length = 16
value = Container:
length = 32
unknown = 0
devtype = 844
serial = 61739
ts = 2017-10-24 11:49:51
offset2 = 16
offset1 = 0
checksum = \xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff (total 16)
DEBUG:miio.device:Discovered 844 61739 with ts: 2017-10-24 11:49:51, token: b'ffffffffffffffffffffffffffffffff'
DEBUG:miio.device:192.168.1.112:54321 >>: {'method': 'get_status', 'id': 9461}
ERROR:miio.device:Got error when receiving: timed out
WARNING:miio.device:Retrying with incremented id, retries left: 3
ERROR:miio.device:Unable to discover a device at address 192.168.1.112
Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/miio/device.py", line 200, in send
data, addr = s.recvfrom(1024)
socket.timeout: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/bin/mirobo", line 11, in
sys.exit(cli())
File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 722, in call
return self.main(*args, **kwargs)
File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 697, in main
rv = self.invoke(ctx)
File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 1043, in invoke
return Command.invoke(self, ctx)
File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 895, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 535, in invoke
return callback(*args, **kwargs)
File "/usr/local/lib/python3.4/dist-packages/click/decorators.py", line 17, in new_func
return f(get_current_context(), *args, **kwargs)
File "/usr/local/lib/python3.4/dist-packages/miio/vacuum_cli.py", line 86, in cli
ctx.invoke(status)
File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 535, in invoke
return callback(*args, **kwargs)
File "/usr/local/lib/python3.4/dist-packages/click/decorators.py", line 64, in new_func
return ctx.invoke(f, obj, *args[1:], **kwargs)
File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 535, in invoke
return callback(*args, **kwargs)
File "/usr/local/lib/python3.4/dist-packages/miio/vacuum_cli.py", line 116, in status
res = vac.status()
File "/usr/local/lib/python3.4/dist-packages/miio/vacuum.py", line 97, in status
return VacuumStatus(self.send("get_status")[0])
File "/usr/local/lib/python3.4/dist-packages/miio/device.py", line 222, in send
return self.send(command, parameters, retry_count - 1)
File "/usr/local/lib/python3.4/dist-packages/miio/device.py", line 165, in send
self.do_discover()
File "/usr/local/lib/python3.4/dist-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.112`

[rytilahti]

Is this with 0.3.0 or with an earlier release? If with an earlier one, could you try and update (we have changed the handshake only to send a single discovery packet, as sending multiple caused some sort of flood protection on some devices)?

[btrial]

Will check later today when come back home. Can you please remind me how can i check the version ? mirobo --help or mirobo --version ?

[MaxRei-dev]

mirobo --version to check version. but i'am on 0.3.0 and have a similar error.

[btrial]

I have version 0.2.0, so updated just right now to version 0.3.0, and tried it out.
Same error on first try. On second it went fine.

[bachya]

Same here. Using mirobo version 0.3.1. I reset my vacuum, did the discovery:

$ mirobo discover --handshake 1

...and got back a good token:

INFO:miio.device:Sending discovery to <broadcast> with timeout of 5s..
INFO:miio.device:  IP 192.168.8.1: 986 - token: b'xxxxxxxxxxxxxxxxxxxxxxxxxxxx'
INFO:miio.device:Discovery done

However, when I try to use this token (with the correct IP):

mirobo --ip 192.168.1.130 --token b'xxxxxxxxxxxxxxxxxxxxxxxxxxxx

...I get the same stack trace:

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.130

Incidentally, sometimes, I'll get this response instead:

ERROR:miio.vacuum_cli:Unable to read the stored msgid: [Errno 2] No such file or directory: '/tmp/python-mirobo.seq'
ERROR:miio.device:Got error when receiving: timed out
WARNING:miio.device:Retrying with incremented id, retries left: 3
ERROR:miio.device:Got error when receiving: timed out
WARNING:miio.device:Retrying with incremented id, retries left: 2
ERROR:miio.device:Got error when receiving: timed out
WARNING:miio.device:Retrying with incremented id, retries left: 1
ERROR:miio.device:Got error when receiving: timed out
Traceback (most recent call last):
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/device.py", line 200, in send
    data, addr = s.recvfrom(1024)
socket.timeout: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/device.py", line 200, in send
    data, addr = s.recvfrom(1024)
socket.timeout: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/device.py", line 200, in send
    data, addr = s.recvfrom(1024)
socket.timeout: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/device.py", line 200, in send
    data, addr = s.recvfrom(1024)
socket.timeout: timed out

The above exception was the direct cause of the following exception:

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 222, in send
    return self.send(command, parameters, retry_count - 1)
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/device.py", line 222, in send
    return self.send(command, parameters, retry_count - 1)
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/device.py", line 222, in send
    return self.send(command, parameters, retry_count - 1)
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/device.py", line 223, in send
    raise DeviceException from ex
miio.device.DeviceException

[bachya]

Just tried running the same command in debug mode and got this:

INFO:miio.vacuum_cli:Debug mode active
ERROR:miio.vacuum_cli:Unable to read the stored msgid: [Errno 2] No such file or directory: '/tmp/python-mirobo.seq'
DEBUG:miio.vacuum_cli:Connecting to 192.168.1.130 with token 5a653170446642364f4c6d37384d7761
DEBUG:miio.protocol:Unable to decrypt, returning raw bytes.
DEBUG:miio.device:Got a response: Container:
    data = Container:
        data =  (total 0)
        value =  (total 0)
        offset1 = 32
        offset2 = 32
        length = 0
    header = Container:
        data = !1\x00 \x00\x00\x00\x00\x03\xda\xbe\xa4Y\xffTO (total 16)
        value = Container:
            length = 32
            unknown = 0
            devtype = 986
            serial = 48804
            ts = 2017-11-05 18:11:27
        offset1 = 0
        offset2 = 16
        length = 16
    checksum = \xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff (total 16)
DEBUG:miio.device:Discovered 986 48804 with ts: 2017-11-05 18:11:27, token: b'ffffffffffffffffffffffffffffffff'
DEBUG:miio.device:192.168.1.130:54321 >>: {'id': 1, 'method': 'miIO.info', 'params': []}
ERROR:miio.device:Got error when receiving: timed out

The DEBUG:miio.protocol:Unable to decrypt, returning raw bytes. line is interesting; is this supposed to happen, or does this mean my token is somehow incorrect?

[bachya]

Sounds like these folks are having a similar issue: aholstenson/miio#59

[bachya]

Got my case figured it. At some point, it looks like the token changed on me; rediscovered it from an iOS backup and everything started working.

[MatsKarlsson]

@bachya Had the same problems:
disconnected from wifi, extracted token, connected vacuum to wifi. Then when trying to use mirobo with latest token it failed like for you: 'no such file or directory ...' and 3 retries.

Then extracted token from android-apk/sqlite-db, it was a different token, so tried that with mirobo and it worked immediately.

[sumnerboy12]

I just upgraded to v0.3.1 and am still seeing intermittent connection problems (I wonder if the robot is shutting down wifi periodically?).

Not sure if what I am seeing is exactly the same as the OP, but it definitely works some of the time, and fails to connect other times.

When a status request fails I am seeing this;

iot@iot01:~$ mirobo --ip 192.168.40.40 --token XXXXX -d
INFO:miio.vacuum_cli:Debug mode active
DEBUG:miio.vacuum_cli:Read stored sequence ids: {'manual_seq': 0, 'seq': 345}
DEBUG:miio.vacuum_cli:Connecting to 192.168.40.40 with token XXXXX
ERROR:miio.device:Unable to discover a device at address 192.168.40.40
Traceback (most recent call last):
  File "/usr/local/bin/mirobo", line 11, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 1043, in invoke
    return Command.invoke(self, ctx)
  File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/miio/vacuum_cli.py", line 86, in cli
    ctx.invoke(status)
  File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/click/decorators.py", line 64, in new_func
    return ctx.invoke(f, obj, *args[1:], **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/miio/vacuum_cli.py", line 116, in status
    res = vac.status()
  File "/usr/local/lib/python3.4/dist-packages/miio/vacuum.py", line 99, in status
    return VacuumStatus(self.send("get_status")[0])
  File "/usr/local/lib/python3.4/dist-packages/miio/device.py", line 165, in send
    self.do_discover()
  File "/usr/local/lib/python3.4/dist-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.40.40

It will fail like this for 5-10 times and then all of a sudden work;

iot@iot01:~$ mirobo --ip 192.168.40.40 --token XXXXX -d
INFO:miio.vacuum_cli:Debug mode active
DEBUG:miio.vacuum_cli:Read stored sequence ids: {'manual_seq': 0, 'seq': 345}
DEBUG:miio.vacuum_cli:Connecting to 192.168.40.40 with token XXXXX
DEBUG:miio.protocol:Unable to decrypt, returning raw bytes.
DEBUG:miio.device:Got a response: Container:
    data = Container:
        value =  (total 0)
        data =  (total 0)
        offset1 = 32
        offset2 = 32
        length = 0
    header = Container:
        value = Container:
            length = 32
            unknown = 0
            devtype = 987
            serial = 40604
            ts = 1970-01-01 18:55:02
        data = !1\x00 \x00\x00\x00\x00\x03\xdb\x9e\x9c\x00\x01\n\x06 (total 16)
        offset1 = 0
        offset2 = 16
        length = 16
    checksum = \xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff (total 16)
DEBUG:miio.device:Discovered 987 40604 with ts: 1970-01-01 18:55:02, token: b'ffffffffffffffffffffffffffffffff'
DEBUG:miio.device:192.168.40.40:54321 >>: {'method': 'get_status', 'id': 346}
DEBUG:miio.device:192.168.40.40:54321 (ts: 1970-01-01 18:55:02, id: 346) << {'result': [{'in_cleaning': 0, 'clean_area': 104695000, 'dnd_enabled': 1, 'msg_ver': 5, 'msg_seq': 29, 'fan_power': 90, 'battery': 100, 'map_present': 0, 'clean_time': 6774, 'state': 8, 'error_code': 0}], 'id': 346}
State: Charging
Battery: 100 %
Fanspeed: 90 %
Cleaning since: 1:52:54
Cleaned area: 104.695 m²
DEBUG:miio.vacuum_cli:Writing {'manual_seq': 0, 'seq': 346} to /tmp/python-mirobo.seq

[rytilahti]

@sumnerboy12 How often are you requesting information from the vacuum? Maybe it has some sort of protection mechanism when too many requests are made consecutively? :-)

@MatsKarlsson that's a good catch, that the token extracted from the device will not work (anymore, if it ever did with newer FWs) at all!

[sumnerboy12]

I did wonder that, but I have found that making a request after > 24hrs still results in this error (sometimes). When it starts working I can fire off requests quite rapidly (1 per sec) and they all come back. Then after a while it seizes up and remains that way for a number of minutes.