Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't connect to vacuum anymore #667

Closed
SebRut opened this issue Apr 13, 2020 · 2 comments
Closed

Can't connect to vacuum anymore #667

SebRut opened this issue Apr 13, 2020 · 2 comments
Labels

Comments

@SebRut
Copy link

SebRut commented Apr 13, 2020

Since 2-3 weeks I'm not able to connect to the vacuum anymore, neither by using homeassistant or python-miio manually from different devices. I am able to ping the device and control it using the MiHome app but local request fail with the following.

Got exception while fetching the state: No response from the device
Got exception while fetching the state: Unable to discover the device 192.168.0.183

Running mirobo --ip 192.168.0.183 --token [TOKEN] -dd info lead to the following log:

INFO:miio.vacuum_cli:Debug mode active
DEBUG:miio.vacuum_cli:Connecting to 192.168.0.183 with token [TOKEN]
DEBUG:miio.protocol:Unable to decrypt, returning raw bytes: b''
DEBUG:miio.miioprotocol:Got a response: Container:
    data = Container:
        data = b'' (total 0)
        value = b'' (total 0)
        offset1 = 32
        offset2 = 32
        length = 0
    header = Container:
        data = b'!1\x00 \x00\x00\x00\x00\x03\xda<\xfa^\x94\x13\x1c' (total 16)
        value = Container:
            length = 32
            unknown = 0
            device_id = unhexlify('03da3cfa')
            ts = 2020-04-13 07:22:04
        offset1 = 0
        offset2 = 16
        length = 16
    checksum = b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff' (total 16)
DEBUG:miio.miioprotocol:Container:
    data = Container:
        data = b'' (total 0)
        value = b'' (total 0)
        offset1 = 32
        offset2 = 32
        length = 0
    header = Container:
        data = b'!1\x00 \x00\x00\x00\x00\x03\xda<\xfa^\x94\x13\x1c' (total 16)
        value = Container:
            length = 32
            unknown = 0
            device_id = unhexlify('03da3cfa')
            ts = 2020-04-13 07:22:04
        offset1 = 0
        offset2 = 16
        length = 16
    checksum = b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff' (total 16)
DEBUG:miio.miioprotocol:Discovered 03da3cfa with ts: 2020-04-13 07:22:04, token: b'ffffffffffffffffffffffffffffffff'
DEBUG:miio.miioprotocol:192.168.0.183:54321 >>: {'id': 1, 'method': 'miIO.info', 'params': []}
DEBUG:miio.miioprotocol:send (timeout 5): Container:
    data = Container:
        data = b'\xcb\xd6yg\xbc\x08\xb2\xbdQA\x07\xd3\x141\x1a\xbc'... (truncated, total 48)
        value = {'id': 1, 'method': 'miIO.info', 'params': []}
        offset1 = 32
        offset2 = 80
        length = 48
    header = Container:
        data = b'!1\x00P\x00\x00\x00\x00\x03\xda<\xfa^\x94\x13\x1d' (total 16)
        value = Container:
            length = 80
            unknown = 0
            device_id = unhexlify('03da3cfa')
            ts = 2020-04-13 07:22:05
        offset1 = 0
        offset2 = 16
        length = 16
    checksum = b'P\x15CQbI\xd0I\xea/\xa8\xc6.\xe7\xbf1' (total 16)
DEBUG:miio.miioprotocol:Retrying with incremented id, retries left: 3
@rytilahti
Copy link
Owner

When the discovery is still working, the timeouts are commonly caused by incorrect token. Could it be that the vacuum has reseted itself and by doing so, changed the token?

@SebRut
Copy link
Author

SebRut commented Apr 18, 2020

That's it! Thank you.

@SebRut SebRut closed this as completed Apr 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants