miio local api soon deprecated? / add support for miot api

[rezmus]

just to let you know. this is part of mail sent to xiaomi iot platform devs today (translated):

The Xiaomi IoT platform is fully implementing the MioT-Spec access work. The Xiaomi IoT Device Protocol Specification (MIoT Specification) will replace the original miio profile protocol specification.

i've checked some plugins of new devices and many of them use miot api (cloud only) rather than miio. for example air purifier 3. i can't say for sure because i don't have device, but from what i saw it's stripped from local miio api.

[syssi]

Wow. Terrible news.

[vampywiz17]

it possible to use miot api on external software, like domoticz or Home Assistant? i know it is cloud based, but possible to make api call across the cloud?

Like this not help? Or it only work with Yeelight lamp?

https://github.com/Yeelight/miot-api

https://github.com/Yeelight/miot-api/tree/master/manual

[Leatherface75]

If that's true then i have bought my last Xiaomi product.

[roth-m]

It's true. I have an Air Purifier 3.
It returns {"id":216,"error":{"code":-5001,"message":"command error"}} for any command excepted {"id":214,"method":"miIO.info","params":[]}.

If someone knows how to get a console (or something like this) on this "thing", it would be great! (ESP32 inside!)

[rezmus]

can you check
"method":"get_properties","params":["prop.3.6"]
or
"method":"get_properties","params":[{"siid":3,"piid":6}]

[roth-m]

Sent: {"id": 2, "method": "get_properties", "params": ["prop.3.6"]}
Recv: {"id":2,"error":{"code":-9999,"message":"user ack timeout"}}

Sent: {"id": 1, "method": "get_properties", "params": [{"siid": 3, "piid": 6}]}
Recv: {"id":1,"error":{"code":-9999,"message":"user ack timeout"}}

[Leatherface75]

Xiaomi Fan seems to work atleast so far.

[rezmus]

"method":"set_properties","params":[{"piid":2,"siid":2,"value":true}]

[roth-m]

{'code': -9999, 'message': 'user ack timeout'}

[rezmus]

strange, this is exact command sent to device from automation to power on purifier.

{"sa_id":2866,"model":"zhimi.airpurifier.ma4","name":"Turn on","keyName":"Turn on","type":0,"groupInfo":[],"tr_id":201,"payload":{"did":"","command":"zhimi.airpurifier.ma4.set_properties","value":[{"siid":2,"piid":2,"value":true}]}}

i even put such automation (manual trigger) on device where i can log device <> cloud traffic and got this from miio.log

{"from":"6,X,Y,.click","id":Z,"method":"set_properties","params":[{"piid":2,"siid":2,"value":true}]}

[roth-m]

Got it working with the DID!

"method":"set_properties","params":[{"did":"MYDID","siid":2,"piid":2,"value":true}]
Turns the beast ON

"method":"set_properties","params":[{"did":"MYDID","siid":2,"piid":2,"value":true}]
Turns the beast OFF

"method":"get_properties","params":[{"did":"MYDID","siid": 3, "piid": 6}]
Returns:
"did": "MYDID",
"siid": 3,
"piid": 6,
"code": 0,
"value": 1
}

How do you get the mapping (siid,piid) <-> function / property ?

[rezmus]

i found out that they use did with siid/piid from some RN plugin and sent you some json for test to your github mail yesterday. did you get it? anyway i'm glad it works, because it proves devices that deploy new miot-spec scheme can still be used with local api :)

do you have chinese version (ma4)? here is full json spec for it https://ufile.io/53ribhi8

[roth-m]

I got it (but prefer to write as much information in public ;) )
I have the chinese version (ma4). I bought it on BG and bet it would work the same as the previous versions (I did not see your message here otherwise I would have not ordered). I lost my bet.
You make me win it with the spec file! :)
Thanks a lot!

[rezmus]

so it looks like miot-spec is based on 3 method "get_properties", "set_properties" and "action" invoked with params according to device specs. can you check last method (action)?

1st get some info about filter usage with get_properties siid:4/piid:3 (filter life) and siid:4/piid:5 (filter usage time). next send (with aiid, not piid)

"method":"action","params":[{"did":"MYDID","siid":4,"aiid":1}]

if executed correctly it should reset your filter life. hope it won't be big issue because you don't have it to long ;) resend get_properties to confirm.

[roth-m]

It does nothing. No reply and no change on filter-life-level.

I tried with {"did":"MYDID","siid":4,"aiid":1, "in": [ true ]}] also, without luck.