Looking at your YAML I am going to assume you have your Fan Switch and your Fan Speed - Switch Off correct.
Everything looked good, I just found one thing that may cause a problem. You have enabled Manual Fan Switch, option 2 - Enable manual fan switch + auto off option but you have no entity in the input. Please disable this option.
Once your derivative goes below -1 then your Time Delay starts and it should turn OFF in summer 10 min and winter 15 min.
Test it again now the Manual Fan Switch is disabled and see if that fixed it.
I am sad to report that the core/derivative file got modified 3 days ago. This modification screwed us over as far as the use of Humidity Derivative in this awesome Blueprint.
@joostlek from the below link made a modification to the derivative value.
FROM: derivative = Decimal(0.00)
to THIS: derivative = Decimal("0.00")
I am including MY chart values from this morning and also from prior to the change.
Luckily, this Blueprint is so awesome it had a “backup” method of activating the exhaust fan when the MAXIMUM HUMIDITY setpoint had been reached.
I’m not going to bother attempting to contact anyone else to get this corrected. I will just download the prior version of the core/derivative code and override the recent update.
If you compare my 2 graphs, you’ll see they are off by a factor of about 50. This means our helper for this Blueprint is useless.
So, in a nutshell, the derivative = Decimal("0.00") change broke everyone’s derivative helper.
Prior to your change, the humidity derivative would reach 5-10% when the humidity increases. Now, the derivative will not reach 0.08% (8/100ths of 1%).
P.S. It’s been a very long time since I’ve done any programming and I’ll admit I do not know Python but, from the looks of your change, it looks like you changed a numeric floating point variable into a String.
Not sure if you are using Z2M sensors. If you are my understanding is they changed the sensor ID’s. You’ll have to delete the old sensor ID’s and enable the new one, in each device, then change all the automations / sensors that used the old sensor ID’s. I don’t think it is this because you said that your using the humidity sensor but maybe it might lead you to finding the solution.
Have you tried deleting your Derivative sensor, rebooting HA and then creating a new one?
Right, I found this out because ruff is catching things like this. 0.00 is resolved as 0.0. “0.00” will be resolved as 0.00. so in theory the code is now doing what is expected for it to do. But now we have to find out what is more correct. Do you mind opening a GitHub issue with your findings?
Hi Blacky,
this seems to be what I am looking for. As of right now, I have no exhaust fan in my bathromm, but will need one. I am 90% sure, it will be a fan plugged into a wall switch (with zigbee). There is electrical wirering in the hole for the fan, and they might conduct electricity, but as I know my landlord, those five wires might not even be on the same fuse
So will the bluebprint work with a wallplug? I know, that the fan will then not be able to change speeds. But all those other great features you wrote would be great for me
If the plug is smart and Home Assistant (HA) can control it (turn it ON and OFF), and if the fan turns ON and OFF when the plug is toggled, you don’t need a fan with different speeds. All my fans are single-speed, so this approach works great. Since you’re renting, a smart plug is a good option because you can take it with you when you move.
Here’s what I’d do:
Set the wall switch to always stay ON, powering a hardwired ceiling plug.
Plug a smart plug into the hardwired plug and connect the fan to the smart plug.
Use HA to control the smart plug, turning the fan ON and OFF via automation.
When you move, you can unplug the smart plug, reconnect the fan directly to the hardwired plug, and the wall switch will resume control of the fan.
Hi Blacky
I have been using this Blueprint and the Sensor Light Blueprint for a few months now with the Apollo MSR-2 in my ensuite. Everything was working perfectly until some updates in December.
Now when the humidity trigger is reached my Heated Towel rail(no fan yet) is turned on but also my Ensuite night light.
This light entity isn’t known by the Humidity Exaust fan Blueprint, but it’s still turned on. Automation link is disabled.
Thanks for replying.
Yes the Apollo only triggers the light when the lux falls below a certain value (get dark).
It seams the night night settings are being triggered at the same time as my heated towel rail, the light stays on for an hour, the same duration as the heated towel rail.
Normally the night light function is triggered on presence between 10pm and 5am, turns off 3seconds after leaving the room.
Could you provide your YAML for the bathroom and sensor light blueprint. I would like to look into this in more detail encase I have missed something. This YAML code are the settings you have selected in the automation so I can help. To do this go into your automation, top right 3 dots, Edit in YAML, copy all the code, come back to the forum and in your reply at the top tool bar click on “</>” and paste code in there.
