Add schedules

[Se7enair]

I'am already using your code. Very nice, saves me a lot of work.
But for now I have to use "schedy" additionally to that. Schedy is doing all the scheduling for me.
So I use more than a simple day and night schedule. For example, when nobody is at home, the heating is running on a lower temperature. But when somebody is coming home, it should already warm, so I need to start the heating before I arrive at home.
Or the bathroom, it is heated only on specific times and somebody needs to be home. Otherwise it will stay on the lower temperature.

Is this something you could imagine to integrate? If yes, this will be really a "better thermostat" and I can give you information how about I realized my heating control.

For now, I can show you my schedy_heating.yaml, but there are few more automations which are controlling the input_booleans.

schedy_heating: # This is our app instance name.
  module: hass_apps_loader
  class: SchedyApp
  schedule_prepend:
    - x: "OFF if float(state('sensor.openweathermap_temperature')) > 15 else Next()"
    - x: "OFF if is_off('input_boolean.heizung') else Next()"
  watched_entities:
    - "group.haus"
    - "sensor.openweathermap_temperature"
    - "input_boolean.absent_long"
    - "group.ferien_und_feiertage"
    - "binary_sensor.bad_fenster_links_contact"
    - "input_boolean.heizung"
    - "input_boolean.unplanmaessig_zuhause"
    - "input_boolean.homeoffice"
    - "input_boolean.partymodus"
    - "input_boolean.kachelofen"
  actor_type: thermostat
  rooms:
    wohnesszimmer:
      actors:
        climate.wohnzimmer_heizung_links:
        climate.wohnzimmer_heizung_rechts:
          hvac_mode_on: auto
          off_temp: 5
        climate.esszimmer_heizung_links:
          hvac_mode_on: auto
          off_temp: 5
        climate.esszimmer_heizung_rechts:
      schedule:
        - v: 21.5
          rules:
            - x: "Next() if is_off('input_boolean.kachelofen') else 'off'"
            - rules:
                - x: "Next() if (is_on('group.ferien_und_feiertage') or is_on('input_boolean.unplanmaessig_zuhause'))and is_off('input_boolean.absent_long') else Break()"
                - { start: "06:00", end: "22:00" }
            - rules:
                - x: "Next() if is_on('input_boolean.partymodus') else Break()"
                - v: 21
            - weekdays: 1-4
              rules:
                - x: "Next() if is_off('input_boolean.absent_long') else Break()"
                - { start: "12:00", end: "21:00" }
            - weekdays: 5
              rules:
                - x: "Next() if is_off('input_boolean.absent_long') else Break()"
                - { start: "11:30", end: "22:00" }
            - weekdays: 6
              rules:
                - x: "Next() if is_off('input_boolean.absent_long') else Break()"
                - { start: "06:00", end: "22:00" }
            - weekdays: 7
              rules:
                - x: "Next() if is_off('input_boolean.absent_long') else Break()"
                - { start: "06:00", end: "21:00" }
        - v: 18
    
    schlafzimmer:
      actors:
        climate.schlafzimmer_heizung:
      schedule:
        - v: 21
          rules:
            - weekdays: 1-5
              rules:
                - x: "Next() if is_off('input_boolean.absent_long') else Break()"
                - { start: "05:30", end: "06:30" }
            - weekdays: 6-7
              rules:
                - x: "Next() if is_off('input_boolean.absent_long') else Break()"
                - { start: "07:00", end: "09:00" }
        - v: 19

    buero:
      actors:
        climate.buero_heizung:
          hvac_mode_on: auto
          off_temp: 5
      schedule:
        - v: 21
          rules:
            - x: "Next() if is_on('input_boolean.homeoffice') else Break()"
            - { start: "06:00", end: "22:00" }
        - v: 18

    bad:
      actors:
        climate.bad_heizung:
          hvac_mode_on: auto
          off_temp: 5
      schedule:
        - v: 23
          rules:
            - rules:
                - x: "Next() if is_on('input_boolean.partymodus') else Break()"
                - v: 23
            - x: "Next() if is_on('group.haus') else Break()"
            - x: "Next() if is_off('binary_sensor.bad_fenster_links_contact') else 'off'"
            - { start: "05:00", end: "08:00" }
            - { start: "18:00", end: "21:00" }
        - v: 19

[Cycor]

I'm using the Scheduler integration for my climate automations, it makes the basic rules very easy to manage for my non-programming family members. It also has conditions but I haven't used that yet.
https://github.com/nielsfaber/scheduler-card

Personally I would keep automations out of the plugin, it causes unnecessary complexity that can easily be handled by home assistant itself.

[Denis-blr]

I fully support the author with the idea of adding a schedule for the daytime operation of the thermal head. Toby, actually for the ai_thermostat integration this would be a big plus. Your integration would completely control the heating. All you need to do is add the ability to schedule daytime and the ability to set the desired temperature.
I use a Saswell SEA801-Zigbee/SEA802-Zigbee thermal head, the time scheduling option is in the Tuya app, and I have already moved to ai_thermostat and have to do everything manually.

[KartoffelToby]

@Cycor @Denis-blr @Se7enair
Simple solution, what if i replace the night mode thing with a array configuration style?:

Like

