i am having trouble detecting the Fan-Off moment. The start detection works flawless as the %/min shoots up like a rocket, but as soon as the humidity reaches 100%, the helper calculates a derivative off of course. Then the slightest drop under 100% will cause the automation to trigger the time-out of the standard 20minutes. I tried to improve the sensitivity of the âfalling humidityâ all the way to -0.2%, but as you can see it still triggers way to early. I already tried to average the helper over 5minutes, hoping to make it less sensitive to the fall from 100%. I could adjust the time-out to much longer, but this is kind of the point of this automation. Any tips?
To me it looks like it is going off on the default âSafe Guard - Maximum Run Timeâ of 20 min. This is not a trigger just a time delay of when the fan turns on. The âFalling Humidityâ trigger is around 11:45 and the fan is already off. The falling humidity trigger is a negative value.
The âFalling Humidityâ trigger happened around 11:45. You can see the humidity is falling as well. Reset back to 3 minutes on the helper and set your falling humidity back to -1.
In your fan I can see âafziging lightâ is this a fan, or a light, or a fan and a light.
Can you confirm the fan is coming on?
If the fan is on, it looks like it not removing the steam. Can you confirm the steam is being removed.
If the steam is being removed then looks like the sensor is not reacting to the steam fast enough or something is happening with your humidity sensor. Maybe the humidity sensor is getting filled up with steam and it has to dry out. Check the position of the humidity sensor, maybe relocate it.
If the steam is not being removed is the fan big enough to do the job?
ill reset some values, maybe if i increase the time-out, it would wait for the falling humidity trigger.
You are right that the sensor quickly âfillsâ with 100% humidity. The thing is that we have 2 showerheads and shower together, creating alot of extra humid air. If one person showers alone the humidity does barely touch the 100%. At this point the humidity of the bathroom has shown a 5x faster drying time compared to no mechanical ventilation. It might be too weak for 2 showerheads.
Yes, âafzuiging lightâ is a Sonoff relays that switches the fan on/off. It is turning on thanks to your automation.
I could also place it a little lower in the room, further away from the ceiling, maybe that could help too. Anyway, thanks for the responce again!
I had the same problem creating a derivative - the adding/deleting/restarting didnât work for me but itâs easy enough to add by editing the configuration.yaml file. For other noobs like me, just use the file editor to add something similar to the following, check the configuration for errors, then restart.
Hi @lk229 thanks for sharing you tip and your code I am sure it will help others.
If you have time could and you still canât see your time window, could you try 2 things.
1/ Reboot your HA, not restart but a reboot and check options. If you are on the latest HA then it will be âsettings/system/top right power button/advance options/ then reboot systemâ.
if that doesnât work can your try
2/ Add a derivative sensor without the time window using helper. Then reboot your HA and check all options.
It will help HA resolve the glitch as this will be a hard one to find and maybe with all our help we can help HA.
My time window is now showing when creating a new derivative. Unfortunately, this means I canât help debug in case anyone else is having this problem.
If it means anything, I did update to 2023.3.4 in between the problem appearing and now. Also, you made me realize that I hadnât rebooted my RP4, only restarted HA.
Hi Lee, glad you got it working now. I have also done some testing and have found if you reboot your HA is will show up again. I have given my 2 cents worth to HA in this bug report (Click Here). Maybe they will take a look at it .
Sometimes if a family member manually switches off the fan, it comes back on a few minutes later. Wife doesnât like that after a pre-sleep showerâŚis there a way to have it not turn back on if manually switched off? Or better to just set a time window to have the automation run/not run?
Hi Markus. With this automation the trigger is the derivative sensor. You dont want the fan to be a trigger. If you have a switch that turns the fan ON then the fan will be the trigger and that is not good. I would look at having a independent switch and make that the trigger so when you turn it ON it turns the fan ON with a time delay.
I am assuming you have a toilet in the bathroom. If so maybe consider my Toilet Exhaust Fan with time delay blueprint and once you have a independent switch (maybe have a push button would be good, on / off in one push) use that as the trigger in the Toilet Exhaust Fan blueprint.
Thanks for that. Having a seperate button is nothing I would like to do. The spouse will freak out.
I think the best way forward here is to have a boolean variable which sets to true when your Automation fires. I can then have a condition check on my Automation for the button saying when it is turned on, check if it was turned on by the Automation (with the boolean variable) and if so, do not run the 15 minute delay and cancel the Automation.
And if your automation ran and finished, set back the boolean to false.
I am not sure if I can implement this myself using your Blueprint. Thoughts?
Agree, maybe consider just using your existing switch, disconnect the switch from the fan and install a Shelly Plus i4. Then when you turn that switch on (Shelly Plus i4) the fan comes on.