Core support for climate schedule

Feature Requests
1

Hi,

Without Core support for climate schedule it is very hard to implement very needed simple actions.
For example doing following:
*) If electricity tariff is low, rise heating temperature.
In ideal solution, use another pre created heating schedule.
*) If electricity tariff is high, lower heating temperature.
In ideal solution, use another pre created heating schedule.
*) If electricity tariff is normal then resume to normal heating schedule.

The most universal way is to introduce current electricity tariff rate in core and
each created heating schedule require price range value on what it operates.
Integrations can provide current electricity tariff.
Under current price i mean price at this timepoint, then it is not important if metering is minute, hour, day, … based - as long as some integration keeps current pice fresh.

Something like that:

climate2
climate21510Ă—600 71.7 KB

Also thermostats should be able override current heating schedule with specified time.

Any thoughts ?

2

Thermostat:
thermostat

3

It really isn’t.

One trigger - your electricity tariff.

One choose action based on that value and three weekly schedule helpers.

4

Ok real life scenario with our hourly based tariffs.
One hour tariff 3 cents, next 30 cents , next 10 cents.
Daily timer sets temperature 22c.
Now 3(low price) cents arrive, automation trigger sets temperature to 24c.
Next hour arrives with 30(high price) cents, automation trigger sets temperature to 22C.
Next hour arrives with 10 cents, how to return normal heating schedule at the point of current time ?

Also if you have many thermostats, you run into automation trigger hell.

5

Why?
You should trigger on the tariff not the thermostats.
You can set several thermostats at the same time with the same action.
Not really sure I see your problem here.

6

Yes, but when cheap hour ends, how you resume on daily scheduler(if use some integration) ?
Schedule is time dependent, so you need resume temperature of current time.

7

The same way you did with all the other tariffs. Trigger when the tariff changes.

8

The current schedule helper lacks a value you can set on each schedule, e.g. temperature in this instance. The helper would greatly improve if you can set a value (default being on/off what it is now) and set that value when the schedule activates.

9

Not if you use YAML. Support for this was added last release.

But that’s beside the point. Don’t use the schedules to set the value, use them to select a choose action that sets the value.

10

As said you will need to duplicate schedule in daily schedule and then same schedule in trigger.
Also you don’t any overview what controls actual scheduling.

I havae 5 room thermostats, 1 air source heat pump, 1 electric floor heating.
Now adding triggers for these with time of day dependent …

11

Have you seen this?

It does what you want.

12

How could I have missed the changes to the schedule helper? :+1:t2:
I do use the advanced scheduler integration because it has a UI, but that is rather complicated due to the endless possibilities. I want the family to be able to change setpoints, yaml is not going to sit well with them. :wink:

Edit: talking to myself, apparently. :rofl:

13

I checked this component soma day ago, yes it can do basic scheduling.

You miss the point.
If trigger ends(for example tariff goes normal), how i resume to your suggested scheduler component at specific time point ?
Also in trigger i want different temperature for same price on different time.
For example:
Tariff 1 cent, time 8-18 , temperature 24
Tariff 1 cent, time 18-24, temperature 22
…

I must say Fibaro climate scheduling is far more cleaner easier to use.
The only cause moving away from fibaro is they hav’t released any real update in 2 years.

14

Whatever you did one way can be done the other way also.

That’s a time trigger.
But it would also mean you need time conditions in your choose in the automation.

15

All a climate schedule do is set the temperature.
The rest of the decision process is something that is specific to each user and can not be made in a core component.
The scheduler integration is an attempt to do that and you said it was too complicated for you.
If it is less complicated then the author will have to decide what settings should be hidden and what values they then should be hardcoded to, which will most likely not be what you want.

1 Like
16

The scheduler integration is an attempt to do that and you said it was too >complicated for you.
It’s not complicated.
It works as long as you don’t mess temperatures in triggers.
As

And there is my point: you need to implement another duplicated schedule in trigger to get right temperature for the time.All this because how you tell scheduler component to resume(trigger changed normal heating schedule)

17

Can’t you do a scene and then just call that?

18

And what i do in scene ?
Notify scheduler component to resume ? How ?
Build duplicate scheduler component in scene ? Then if any changes temperature to be made, must be do multiple places and must remember how many places related to another.

19

If it is a complicated decision process with many outcomes then yes, but it will have to be done in all solutions anyway.

20

For example in Fibaro you can do this simple.

  1. Create complicated climate schedule in UI - any user with out any knowledge can drag and drop setpoins for day and do it for all days. Very easy to alter time/temperature any time.
    (First image in post - just photoshoped tariff part to it.)
  2. Make only 1 timer per wanted period, in hourly based tariffs - timer for 1 h.
  3. Set(Override schedule) thermostat for desired temperature for 58 minutes.
    After thermostat minutes elapsed, thermostat switches automatically to normal schedule.
    … timer loop starts again

The only reason to move from Fibaro is that they haven’t done any major update during 3 years i used it. So future doesn’t seem bright for them.