Big applause !!! Very impressive !
French and english versions :
Thanks
Bravo @neliss !
ButâŚ
It would seem that when WORKDAY: is set to consider Saturday as a working day it presents the weekend with a start on Saturday at 00.00 when it should be Sunday at 00.00.
I remind you that the advantage of using WORKDAY: is to be able to override any day as a holidayâŚ
Itâs a bit off topic, but does anyone know how to predefine on the standard CLIMATE component teperature values that would correspond to ECO or COMFORT? (I had done it with input_number but itâs not very practicalâŚ)
What did you put in secondary on these cards?
Have you found a way to extract and display the atrtributes of the Schedule entity?
See my config 5 topics above
I was not interested (for the moment) to extract this kind of information. Sorry
Okay, I thought it was a card entity!
Hello @neliss
iâm afraid I have the same issue !
All my 7 heaters have two sets of scheduler : one for the workdays and one for the week-end.
All the schedulers for the week-end did not fire yesterday (saturday) and they all fired this morning (sunday) on due time.
Week-end schedulers are scheduled to start on âsaturday at midnightâ. For me âsaturday at midnightâ means in the night between saturday and sunday.
In the night between friday and saturday should be âfriday at midnightâ ?
Am I right ?
Check these out:
Thanks for this clarification.
However that is not the issue.
The issue is that the scheduler does not fire on saturday morning (despite the fact it is schedule for the week-end) but only on sunday morning.
I will check if it fires tomorrow morning.
regards
@Merangle I would recommend to avoid using midnight as scheduled time.
I cannot say for sure on which day it would trigger, depends on how the date/time functions in HA are processing it (and its a matter of definition as @KTibow says).
Why make it difficult for yourself? I would just set it one minute earlier or later to avoid problems. But in my case I would be sleeping usually 
For time schemes the view is limited from 00:00-23:59, so that is what I would consider as a full day.
Hello @neliss
I do not schedule any scheduler at midnight.
Please have a look at those three pictures:
The first one is a screenshot of the scheduler card with two schedules : one which should fire on workdays at 05:30 AM and the second one that should fire on week-end at 6:00 AM
The first one on workdays fired last week. The second one (on week-end) did dont fire saturday but sunday.
As you can see, none of them are secheduled to start on midnight. however on can see on the schduler card âsaturday at midnightâ which is not consistent with the first scheduled time.
This a copy of the state screen
entries:
- 67DT0000T0600A0
- 67DT0600T1000A1
- 67DT1000T0000A0
actions:
- service: set_temperature
entity: climate.sdb
hvac_mode: heat
temperature: 17.5
- service: set_temperature
entity: climate.sdb
hvac_mode: heat
temperature: 20
next_trigger: '2020-11-14T00:00:00+01:00'
friendly_name: SdB Week-end
icon: 'mdi:calendar-clock'
As you can see the next trigger time is next saturday 11/14 on 00:00. Which is not the scheduled time.
Do you need additional information ?
And this morning, two schedulers at least were not triggered:
What can i do to help you ?
thanks
@Merangle
Your question/issue is not really clear to me, you shared a lot of pictures, but they donât give much info to me.
If you think there is a bug with workday/weekend setting, create an issue for it in GitHub of the scheduler-component.
Please share the following information:
- The attributes of the schedule entity that does not work as you expect
- History / logbook info of this schedule and the device it should trigger, around the time you expected it to trigger (to show that it skips this time)
- Are you using the workday integration? If yes, then share its configuration too.
- Which climate integration are you using?
- You told me before you are using scripts to combine your climates. Are they related to the issue?
In v1.9.5 I added a small enhancement to editing an existing schedule:
If you click on the displayed entity + action, you will be brought back to the selection panel and you can make changes to the entity and/or action.
I can imagine some of you were missing this functionality (and were forced to remove it and create a new one).
Its a bit of a âhiddenâ feature because I didnât want to add extra buttons to the GUI (on mobile phone space is kind of limited).
So here a small guide:
The function preserves the settings for days, time (/timeslots) and all additional options.
If you change the action or entity, the function attempts to preserve your settings (such as temperature), but it may not work (yet) for all scenarios.
I recommend not to try any funny stuff like changing a schedule for a thermostat into a lamp
3 Likes
@snoopy1492 please let us knowâŚ
Iâm still fighting with the same problem since a couple of week.
Generic Thermostat + scheduler = only temp change with no switch action
All other schedules works flawlessly (lights, switches and even my garden sprinklers). Amazing job @neliss
1 Like
Please read my comment about this.
The scheduler doesnât really have anything to do with it.
It seems quite weird to me that when you update the temperature setpoint, the device stays OFF.
This is a bug/limitation in the generic_thermostat that causes this.
I donât know if someone already took initiative to have it fixedâŚ
1 Like
nice workaround, thank you!
sorry for the off-topic
OK guys, I havenât had time to install all the prerequisites to install the dev environment for HA.
(Working from home is a pain, time just flies away)
In the meantime, youâll find my custom_components at this link.
This is my custom component.
Copy the contents of generic_thermostat to <your config dir>/custom_components/generic_thermostat/ and restart HA. It should now use this version instead of the one included with HA.
Beware, Iâm giving this as is. It works for me but could break something (unlikely due to the minimum amount of change I made, but I prefer to err on the side of caution).
And if a change is made to the generic_thermostat in a future update, this custom_component will prevent you from using it until you delete it.
Iâll try to find the time to finish installing a dev environment for HA and push my fix.
2 Likes
Hello snoopy1492,
It works very well !!!
Youâre a genius !
1 Like
Hi have a problem, i cannot have my switch to turn on. I tried set a schema and also set a simple time but no action executed. How to debug this? Seems that nothing is wroted.
- type: âcustom:scheduler-cardâ
include:
- switch.caldaia
time_step: 1
edit: using HA 0.117.6