Giter VIP home page Giter VIP logo

Comments (6)

nielsfaber avatar nielsfaber commented on May 29, 2024

How would you do this in HA (outside of scheduler)? If some service call exist to increase/decrease temperature setting I can add support for this in scheduler.

from scheduler-component.

bensuffolk avatar bensuffolk commented on May 29, 2024

I don't think you can do it on HA. But the way I assumed it would work is you must already store a set temperature for each schedule slot. So I if you also store the offset value, you would do a little bit of math and then set the thermostat to the shceuled temp less the offset.

The offset would only be settable via call so no need to change the GUI at all. I was thinking it would be a global offset for eery schedule.

from scheduler-component.

mhaket avatar mhaket commented on May 29, 2024

The way I solved this is, is by defining two different schedules and switching between the two with a binary switch. Being able to do this within a single schedule would be nice but in my opinion not perse necessary.

from scheduler-component.

bensuffolk avatar bensuffolk commented on May 29, 2024

@mhaket yes I can see that would work. Its a bit more of a faff to alter multiple schedules though. I was thinking of having the offset slide on a scale based on how far away I was form home (e.g. if I'm an 8 hour drive away, I'm not coming home any time soon so can have it get cooler than if I was at the office 30 mins away).

But its a cludge to implement something now. Thanks for the suggestion.

from scheduler-component.

jbergler avatar jbergler commented on May 29, 2024

Another approach to this is to use a script for changing the climate entity with input parameters.
In the script you can apply custom logic to adjust the requested temperature.

You then control this script from the schedule.

The script I use (not for this use case exactly) is

alias: Set heatpump
description: Sets climate parameters for scheduler-card
variables:
  target_entity: climate.heat_pump
sequence:
  - repeat:
      count: 2
      sequence:
        - service: climate.set_hvac_mode
          target:
            entity_id: "{{ target_entity }}"
          data:
            hvac_mode: "{{ hvac_mode }}"
        - delay:
            hours: 0
            minutes: 0
            seconds: 2
            milliseconds: 0
        - service: climate.set_temperature
          data:
            temperature: "{{ temperature }}"
          target:
            entity_id: "{{ target_entity }}"
        - delay:
            hours: 0
            minutes: 0
            seconds: 2
            milliseconds: 0
        - service: climate.set_fan_mode
          target:
            entity_id: "{{ target_entity }}"
          data:
            fan_mode: "{{ fan_mode }}"
        - delay:
            hours: 0
            minutes: 0
            seconds: 30
            milliseconds: 0
mode: single
icon: mdi:air-conditioner

I've configured the scheduler card like this

  - type: custom:scheduler-card
    title: false
    discover_existing: false
    time_step: 15
    include:
      - binary_sensor.anyone_home
      - sensor.heatpump_mode
      - climate.heat_pump
    exclude: []
    display_options:
      primary_info: '{entity}: {action}'
      secondary_info:
        - relative-time
      icon: action
    show_header_toggle: false
    customize:
      script.set_heatpump:
        actions:
          - service: script.set_heatpump
            name: Set heatpump
            icon: mdi:air-conditioner
            variables:
              hvac_mode:
                name: Mode
                options:
                  - value: 'off'
                    icon: mdi:power-off
                  - value: heat_cool
                    icon: mdi:renew
                  - value: heat
                    icon: mdi:fire
                  - value: cool
                    icon: mdi:snowflake
                  - value: dry
                    icon: mdi:air-humidifer
                  - value: fan_only
                    icon: mdi:fan
              temperature:
                name: Temperature
                min: 16
                max: 25
              fan_mode:
                name: Fan mode
                options:
                  - value: auto
                    icon: mdi:fan-auto
                  - value: low
                    icon: mdi:fan-speed-1
                  - value: medium
                    icon: mdi:fan-speed-2
                  - value: high
                    icon: mdi:fan-speed-3

from scheduler-component.

github-actions avatar github-actions commented on May 29, 2024

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

from scheduler-component.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.