kovapatrik / homebridge-midea-platform

Homebridge plugin for Midea devices
https://www.npmjs.com/package/homebridge-midea-platform
Apache License 2.0
21 stars 2 forks source link

Separate the humidity sensor from dehumidifier so I can use it as its own sensor when creating automations. Similar to how the temp sensor is #88

Open nbraunstein opened 1 week ago

nbraunstein commented 1 week ago

Is your feature request related to a problem? Please describe:

Describe alternatives you've considered:

Additional context:

nbraunstein commented 1 week ago

image

I'd like to have a separate sensor for humidity so I can use my dehumidifier's sensor to create automations. Like this temp sensor that is built into my dehumidifier.

dkerr64 commented 1 week ago

This is interesting... HomeKit dehumidifier has current humidity as a characteristic, but the Apple Home app cannot use that as a sensor from which to create an automation... it can only use the on/off state of the dehumidifier.

I think it would be easy to add a separate service for humidity sensor. I would not separate it, but rather I would leave the current humidity characteristic as it is, but then create a humidity sensor in addition based on a config setting, just like the temperature sensor is created.

kovapatrik commented 1 week ago

I've had issues like this before with other services (like an air purifier filter usage level couldn't be used in automation and such...), so it looks like this is common with accessories in the Home app.

kovapatrik commented 1 week ago

I've published v1.1.0-beta.2 which contains the ability to toggle the humiditySensor config in the plugin configurations which should create the separated humidity sensor. Could you please try it out?

mrbritten commented 1 week ago

Not my request, but I can say it seems to be working great, I can use humidity level to trigger automations now.

kovapatrik commented 1 week ago

Thanks for the feedback!

nbraunstein commented 1 day ago

Thank you!! Works perfectly

kovapatrik commented 15 hours ago

Great to hear it! I will close this issue as soon as I release v1.1.0.