So, I’ve created two scripts for turning the fan on and off, but I notice that it doesn’t always work properly. Today, the fan didn’t turn off. I’ve added a few repeats now to verify that the action has been executed. So, I suspect that this isn’t an ideal situation.
I can’t seem to figure it out. I have a Fan with 4 presets (Low, Medium, High, Auto). Is it possible to setup this blueprint in such a way that on ‘On’ it switches to ‘High’ and on ‘Off’ it switches to “Auto”.
I’ve tried creating a input helper (boolean) which triggers an automation doing the above. But I can’t select a boolean in the On (or Off) fields in the blueprint.
Edit: Never mind, I now use a script instead of a helper.
You will need to do something in this update. See below “Clear “input_fan_speed_off” YAML”.
Multiple Fan Speed Control - If you are using a fan with multiple speeds, you can now select 2 different speeds. We have called them “High” and “Low” but your selection could be “Med - Low” or “High - Med” etc. Before you could only turn OFF a multi speed fan, now you can select to run on high speed for X amount of time to then run on low speed for X amount of time, then turn OFF. You can also select to have different options for summer and winter, as in winter it could be advantageous to run the fan for a longer time period on low speed and in summer you could just turn it OFF
Lights Time Delay - If using the lights options you now have a separate time delay for them. This was added as you may not need the lights ON the entire time the fan is running
Turn OFF By-pass, the rising humidity is above set point and fans / lights (if enabled) are off? Fans and lights (if enabled) will now turn ON.
HA restart - If rising humidity is above and fans / lights are off, fans and lights (if enabled) will now turn ON.
BLUEPRINT CODE UPDATE
Just a heads up if your still on a old HA version before you update.
From time to time Home Assistant update their code structure and the old code will become “DEPRECATED” stopping / breaking automations from working. It effected this blueprint about 4 to 6 months ago. I wanted to wait some time so everyone had a chance to update their HA version before updating the code as older HA versions can not run the new code. This blueprint has now been updated so it will still operate once HA remove the “DEPRECATED” code from their system.
Clear “input_fan_speed_off” YAML
To clear your HA “input_fan_speed_off” YAML please follow these steps.
1 - Update you blueprint and open your automations.
thank you for your automation, i got it to work.
However, there is one strange thing.
The derivate sensor calculates the percentages divided by ten. So 1% rv rising, is 0.1% rising in the sensor. To clarify see the pictures.
Now i let the fan turn on at 0,1% so it works, but actually it is 1% What did i do wrong whit the derivate? i made it twice folowing exactly the steps.
Looking at the screen shot looks like you “bathroom RV” sensor is not reporting enough values. I have my humidity sensor reporting a value every 60 seconds. Can you confirm how often your humidity sensor report its value to HA. We need it to be fast and the helper has a time window of 3 minuets (if you set it up like this) so we need a few samples in the window. Don’t worry about building up data as HA automatically purge this data after a period of 10 days (default is 10 days). If you can make your bathroom RV sensor report at least every minute regardless.
I have my card in my dashboard show 2 hours as it also helps me keep a close eye on what it happening.
If you have a physical switch you can use it as long as that switch doesn’t control the fan. Example;
If you use your “physical switch (Aqara) which activates fan on or off” then HA looks at the fan being ON or OFF. So if the automation turns the fan ON it is like turning the by-pass ON at the same time and the automation will never work. It will turn the fan ON (turn the switch ON, Fan ON, By-pass ON, same, same) then depending on your by-pass selection it will then run this part of the automation.
No you can’t use your "physical switch (Aqara) which activates fan on or off " as the by-pass.
Nice, can you let us know if this resolved it as this is what I could see from the information you provided. If not can you provide a screen shot of your derivative settings and a 2 hour window of your sensors graphs.
The yellow bar on top is based on the heater hot water signal. I have a 10 second interval humidity sensor, that helps of course when working with derivatives. Sensor is away from the shower, close to the fan inlet.
So i have been using node red for this and i have just tried this blue print but I can’t get it to run, not via the trigger or when manually selecting run. My entities are correct, derivative sensor is working. here is the yaml: