Maybe related: https://github.com/nielsfaber/scheduler-card#my-climate-entity-does-not-work-when-i-create-a-schedule-to-change-the-temperature
Thanks I saw that part but really thought that the generic_thermostat wasnāt part of those ādevicesā that could not be working due to it being a base component of HA 
I implemented that piece of code, and it does exactly what the component is already doing, changing the temperature but not switching the hvac to āheatā.
I could still try to create an automation that would switch the heater on if it detects a change in set_tempā¦
Actually @KTibow is right and thereās a bug in the generic thermostat.
Please follow his link and try again.
I will see if I can make a better solution (because youāre not the first with this issue).
1 Like
Ok I just modified the code and will report back in 2 minutes if the heating switched on !
Thanks to both of you !
EDIT : it didnāt 
But the set_temperature changed.
I donāt see what would change hvac_mode to āheatā in the piece of code KTibow references ?
Ok there is definitely a bug in the implementation of the climate.set_temperature in the generic_thermostat.
You cannot change the property of hvac_mode through this service
Iāll try to use a script with the scheduler to set temp and hvac_mode to āheatā through the climate.set_hvac_mode service which is working
Thank you 
Hello.
Is there someone who can share his custom code of Scheduler Card ?
Itās to see how to add the customize section.
Read the docs
I read it but it will be really helpfull for me. I need some clues to understand what to write and how. Iām not a YAML coder.
I just want to say: Are you sure you need to customize it? The GUI should be just fine, and you should really learn some basic coding and YAML understanding if you want to customize HA, or anything in it without a GUI. Anyway, not trying to be mean to you, just saying. Also try reading the last 25 replies.
Sorry, i misunderstood.
Yes i want to customize because i want to show the friendlyname on my card.
i know that i need to learn YAML coding and i first understood the big importance of indent for example.
I succeeded customizing HA with different sample provided and with succession of testing - correcting - testing - correcting ā¦
This might help you:
(I think they forgot to change the description, Linux doesnāt use YAML)
Ok, Iāve made a copy of the generic_thermostat as a custom_components and added the necessary bits in its code to handle setting the hvac_mode with the set_temperature service and guess what, your component works perfectly 
Iāll see if I can open a PR on HA Github but itās been a while since Iāve used itā¦
Thank you again for your component, itās beautiful.
3 Likes
One day on HA and you already joined the dark side 
I like your guts!
Would be great if you can take initiative to have it fixed, because a lot of people blame the scheduler for implementing things correctly. 
Glad you like it!
Donāt be scared of YAML 
Check my post here and the docs.
Its really a matter of copy-pasting.
Just try and see the result.
I have a different genetic_thermostat setup:
- platform: generic_thermostat
name: Salon
heater: switch.podlogowka_salon
target_sensor: sensor.temperatura_salon
hot_tolerance: 0
min_cycle_duration:
seconds: 30
I didnāt test the scheduler integration yet, Iām in process of setting up a test environment right now.
@snoopy1492 why do you need initial_hvac_mode? In my case, the generic thermostat works perfectly. Currently, Iām using automation, but I want to replace all of them with scheduler integration and card.
btw do you have your modification available online?
Iād like to check them in my setup
Iām using initial_hvac_mode set to āoffā to be sure that at startup no heating is done until an automation or schedule asks for it.
Iāve had different experiences with other automation software and I prefer to be cautious as I donāt want my house to be heated for days without no reason just because the mains went out and a bug occurred and none of my automations started
That way Iām sure that the default is āno heatā.
As for the modification I made, the schedule component uses the climate.set_temperature service to set the temperature AND switch between the different hvac mode (mainly on or off for the generic_thermostat).
This is one of the service available in the climate integration per HA documentation (Climate - Home Assistant).
Unfortunately the generic_thermostat platform doesnāt implement this functionnality. With the climate.set_temperature, you can only set the temperature.
The scheduler component then cannot switch the heat on or off on a generic_thermostat. It can only change the target temperature.
So if your thermostat is off (and I mean switched off, not just not heating due to the temp not requiring it), the scheduler will just adjust the temp but the thermostat will stay off and wonāt heat.
What Iāve done is change the function in the generic_thermostat code so you can pass two arguments to the set_temperature function, the target temperature and the hvac mode as per the documentation.
And now everything works.
Iām in the process of installing everything to be able to submit my PR to HA Github. Iāll also make my custom_component available in case someone wants it.
Iām sure there is a discussion around the generic_thermostat available here, we should go there if we want to continue
3 Likes
@snoopy1492 your case is a good example. Thank you for your explanation 
Sorry for a non-scheduler related question.
Letās focus in this thread on the scheduler only.
Hello
Right now itās 5.15 PM and the next action is scheduled at 6.30 PM and the scheduler card shows āand 15 minutesā
Do you know what to change ?
Thanks
I will make a fix for that.
Itās actually due to broken translations. But that doesnāt make it less bad
Actually: which version of the card are you running? and which language?
Because for me it shows fine for English.
version 1.9.3
language english UK
and settings
type: 'custom:scheduler-card'
title: Chauffage
standard_configuration: true
include:
- climate
time_step: 1
display_options:
primary_info: '{entity}: {action}'
secondary_info:
- relative-time
icon: entity
thanks for your help
@Merangle I just created a new release v1.9.4 with a ācreativeā workaround for this.
I hope it improves things for you.
There are still some glitches sometimes with loading translations from the frontend.
Ever since they introduced lazy-loading, depedencies are very unreliable.
Unfortunately, missing translation will just result in disappearing wordsā¦
There is no fallback to english or whatsoever.
@Canaletto Since you addressed the same problem, maybe updating would help you as well.
However, i see that still the french translation is not fixed. The relative time might show up in english instead of french (if the time is <6 hrs from now).
1 Like