Add support for Vacuum 1C STYTJ01ZHM

[craiq]

WARNING:miio.discovery:Found unsupported device dreame-vacuum-mc1808_miio29430xxxx._miio._udp.local. at 192.168.0.172, please report to developers

would love to get support :)

[rytilahti]

Could you try if some of the commands of mirobo (or miiocli vacuum) or miiocli viomivacuum work on that device?

[craiq]

just found the miot-spec files

released:
http://miot-spec.org/miot-spec-v2/instance?type=urn:miot-spec-v2:device:vacuum:0000A006:dreame-mc1808:1

debug:
http://miot-spec.org/miot-spec-v2/instance?type=urn:miot-spec-v2:device:vacuum:0000A006:dreame-mc1808:2

Could you try if some of the commands of mirobo (or miiocli vacuum) or miiocli viomivacuum work on that device?

ERROR:miio.miioprotocol:Got error when receiving: timed out
Error: No response from the device

[rytilahti]

if you are not afraid of testing a PR, you could check out #672 to see what miiocli miotdevice --ip <ip> --token <token> miot_info returns to you. I'll create a WIP PR to add support for this vacuum based on that PR.

[craiq]

Thanks for your effort!

Running command miot_info ERROR:miio.miioprotocol:Got error when receiving: timed out Error: No response from the device

What I did:

• clone repo, fetch pr in branch, checkout branch
• pipenv install requests, pipenv shell, python setup.py install, your command
• got token via App downgrade - afraid that the app update created a new token

Somewhere I read yesterday some more commands to setup, but can't finde them anymore

Edit: wrong token provide same result

[rytilahti]

If you reseted the device, the token will change which will lead to timeouts. Is info command working just fine even when miot_info is failing? If so, then the token is definitely correct.

The setup commands you used should be fine, I don't personally use pipenv, but python setup.py install should do the same as pip install ., and if miot_info would not be there (i.e., you wouldn't have that PR), you would be receiving an error about unknown command.

[craiq]

changed setup now. Running directly from pc not over raspberrypi anymore.
Did reset the vacuum, get token via discover handshake and set wlan via mirobo successfully.
still timeout with miot_info and info

[rytilahti]

Info should be working if the token is correct, the token via discover handshake hasn't worked since end of 2017 or so (if you paired it with the mobile app). When the device gets provisioned (either by the app or configure_wifi), it will generate a new token.

[craiq]

miiocli device ... info && miiocli miotdevice ... info
Model: dreame.vacuum.mc1808
Hardware version: Linux
Firmware version: 3.5.8_1045
Network: {'localIp': '192.168.0.172', 'mask': '255.255.255.0', 'gw': '192.168.0.1'}
AP: {'ssid': '', 'bssid': '2C:51:2F:92:A5:0B', 'rssi': -33}

miiocli miotdevice ... miot_info
Running command miot_info
ERROR:miio.miioprotocol:Got error when receiving: timed out
Error: No response from the device

[craiq]

if i can help you with any raw commands, let me know

[rytilahti]

So, you could try this out to see if that is a miot device which simply ignores the miot_info:

miiocli -d miotdevice --ip <xx> --token <xx> raw_command get_prop "[{'did': 'state', 'siid': 3, 'piid': 2 }]"

If it responds back with, it's a miot device and adding some basic support should be straight forward. If that is not working, maybe it is using the miio protocol, but neither miiocli viomivacuum nor mirobo was working for it?

Here's how the interpret the return value (siid/piid description) of that call:

INFO:__main__:Service: siid 3: (Robot Cleaner): 2 props, 2 actions
* Property piid: 2 (Status): (int8, unit: None) (acc: ['read', 'notify'], value-list: [{'value': 1, 'description': 'Sweeping'}, {'value': 2, 'description': 'Idle'}, {'value': 3, 'description': 'Paused'}, {'value': 4, 'description': 'Error'}, {'value': 5, 'description': 'Go Charging'}, {'value': 6, 'description': 'Charging'}], value-range: None)

[craiq]

sadly all of the commands time out: Error: No response from the device
Despite ... info is working for all of them

[rytilahti]

Okay, then it's likely a miio device, but we need to figure out what commands it accepts. One way to do that would be to capture the traffic between your phone and the device as described here: https://github.com/aholstenson/miio/blob/master/docs/protocol.md. Another potential way involves obtaining the app plugin (from a backup, for example) and reverse engineering it for the expected commands.

[craiq]

I could not capture commands from my phone. looks like it pings the vacuum with 21310020ffffffffffffffffffffffffffffffffffffffffffffffffffffffff and then the commands are not visible to wireshark anymore. Capturing the info command from pc and decrypt it worked fine.
filter was set to just ignore mac addresses of other devices.

unplug the router from the internet:
can control the vacuum until restart of the app. then the app wont find the vacuum anymore...

regularly the vacuum calls out:

Frame 44: 285 bytes on wire (2280 bits), 285 bytes captured (2280 bits) on interface \Device\NPF_{1A8EAB37-2AE2-4DCB-A1AB-DA14AE08AA91}, id 0
Ethernet II, Src: BeijingX_ec:0f:0e (44:23:7c:ec:00:0), Dst: IPv4mcast_fb (01:00:5e:00:00:fb)
    Destination: IPv4mcast_fb (01:00:5e:00:00:fb)
    Source: BeijingX_ec:0f:0e (44:23:7c:ec:00:00)
    Type: IPv4 (0x0800)
Internet Protocol Version 4, Src: 192.168.0.172, Dst: 224.0.0.251
User Datagram Protocol, Src Port: 5353, Dst Port: 5353
    Source Port: 5353
    Destination Port: 5353
    Length: 251
    Checksum: 0x432c [unverified]
    [Checksum Status: Unverified]
    [Stream index: 7]
    [Timestamps]
Multicast Domain Name System (response)
    Transaction ID: 0x8a08
    Flags: 0x8400 Standard query response, No error
    Questions: 0
    Answer RRs: 1
    Authority RRs: 0
    Additional RRs: 6
    Answers
        _services._dns-sd._udp.local: type PTR, class IN, _miio._udp.local
    Additional records
        _miio._udp.local: type PTR, class IN, dreame-vacuum-mc1808_miio294305000._miio._udp.local
        dreame-vacuum-mc1808_miio294305000._miio._udp.local: type TXT, class IN, cache flush
        dreame-vacuum-mc1808_miio294305000._miio._udp.local: type SRV, class IN, cache flush, priority 0, weight 0, port 54321, target dreame-vacuum-mc1808_miio294305000
        dreame-vacuum-mc1808_miio294305000: type A, class IN, cache flush, addr 192.168.0.172
        dreame-vacuum-mc1808_miio294305000: type A, class IN, cache flush, addr 192.168.0.172
        dreame-vacuum-mc1808_miio294305000: type NSEC, class IN, cache flush, next domain name dreame-vacuum-mc1808_miio294305000
    [Unsolicited: True]

[rytilahti]

That 21310020ffff... is the handshake and those mDNS advertisements are just to let the network know that the device is there.