Could you please provide us your YAML of the automation? 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.
itâs strange because i try to fill all the settings in blueprints when i click save, i didnât get error, but when i come back to see if the setting are save, they are not save.
After saving a blueprint automation, youâll find it listed under the Automationâs tab, not the Blueprints tab. A blueprint acts as a reusable template, allowing you to create multiple automations from it. For example, you could use the same blueprint to set up automations for three different bathrooms.
Once saved, each automation will appear under the Automationâs tab, where you can view and adjust its specific settings.
It might feel a bit confusing at first, but I hope this explanation clarifies things!
so for this fan i have a push button to control it, so i want to use this push button every time i think itâs necessary.
but with the current setting when i press the PB (shelly 1PM) the shelly start to flicker very fast on/off i donât think itâs suppose to work like that.
Fan Input: Only entities are supported; areas, devices, or labels cannot be included. I have adjusted this for you.
In Manual Trigger and Manual Fan Switch it cannot be your actual Fan Switch entity; it must be a completely different entity. I have removed this and disabled these options. You will need to find a different switch other than the fan switch. You could add a toggle helper but it will not be a physical switch but this may be a good way to test it out. When selecting the entity if you scroll down to the bottom you will see Create new Toggle Helper, this will create one for you and then you add it into a dashboard.
Hi Blacky,
Thank you for helping me.
I just want to point out , manual trigger work with phisical push button, i test it with delay time 5 min and works.
Now i think i need a little bit a fine tuning, i will explain why:
i take 2 showers with 5 min interval (i will post screenshoot)
the automation starts but only works for 5 min i will aspect to work till humidity falls back to normal levels
Your Fan is switch.ventilator_baie_mare_switch_0.
Your Manual Fan Switch is switch.ventilator_baie_mare_switch_0.
When you turn ON your manual switch the fan runs for 5 min as per your settings.
When the automation turns the fan ON it is the same as the manual fan switch, so it activates the manual fan switch and it runs for 5 min. This is what you are seeing.
If you would like to use the same entity for the fan and manual fan switch input then I do have a solution for your click here. It will show you how to do this. You will need a file editor to access your config file, click here as HA shows you how to do this.
Also note you can not use areas or devices in the fan input.
That look a lot better. Glad you got it all working now. It is an automation I really love.
Tidy Up: In your Manual Trigger remove the entity switch.ventilator_baie_mare_switch_0 in Manual Trigger this option is disabled so it wont do anything but it will help the performance of the automation.
TIP: If you are doing back to back showers then the Maximum Humidity Option is what will keep the fan going. You have already enter in your humidity sensor so if and when you are ready consider this option.
Any update on resolving the errors within logs caused by the manual switches?
Logger: homeassistant.components.homeassistant
Source: components/homeassistant/__init__.py:144
integration: Home Assistant Core Integration (documentation, issues)
First occurred: 5 December 2024 at 19:47:09 (9 occurrences)
Last logged: 08:23:11
The service homeassistant.turn_off does not support entities binary_sensor.manual_en_suite_fan_switch
The service homeassistant.turn_off does not support entities binary_sensor.manual_bathroom_fan_switch
This is because it is a binary sensor and you canât turn them ON or OFF. I do have another blueprint that I have not released yet. It just creates a manual switch like the template binary sensor so you can use it in this blueprint. If you like I can provide the link so you can test it out. It does the same as the template binary sensor but works a lot better. Let us know what you would like to do.
Iâve noticed after updating to the latest version of the blueprint, that a HA restart seens to trigger the automation? I saw the mention of a bugfix relating to HA restarts and manual switches being ON, so wondering if this is still happening in my case? The latest automation trace shows:
Hi Scott, what is happening when you restart HA your humidity is above 85 so it turns the fan ON but you donât have a Derivative Sensor so it will never drop below -1 because it has no entity and then just times out on your safeguard of 55 min.
You should really create and use a Derivative Sensor for the automation. It is in the FAQ.
Hi. The blueprint looks great & is very well explained; thank you.
However I have failed to get it to save when I enter entity idâs for the derivative trigger & the fan sensor.drev_shower sensor.3_shower_humidity switch.mss710_9d5c_outlet1
I have also tried renaming the sensor to
sensor.shower_humidity
& loading from the blueprint from the community forum & Github, but each time I get" Message malformed: extra keys not allowed @ data[âtriggersâ] "
I canât work out whatâs wrong - I guess something in my naming doesnât fit the syntax, but Iâve no idea what.
Core2024.8.3
Supervisor2024.11.4
Operating System12.3
Frontend20240809.0
Raspberry PI 3b with HA install.