@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).
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
@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
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…
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.
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
schedule entity is always in “waiting”. i have to add something to add more debug log? i cannot see anything strange in the log. how can i check if component is up and running?
I know how to access ha logs. But there are no exception error or warning regarding schedule-component. This Is why i asked if there was possible to have more debug log or some other way to check if component Is running…
