The manual switch can not control the fan directly. You can’t use the switch connected to the fan. It has to be stand alone and it will only turn the fan ON and OFF. Low speed will not run.
If you would like to test it you can create a toggle helper and use that toggle as your manual switch.
If you are happy with it, you will probably have to add another Shelly in… like a Shelly plus 1 and wire another switch (or connect it to the existng fan switch and disconnect the other Shelly 2.5 to the switch) to it and connect it to nothing. Then use that switch to turn ON manual control.
I love your bathroom! Looks like you live in a hotel!
Question regarding ‘Automation Link - By-pass Control’ - can an automation be used as one of the entities? Automations can be turned on and off like an input_boolean. I use the Toilet Exhaust Fan blueprint and wondered if adding the blueprint automation into this field will simply turn the automation off and on as needed?
Yes but you will need to edit the code. The reason I say this is if your using my Toilet Exhaust Fan with time delay there is no by-pass yet… yes it is on the road map and I will make it work with this blueprint . Rather than edit the code I would suggest you create a template sensor that will do this for you, that way you never have to edit the blueprint code. It make it easer when updating. If you are not sure how to do this just reach out and I will provide the code for you.
FYI: When we enable and disable an automation it preforms not action, so it is basic function and not my recommendation. When we use the by-pass in my blueprints you have options, on what to do when you turn them ON (smart function). When we turn the by-pass OFF the blueprint analyse the automation and all your settings and tries to preform the correct action (smart function). So this is not realy good automation to enable or disable automations, just basic function. So if there is a by-pass I would recommend to use it rather than enabling and disabling an automation.
This Toilet Exhaust Fan with time delay blueprint has now been updated so it will work with this blueprint now. Just need to create a toggle helper and enter it into both blueprints. More information can be found in its thread Click Here.
You can use other humidity sensor and you don’t have to use the one I use but it must report at least every 60 seconds or on every state change.
I did a quick google search and still not sure what your sensor does. Your humidity sensor must report a value at least every 60 seconds. Some battery sensors report on every change and I think your one reports on 5% of change even when they say it report every 5 seconds. If it is 5% change then no it will not work. The best way it to see what your sensor reports.
@Blacky can I also use the derivative of an absolute humidity sensor? Currently the “rising” and “falling” has the % unit of measurement. If I use absolute humidity, the value will be a change of 200 mg/m3/minute or so, instead of 5%/minute.
Why absolute humidity? Value change is “sharper”; relative humidity value is damp(en)ed due to temperature rise that comes with it when taking a shower. A 5% relative humidity increase combined with a 2 degreeC increase is a 24% increase of absolute humidity (50% to 55%, 20 to 22 degC). See Absolute Humidity Calculator
@Blacky I am testing your blueprint out, and I have a manual binary switch setup in ESPhome called “binary_sensor.bath_sense_fan_10” The setup looks like:
I tried and pressed the temperature-open push button, but the fan did not turn on. Do I need to make the filter delayed_off longer than 250ms?
And do I insert a motion sensor somewhere in the blueprint? I do have a binary sensor in helper to bypass the motion sensor, setup I have is in node-red. In node-red I have disabled my fan on and off nodes.
I think I have to change the ESPhome to toggle switch, and not nomally open. It is a physical nomally open push button.
You are close but missing some things. Below is your code and some notes in the code.
# Enter this switch into the automation (manual fan switch) and into a HA dashboard if you like.
switch:
- platform: gpio
pin: GPIO19 # Set any spare pin you like it will do nothing
id: bathroom_manual_control # This ID is the link to the binary sensor
name: "Bathroom Fan - Manual Control" # Call it whatever you like
icon: "mdi:fan-clock"
binary_sensor:
- platform: gpio
pin: D0
name: ${display_name} Motion
device_class: motion
- platform: gpio
pin:
number: D3 # Wire from this pin to the push button on the wall and back to ground on esp32
inverted: true
mode:
input: true
pullup: true
name: ${display_name} "Fan 10"
on_press:
then:
- switch.toggle:
id: bathroom_manual_control # This is the link back to the switch ID above.
filters:
- delayed_on: 10ms # This is for the bounce in the push button, keeps things happy ;)
Here is a strange request. I live in Houston which can have a very humid climate. Is there a way to add a bit of logic so that if the humidity after the shower is less than the humidity outdoors, it will not run ? There is no point in exhausting the humidity if it will only get replaced by maybe even more humid air…
I have just been thinking about this since I put in a bathroom fan with a built in humidity sensor years ago, but it has a very short discharge hose that goes only about 1 or 2 feet. I think that the fan senses the outside humidity and just runs for hours. I’d like to prevent this.
This is interesting… I would think that is shouldn’t run if set up correctly.
You have a safe guard to stop this but maybe have a look at my set up as it just may help you. If you do have any further questions then please ask. To see my set up Click Here
. Rather than edit the code I would suggest you create a template sensor that will do this for you, that way you never have to edit the blueprint code. It make it easer when updating. If you are not sure how to do this just reach out and I will provide the code for you.