climate:
  - platform: ai_thermostat
    name: room
    thermostat: climate.tvr
    temperature_sensor: sensor.temperature
    window_sensors: group.office_windows #if this is not set, the window open detection is off
    weather: weather.xxx #if this is set, the outdoor_sensor is ignored, remove the outdoor_sensor config!
    outdoor_sensor: sensor.outdoor_temperature #if you want to use it, remove the weather config!
    off_temperature: 20
    window_off_delay: 0
    valve_maintenance: false
    scheduler:
      - name: Night
        temperature: 19
        start: "22:00"
        end: "07:00"
      - name: Day
        temperature: 17
        start: "13:00"
        end: "14:00"
      - name: anyotherword
        temperature: 12
        weekdays:
          - mon
          - tue
          - wed
          - thu
          - fri
        start: "15:00"
        end: "16:00"

[Se7enair]

For the first this could be a idea. But I would need conditions on that. So for example, if I am not at home, I want a lower temperature. Or maybe another schedule on the weekend then on weekdays.

[KartoffelToby]

I think about trigger entities, to do something like turn of if a door is open, or a button is pressed or something else,
but i think this is really a thing for HA Automations not for the Thermostat itself. the away thing is a point that i will be add by side the schedules. but yes, for all other special cases they option to override states with HA Automation will be the better one.

[KartoffelToby]

I mean, this option will make it extream complicated for most users,

must look like this:

    scheduler:
      - name: Night
        trigger: sensor.entiy
        state: away
        temperature: 19
        start: "22:00"
        end: "07:00"

And this can only handly a if than operation, not or when, or combine multiple other sensors or states, so its too much, to be honest, there are probably too many problems for it. So if someone needs more than a daily routine, it must be handeled by a HA Automation.

But for the weekdays, i have a update (look at the edit post)

[Denis-blr]

Great solution! How many gaps will the array be divided into? I think that a maximum of 5 gaps will be enough, everyone will decide whether he needs to use 2 or 3 or 5 gaps. пт, 17 дек. 2021 г. в 20:38, Tobias Haber ***@***.***>:

…

@Cycor <https://github.com/Cycor> @Denis-blr <https://github.com/Denis-blr> Simple solution, what if i replace the night mode thing with a array configuration style?: Like climate: - platform: ai_thermostat name: room thermostat: climate.tvr temperature_sensor: sensor.temperature window_sensors: group.office_windows #if this is not set, the window open detection is off weather: weather.xxx #if this is set, the outdoor_sensor is ignored, remove the outdoor_sensor config! outdoor_sensor: sensor.outdoor_temperature #if you want to use it, remove the weather config! off_temperature: 20 window_off_delay: 0 valve_maintenance: false scheduler: - name: Night temperature: 19 start: "22:00" end: "07:00" - name: Day temperature: 17 start: "13:00" end: "14:00" - name: anyotherword temperature: 12 start: "15:00" end: "16:00" — Reply to this email directly, view it on GitHub <#93 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATVNTK5UJ523ZVUV2HHCVETURNYPZANCNFSM5J4CDIKQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[KartoffelToby]

What do you mean by how many gaps? You can add infinity points, as long as they will have different names, i guess, its just a sketch config. Every entry as has a name, target temp, start and end time.

[Denis-blr]

Toby I totally agree with you that adding a time period and specifying a temperature is a job for HA automation. Your integration does a completely different job. I appreciate your work! scheduler: - name: Night temperature: 19 start: "22:00" end: "07:00" - name: Day temperature: 17 start: "13:00" end: "14:00" - name: anyotherword temperature: 12 start: "15:00" end: "16:00." I believe that this entry will not make your work worse, but only allow users to trust their devices 100% to the AI THERMOSTAT for Zigbee2MQTT project. Your HELP is very well written, setting up the thermal head is not difficult. вс, 19 дек. 2021 г. в 03:01, Tobias Haber ***@***.***>:

…

I mean, this option will make it extream complicated for most users, must look like this: scheduler: - name: Night trigger: sensor.entiy state: away temperature: 19 start: "22:00" end: "07:00" And this can only handly a if than operation, not or when, or combine multiple other sensors or states, so its too much, to be honest, there are probably too many problems for it. So if someone needs more than a daily routine, it must be handeled by a HA Automation. But for the weekdays, i have a update (look at the edit post) — Reply to this email directly, view it on GitHub <#93 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATVNTKYREZK2RNZOP26KQITURUOG7ANCNFSM5J4CDIKQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[Se7enair]

I can totally understand when somebody says thre scheduling should be done in homeassistant.
I thought about a All in one solution for thermostats. But yes, this will be a difficult thing to solve.

There are a few great solutions for schedules out there. Just wanted to place a idea and waited if it maybe grows.

[chris400]

I second this.
There is also another aspect why I would like to have a schedule in BT: reaching the target temperature.
Let's say you want you office to be at 21°C at 08:00. Throughout the night it only be heated to 16°C. So heating would need to start before 08:00.
Adapting the logic from BT it would be very nice to have have the room temperature at 21°C at 08:00.

[Denis-blr]

@KartoffelToby
Please tell me, do you plan to add the schedule in the next update?

[KartoffelToby]

@KartoffelToby
Please tell me, do you plan to add the schedule in the next update?

Currently the Focus ist on a stable code rewrite, but i hope its implementet this year

[Denis-blr]

Hi,
Have you changed your mind about adding this option to your integration yet? :)

[Denis-blr]

Hi, please tell me, will we have a chance to test the final version of release 1.0 this season? Because the heating season will be over soon)

[andreamag00]

Maybe somebody could find interesting an alternative solution for schedules that I’m using and you can create and modify directly in UI (without having to change yaml code)

#721 (comment)

[james-fry]

Bit of a necro of an old thread, I know.
You can use https://github.com/nielsfaber/scheduler-component
Install custom component and card via HACS.
It has a decent UI for setting up schedules...