@Christopher
Chris
I you want a really solid baseline you could use a number of sensors and average them out to use as the baseline sensor
(My ‘Average All’ app & driver)
I might think about building this into the app so a number of sensors could be used for the baseline
Please also include a way to have the fan on regardless of humidity for the case of someone using the toilet and just want the vent or sometime you just want air circulation.
In ST, I do this by sensing if the fan switch is turned on manually. Run fan and turn off aft x minutes with no motion. Haven't done anything with HE yet. I have the Aeon sensor and Xiaomi both in the washroom and find the Xiaomi is very slow on updating humidity.
Of course, I was trying to give an estimate of how long it takes typically. I have a 110CFM bathroom fan so it clears it pretty quick, just faster with the door open as it doesn't have to pull the dry air from under the doorway if it's open.
I'd say if it's more than 5% over base line it should be on. But that's just my preference. And your right how long it takes to get there isn't relavent. My aeotec multi sensor (USB powered) is set to report every 5 minutes or if humidity increase by 5%. It can be set much more sensitive, but I don't like to make it too chatty and potentially cause issues with the z-wave mesh performance.
Sounds good. @napalmcsr port of smart humidity sensor was my first attempt at automation of this, but I find that using the average readings over 20 minutes and not a baseline from an adjacent room causes the fan to shut off too soon after humidity starts to drop, and stay on longer than necessary if I just try to use time to clear as a reference depending on the situation.
Sure, It would work. Mark's idea is pretty close to what I do, except I just look for it to start dropping and then turn it off after X minutes. The compare to another sensor would scare me due to calibration, needing to guard band, other sensor differences, but they can be overcome.
What might work better is to record the starting humidity and wait to turn off until you get back to say X% of the total change. You'd have to record the highest humidity, etc... Something to ponder...
Screenshots are limiting my ability to show the restrictions I have in place so the the humidity present only runs if humidity isn't present and humidity off only runs when humidity is present.
@Navat604
Recording physical device events is very hit and miss - not many switches report this correctly.
We could probably look at the humidity again as a baseline and say something like;
If the humidity is the same as baseline but the switch is on then turn off after x mins.
Perhaps also with a motion sensor... off after x mins once motion stops (if humidity is the same as baseline again)
So... pseudo code again..
Apart from the humidity already defined...
If fan switch is turned on... wait configurable mins before off UNLESS...
optional Motion sensor is active... configurable delay for off once motion is inactive.
Because of the ge jasco physical turn on issue, I have a Boolean in my code track if the switch was turned on by the app, or magically shows on due to polling.
I think it would be nice to have another option to set a RH point where the fan would run for xx minutes even if the measured RH isn't higher than the threshold above baseline. I mention this only because if it's really humid outside the RH could creep up and having the fan run for xx minutes might help with potential mold issues.
Otherwise, I like what I'm seeing so far. I'll test it out and provide feedback soon.
In my case, the fan is rated at 1.5 Sone so waking me up isn't really an issue. However, I can see where that wouldn't be a desired feature for someone with a noisy fan.
Yes, in my RM rules (listed a few posts up) I was triggering "humidity high" at 62% RH regardless of baseline. Then my fan rule would shut it off after 10 mins since it was below baseline RH. I suppose this is probably unnecessary, but I've been known to have a touch of OCD at times.