Feature request: Ability to control generic_hygrostat

[ndrwrbgs]

Much of the HASS UI links or shares components for (de)humidifiers and thermostats. Can we control a generic_hygrostat (humidifier.*) entity with this plugin easily?

What are you trying to do

I'm actually trying to play with configuring my tropical plant chamber based on absolute humidity/vapor pressure rather than relative humidity; so this wouldn't be "the right way" (which would be "if you want to do that, do that") anyway. But configuring rH based on time was a quick work around I could do in a few minutes.

However, automations with time triggers just aren't as friendly as the UI here!

So I open the discussion so there's a place for folks to +1 if they want it, but would not ask for doing anything with it right now.

[kneave]

As luck would have it I have a manual dehumidifier in my workshop along with external temperature/humidity sensor. I'm guessing in this case you'd need humidity as the Y axis rather than temperature?

[ndrwrbgs]

Yeah, in my imagination it’d be a direct replacement for temperature.

If it could control an arbitrary input number then it wouldn’t need separate paths for temperature vs relative humidity (vs vapor pressure).

“workshop” 🤩

[kneave]

Workshop in this case is a cargo container that isn't properly insulated, without the dehumidifier everything goes moldy over winter :S

Someone else has asked for a way to control things without a temperature, I'll have a think to see how I might integrate humidity that way, or like you say a generic input number. I'm just not quite sure how to integrate something like that but I'll figure it out.

[kneave]

I've added the ability to create a schedule without an entity associated with it, you can still set the temperature using the graph or set the "no change" option. You have three freeform numeric fields to play with, events will be fired with the name 'climate_scheduler_node_activated`.

You can set whatever numeric values you want to A, B, or C and you should be able to create an automation based on those numbers.

https://github.com/kneave/climate-scheduler/releases/tag/v1.14.0.1b

[kneave]

FYI @ndrwrbgs, I think I accidentally included full support for humidifiers in 1.15... I asked Copilot to implement all variations of the various supported features the Climate entity can include and it included humidifiers. I don't have one to test against so this may be over to you to have a look at. I hadn't realised it'd done it until I was fixing something with the step values and it asked if I wanted to apply them to humidity levels too. 😅