Alone

> This goes back to my comment on is there a way to disable miot for a mixed miio/miot device (since the spec is almost 100% broken for this device)....

The original spec will be overwritten. Thank you. I think you know me very well. 🤝

> 1. Actions. How to implement? Add support action for miio2miot in https://github.com/al-one/hass-xiaomi-miot/commit/9edc529934e3c2449fed78903c5071c2a935c0c7. But I don't have time to test it. > 2. Using pre-existing miot types Maybe in a...

> however I wonder if it's worth storing extend_miot_specs externally? That's what I was thinking too, maybe migrate them to a yaml file. ---- Call action for miio2miot was fixed...

> In miot spec, action arguments are piids for that service - how to do the same? (i.e to pass the value of a miio prop as an argument to...

Hi, `extend_miot_specs` has been migrated to a single file [`core/miot_specs_extend.json`](https://github.com/al-one/hass-xiaomi-miot/blob/master/custom_components/xiaomi_miot/core/miot_specs_extend.json).

@Wh1terat Can you create a PR for this device ?

Do you have any suggestions if implemented using `RestoreEntity` and `NumberEntity` ?

There is no `water_level` property under the `humidifier` service in [`urn:miot-spec-v2:device:humidifier:0000A00E:leshow-jsq1:1`](https://home.miot-spec.com/spec?type=urn:miot-spec-v2:device:humidifier:0000A00E:leshow-jsq1:1), only [`urn:miot-spec-v2:device:humidifier:0000A00E:leshow-jsq1:2`](https://home.miot-spec.com/spec?type=urn:miot-spec-v2:device:humidifier:0000A00E:leshow-jsq1:2) has it, but it is debug state. You need to specify it manually: ```yaml # configuration.yaml xiaomi_miot:...

Try restart HA.