You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, sorry for all the feature requests lately! I wanted to post this idea to get some feedback.
I would like to add support for an active_forced, and a new forced_sensors list. Or maybe a way for each entry in the sensors list to be an object with it's own options.
I think this is not quite the same as active_stay_on, because I want entity-controller to turn off the entity and regain control after all forced: sensors are off. This is sort of the opposite of overrides. Instead of disabling the entity controller, I have some sensors where I want them to force the entity to stay on until the sensor (or input boolean) is off. I typically need this for hygrostats and thermostats that are controlling temperature, humidity, or air quality.
Original Configuration
Here is the current configuration for one of my bathroom fans. This was really tricky to set up - I want the fan to turn on immediately via motion or door sensor whenever someone uses the bathroom. I also want to leave the fan running if there is high humidity (e.g. after a shower.) I want to turn the fan off if our balcony door is left open for 10 minutes since we will be getting lots of fresh air, so there's need to waste electricity running the fan. Finally, I want to disable the motion sensors at night so that our cats don't trigger the motion sensors and wake us up with the fan.
I also needed to set up a little flow in Node-RED to fill in some gaps: turn off the fan when certain overrides are activated, and turn on the fan for other overrides (input_boolean.keep_all_fans_on and binary_sensor.ensuite_bathroom_hygrostat).
I wasn't able to use on_enter_overridden: "..." because I needed "on" for some cases, and "off" for others.
Hello everyone,
Thanks danobot for this great integration, is really usefull.
i'm also interested by this feature. Force the entity-controller to stay active until a third sensor/entity is on and return into the "delay mode" when the third sensor pass to off.
Thanks
Description
Hello, sorry for all the feature requests lately! I wanted to post this idea to get some feedback.
I would like to add support for an
active_forced
, and a newforced_sensors
list. Or maybe a way for each entry in thesensors
list to be an object with it's own options.I think this is not quite the same as
active_stay_on
, because I want entity-controller to turn off the entity and regain control after allforced:
sensors are off. This is sort of the opposite ofoverrides
. Instead of disabling the entity controller, I have some sensors where I want them to force the entity to stay on until the sensor (or input boolean) is off. I typically need this for hygrostats and thermostats that are controlling temperature, humidity, or air quality.Original Configuration
Here is the current configuration for one of my bathroom fans. This was really tricky to set up - I want the fan to turn on immediately via motion or door sensor whenever someone uses the bathroom. I also want to leave the fan running if there is high humidity (e.g. after a shower.) I want to turn the fan off if our balcony door is left open for 10 minutes since we will be getting lots of fresh air, so there's need to waste electricity running the fan. Finally, I want to disable the motion sensors at night so that our cats don't trigger the motion sensors and wake us up with the fan.
I also needed to set up a little flow in Node-RED to fill in some gaps: turn off the fan when certain overrides are activated, and turn on the fan for other overrides (
input_boolean.keep_all_fans_on
andbinary_sensor.ensuite_bathroom_hygrostat
).I wasn't able to use
on_enter_overridden: "..."
because I needed "on" for some cases, and "off" for others.Proposed Configuration
I'm not sure about the naming, but I something like this would be very useful. I might try to experiment with this idea in my fork.
The text was updated successfully, but these errors were encountered: