-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request: rescheduling delay #75
Comments
This feature would be really appreciated ! +1 |
I circumvented this by keeping the heaters on but setting the baseline temperature to 15, meaning they would be effectively off. |
There is actually a way of doing it with HA - create a binary_sensor with
delay who mirrors your initial binary_sensor.
But it would be better that schedy manage it directly.
binary_sensor: - platform: template sensors: garage_door_delayed:
friendly_name: "Delayed Garage Door" #window_room: bedroom delay_on: seconds
: 180 delay_off: seconds: 360 value_template: >- {{
is_state('binary_sensor.porte_garage', 'on') }} icon_template: >- {% if
is_state('binary_sensor.porte_garage', 'on') %} mdi:door-open {% else %} mdi
:door-closed {% endif %}
Le dim. 1 janv. 2023 à 22:18, rickytenzer ***@***.***> a
écrit :
… This feature would be really appreciated ! +1
I circumvented this by keeping the heaters on but setting the baseline
temperature to 15, meaning they would be effectively off.
—
Reply to this email directly, view it on GitHub
<#75 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6Z5DIPDSWADAMMUHTJ6ITWQJCIFANCNFSM5TI4MNHQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Love Schedy! I have my baseboard heater schedules setup with presence sensing as well as outdoor temperature checks (they will turn off if the temp is above 10 C). I've also implemented rescheduling delays that work amazingly.
There is one thing that I can't figure out and maybe it's impossible: if the temperature is above 10 (meaning that the heaters are OFF), if I turn them back on for specific cases, I'd like for them to turn back to their previous state (OFF) after the set time, but that doesn't happen. I can probably circumvent this issue by dropping the temperature instead of turning them off, but I prefer them to be off.
How can I achieve this? Code below:
schedy_heating:
module: hass_apps_loader
class: SchedyApp
actor_type: thermostat
watched_entities:
- group.family
- input_boolean.guest_mode
- sensor.openweatherdetailed_temperature
- light.basement_sitting_area_main_lights
- light.basement_work_area_main_lights
- media_player.vizio_tv_3522
- switch.master_bathroom_fan
- switch.second_bathroom_fan
schedule_append:
- v: "19"
rooms:
basement:
actors:
climate.basement:
schedule:
- v: 17
rules:
- rules:
- x: "Next() if (state('group.family') == 'home' or state('input_boolean.guest_mode') == 'on') and (state('light.basement_sitting_area_main_lights') == 'on' or state('light.basement_work_area_main_lights') == 'on' or state('media_player.vizio_tv_3522') == 'ok') and float(state('sensor.openweatherdetailed_temperature')) < 10 else Break()"
- v: 21
- rules:
- x: "Next() if float(state('sensor.openweatherdetailed_temperature')) < 10 else Break()"
- v: 17
- rules:
- v: 'OFF'
rescheduling_delay: 15
entrance:
actors:
climate.entrance_room:
schedule:
- v: 19
rules:
- rules:
- x: "Next() if (state('group.family') == 'home' or state('input_boolean.guest_mode') == 'on') and float(state('sensor.openweatherdetailed_temperature')) < 10 else Break()"
- { v: 23, start: "07:00", end: "22:00", weekdays: 1-7 }
- rules:
- x: "Next() if float(state('sensor.openweatherdetailed_temperature')) < 10 else Break()"
- v: 19
- rules:
- v: 'OFF'
powder room:
actors:
climate.powder_room:
schedule:
- v: 19
rules:
- rules:
- x: "Next() if (state('group.family') == 'home' or state('input_boolean.guest_mode') == 'on') and float(state('sensor.openweatherdetailed_temperature')) < 10 else Break()"
- { v: 20.5, start: "07:00", end: "22:00", weekdays: 1-7 }
- rules:
- x: "Next() if float(state('sensor.openweatherdetailed_temperature')) < 10 else Break()"
- v: 19
- rules:
- v: 'OFF'
rescheduling_delay: 10
second bathroom:
actors:
climate.second_bathroom:
schedule:
- v: 19
rules:
- rules:
- x: "Next() if state('switch.second_bathroom_fan') == 'on' and float(state('sensor.openweatherdetailed_temperature')) < 10 else Break()"
- v: 22
- rules:
- x: "Next() if (state('group.family') == 'home' or state('input_boolean.guest_mode') == 'on') and float(state('sensor.openweatherdetailed_temperature')) < 10 else Break()"
- { v: 21, start: "07:00", end: "08:00", weekdays: 1-7 }
- { v: 22, start: "19:00", end: "20:00", weekdays: 1-7 }
- rules:
- x: "Next() if float(state('sensor.openweatherdetailed_temperature')) < 10 else Break()"
- v: 19
- rules:
- v: 'OFF'
rescheduling_delay: 30
master bathroom:
actors:
climate.master_bathroom:
schedule:
- v: 19
rules:
- rules:
- x: "Next() if state('switch.master_bathroom_fan') == 'on' and float(state('sensor.openweatherdetailed_temperature')) < 10 else Break()"
- v: 22
- rules:
- x: "Next() if (state('group.family') == 'home' or state('input_boolean.guest_mode') == 'on') and float(state('sensor.openweatherdetailed_temperature')) < 10 else Break()"
- { v: 22, start: "06:30", end: "08:00", weekdays: 1-7 }
- { v: 22, start: "20:00", end: "22:00", weekdays: 1-7 }
- rules:
- x: "Next() if float(state('sensor.openweatherdetailed_temperature')) < 10 else Break()"
- v: 19
- rules:
- v: 'OFF'
rescheduling_delay: 15
The text was updated successfully, but these errors were encountered: