The four minute delay is to allow for the dehumidifier’s cooling off period after a power interruption, should the automation be triggered immediately after an hour. There’s a separate automation that turns the switch off after an hour that works without issue.
The automation as-is will go hours without triggering if left alone, even with plenty of sensor readings- the only way I’ve found that I can force it (without using the “trigger” button) is to turn the automation off and then on, and use States tool to bump up either sensor.house_average_humidity or one of the individual sensors so that the average changes.
A couple of days ago I wanted to keep the dehumidifier from turning on during sleeping hours and had a condition for time, the automation seemed to work as expected with a condition in place, but not without one. As I type I realize I could use a false condition and just a time of 00:00:00 to 23:59:59 to hopefully replicate prior performance, but I guess now I’m curious about why the automation is not working as expected.
What do you mean by “the automation isn’t working as expected”? Note that a numeric state trigger will only trigger whenever the state of the entity goes above or below the value you set. If it’s already above or below the threshold you define when you create the automation or turn it on, it won’t trigger.
Thanks for your reply! I understand that the automation cannot trigger without a change in the numeric state in the entity, but for some reason it does not work unless “forced”, please see a snippet of readings from earlier today:
At ~2:05 the switch turned off as expected as per the working “off after an hour automation”. Then the entity shows different states, all above the threshold that should trigger it, until ~3:00, when I cheated by turning it on and off and then changing the value using the States tool.
Because I’ve found that there’s diminishing returns once once the dehumidifier has been running for an hour with it’s current location and the fact that one of the rooms that’s being monitored (kids bedroom) is closed for a few hours during the day.
If left on, the device spends roughly half the time in fan only mode with very marginal improvements in overall humidity levels. My thinking is that by using an average and forcing a max hour runtime it’s making it more efficient while it’s on.
If the device was in a closed room it would certainly work as expected, but I’m trying to use an over-powered dehumidifier to address all of the air in a smaller, one-story house.
I’m open to the possibility that I’m over-thinking it and or incorrectly-thinking too!
Thank you both so much- it makes sense now that I have a better understanding of how the threshold works, I thought it should be checking to see if the value “was” above a certain number, rather than “going” above that number (at least, that’s my amateur approach to thinking about it).
I’ve changed it so the dehumidifier does it’s job as suggested, dropping the average humidity below the threshold before turning off as suggested and it’s working as expected.
Taras- the link you posted to your write up looks great for version 2.0 of my setup; now that I have it working flawlessly I can’t wait to play with (break) it some more.