Hello everybody. I have installed this card and it works like a charm. I am only struggeling with setting up the temperatures in shedules. The Slider is handy but my finger too fat for setting up a proper temperature. I wonder if its possilble to have integer values only. I would even reduce those to a range from 10 - 25°C.
I am sure thats setable somewhere, does anyone have an idea where?
Thanks very much!
I am new but i read the documentation and there is an option in the settings of the card called TAGS, once you have seletected the entities and you have then chosen the Tab OTHER on the top
Now scroll down to the end and the last option seems to describe
“Use tags to divide schedules between multiple cards”
So I guess you have your first card wit a tag called
uneven (for week 1 3 5 …) and
second card withh tag
even (for week 2 4 6 …)
You can also find tags: in yaml here for example THERMOSTATE
BUT be aware that I had to remove FIRST my old schedules cause it seems you can not update these older schedules.
So start with a new dashboard and a test device.
Add the first card and add the bare minium like entity but also tag 1 and so on.
Then copy the yaml code and create a second one as a copy but change the tag to 2
Now you can start adding schedules and those will not appear on the other card and vice versa.
FOUND IT:
If you want to use multiple scheduler-cards in your Lovelace dashboard, it can be difficult to separate the schedules which show up in each card (with include you can only control which entities are controlled by which cards). With tags you can filter out schedules and assign them to their own cards.
To start using tags, edit the card configuration and assign tags to the scheduler card.
Example:
type: custom:scheduler-card #…rest of card configuration tags: holiday
The effect of assigning tags:
discover_existing is set to true.Notes:
tags: none to a card if you want to have only schedules without a tag showing up here.tags: enabled or tags: disabled to a card if you want to include (respectively) all enabled or disabled schedules.tags option set.
Tip: If you want to start using tags you will have to go through your current schedules and assign them with tags. You can temporarily set discover_existing: true to make also schedules accessible which don’t have the correct tag (yet). You can also make the tags for schedules show up in the overview through display_options.
Example usage:
Consider the following situation:
Since both cards have the light domain included, the created schedules would normally show up in both cards, which is not desirable.
Now by assigning tags to the card configurations, you can filter them.
Config for card A:
type: custom:scheduler-card title: Normal schedule #…rest of card configuration tags: none
Config for card B:
type: custom:scheduler-card title: Holiday schedule #…rest of card configuration tags: holiday
Same is issue here and I have opened can issue on github too.
All attempts failed so far.
It is terrible cause I always have this orphand in the existing card.
If I want to use the entity I can even create a new card but in the second where I choose incluse this sensor the crap comes back again.
I have deactivated the integration
switched to developer tools
marked the entity schedule_as and delted that.
Vanished
but the moment I had activated the integrtion again the crap turned up again.
My only and last hope right now is to find the way how to delete entities on the native file level somewhere burried deep below in the file system which had workd for me before
OR
to delete the mother entity or device called climat 7 and later add the device again in the hope the unique id of the device would change too.
The broken entity has become a real issue.
The only solution I have found so far is a simple , but terrible one.
complete uninstall of the scheduler backend which then will delete all schedules
reinstall the back end component
you might have to adjust the scheduler card also
finally you need to create all the schedules again.
Therefore I suggest a kind of backup that should do the trick for you cause it took quite a long time till I got what I have had already before.
UPDATE: there are a lot of an ACTION under developer tools - action tab belonging to the scheduler and one of them is called SCHEDULE REMOVE which means deleting the entity
Sorry, but that does not really answers my question to a really simple problem: I want to control the entity that is used to evaluate if it is workday or weekend.
If I click on, this should be active on weekday (werktags), how does it know that?
How can i limit the settings for a new schedule on a thermost to
automatic and the heating option activated only,
I want to hide “ausschalten / turn off” and “heizen- kühlen / heating - cooling”
and then if I press automatic I want to have set the temperature option settings on to only have to adjust the temperature.
I know it must have to do with the customize sections but my first attempt here did not work out
customize:
climate.thermostat_1_kaminzimmer:
name: KAMINZIMMER
icon: thermometer
actions:
- service: set_hvac_mode
name: Set mode
icon: hass:settings
variables:
hvac_mode:
name: Operation mode
options:
- value: heat
icon: hass:fire
any suggestions.
You have made the decision for workday and the home assistant server has its own calendar, so it knows if it is a day on the weekend or not. If not it is a weekday.
You sound like you have a german assumption of workday cause I bet you are thinking about the issue of a holiday on a workday, which usually means to be treated like a sunday, right ?
You have the choice between
and you have chosen werktags aka all the days that are not weekend.
Monday till Friday are Werktage and so it can run the schedule easily.
If you are look for a sophisticated version with german public holidays treated like a weekend or sunday you will not get that - not for germany nor for the states level usually needed in germany like public holidays for bavaria with all the specialities like Nuremberg / Nürnberg.
I guess developers will go crazy with german kind of national and state wide public holidays.
But you might open a feature request and wait for a reply - cause it would have an impact for every user and every country cause that would require a country selection and state selection which has impact on the already crowded UI most likely for everyone. You will need a selection for Germany and then for the state like Bavaria cause some countries will get along with a country alone while germans would wanna have state based list of holidays.
It is possible but I assume a lot of work to handle a public holidays in your state like weekend day, so open a request cause I have not found the word holiday once.
Maybe there is a kind of improvisation in the yaml file possible, where you can enter a list of dates and all those dates are treated like a Sunday / Weekend.
I doubt that they will expand the crowded UI for that cause it will become a mess I guess unless they would be able to open a new window for holidays on top.
I took a look at the source code and it says exactly what I thought it would.
Yes, that’s exactly what I get when I install the Workday integration. If there is a public holiday in my state, in my country, it is treated as a weekend and therefore the weekend schedule is executed.
__Workdays__
perform action only on Monday thru Friday.
If you have the [workday integration](https://www.home-assistant.io/integrations/workday/) installed, you can use it to define your own set of workdays.
The workday integration and its settings will be automatically detected if it is installed.
Note that if you define holidays, they will be excluded from workdays.
__Weekend__
perform action only on Saturday and Sunday.
If you have the workday integration installed, the weekend will be considered as the inverse as workdays. This means that holidays and your 'fixed day off' are included in the weekend setting.
Now I just have to find a way to address my own Workday sensor.
I have added this workday HA integration and made a screenshot of the setup which explains all the implications .
The key setup for germans are located in the lower half which means to ignore the manual public holiday setup cause below you will find the area for country = germany and state = bavaria
But as you said I have not found the connection inside the scheduler component where to tell the scheduler component that I have installed WORKDAYS integration and the name of my sensor which is managing my workdays.
I have searched through the component, but not the card itself how to set it up properly.
You can find the word workday in the code but no explanations how and if that can be used as I had said yesterday that it is not part of this solution so far.
But I will try to find the connection.
UPDATE 1:
Yesterday I had searched for public holidays and therefore did not find anything how to set those up and connect those.
Today I searched for work days and the most details I could find are mentioned here regarding the workday sensor
and then
… want , is by defining some input_boolean entity which represents whether “today is a workday”. You could create some automation that automatically enables it from Mon-Fri, which you could override manually. However you would need to set all schedules to “daily” and define the condition “input_boolean.workday is ON” or “input_boolean.workday is OFF” for your workday / weekend schedules respectively.
It is part of yaml only but not described how to achieve that. There were some other hints but more in general like a workday that is a holiday will be treated like a day on the weekend and then there is also a kind of holiday sensor for holidays only. But I have not found any description how to integrate both. I guess this is working out of the box unless you change the sensors title which I had done assuming that there would be a configuration inside scheduler component to define workday or rather which sensor name is delivering the workdays.
UPDATE 2:
Here is the answer regarding the sensor and its name cause jjross has not gotten a reply so I assume there is only 1 sensor based on this question
And that was a reply to jjross questions about multiple workday sensors
Therefore I assume you need to use the workday integration as it is with all default options and can not change the workday entity name.
And that might explain why you can not find more details in the scheduler card / component setup except this part
which had been added in Oct. 2020
I will have to uninstall workday integration now and then reinstall the integration with default values to get scheduler component connected with the workday connection sensor.
I want to customize my thermostate and remove the useless options here cause I want to use the thermostat to set a specific temperature and nothing else.
What does “turn off” for a thermostat mean ?
My rademacher thermostat (based on the rademacher integration) is doing nohting which would mean that the temperature would stay the same afterwards.
So I tried out what I had found with customize.
type: custom:scheduler-card
title: ""
include:
- climate.thermostat_1_kaminzimmer
time_step: 5
show_header_toggle: false
display_options:
primary_info:
- "{action}"
- "{time}"
action: null
secondary_info: []
icon: action
sort_by:
- state
- relative-time
tags:
discover_existing: false
customize:
climate.thermostat_1_kaminzimmer:
name: KAMINZIMMER
icon: thermometer
actions:
- service: set_hvac_mode
name: Set mode
icon: hass:settings
variables:
hvac_mode:
name: Operation mode
options:
- value: heat
icon: hass:fire
I had hoped to get rid of the actions “turn off” and “heating / cooling” but instead of that I got even 1 more button I did not want or at leas a half button called SET MODE but without the circle in front of that.
I simply want 1 action only - the “automatic” and the best would be if the checkbox bewlo TEMPERATURE would be turned on automatically if I have clicked on the action “automatic” cause that is necessary to move the slider.
I have found only 1 service under developer tools service / actions called climate: Set HVAC mode but no other thermostate like mode.
Any suggestions what went wrong and what to do to achieve that ?
Hi everyone!
I’m trying to rename the schedule with a more friendly name.
Can anyone help me find where to edit the settings?
thanks in advance
Ennebie,
Edit the Schedule, on the Options section the field between the date fields and above the TAGs is what you want.
If you have set it up and saved then you can change it here in NAME afterwards.
I have added “office: click to expand the scheduler” in german the highlighted “BÜRO …”
as a reminder for me and everyone using the scheduler that you get a wide window after you have clicked on the title of the window (next to the X in the upper left corner on BÜRO aka OFFICE)
You will then get the full width window and you will be able to use the full time scale from 0:00 to 23:59 which is a must have for the schedule tab as you can see here easily.
But of cause I have “abused the title for a reminder” - at least very usefull in the beginning when you set up temperature plans for each room and have to adjust cause the small windows is too small for usefull schedules.
Here is the solution or at least what has worked out for me being no professional.
To start with I have searched the whole topic here and github documentation about the issue and found these 2 sources
A general introduction how to hide unwanted actions in the release notes for Release v1.9.0 from oct. 2020.
I suggest to also read along the discussion between Motti_Bazar and neliss before this release notes, cause Motti_Bazar came up with the issue, ideas and solutions. It is good to know just to get into the topic in general.
And with that knowledge I also found a key explanation in the documentation when I searched for Motti_Bazar s solution or key word called
“exclude_actions:”
This part in the documentation is meant for a different use case where the tuya device needed a kind of special “auto mode” but it explains a lot of the details and code what I had been missing before like how to control a simple thermostat.
This code worked out for me too with Rademacher Thermostats which can only heat.
I also used the “auto mode” advised for tuya as it had worked out for me even I do not know if it would work without that - read along cause the further explanations can be found below.
As you can see above all the unnecessary options from the hvac mode have vanished when I switched to the service: set_temperature
Below you find my coade and all relevant changs have been made from
standard_configuration: false
onwards and especially in the
customize: section
ATTENTION: you would not need the exclude_actions section with the 3 elements but I let it there to have a reminder if I would need that in the future.
The service: set_temperature has removed all those unwanted actions which were part of the hvac mode with which I had started with as the only climate regulation I had been aware of back then.
The last sentence is wrong cause the hiding of all the actions I did not want was caused by
service_data:
hvac_mode: auto
If you would turn the last line to “hvac_mode: heat” which sounds or feels quite logic and good then you would get all actions and controls back which I did not want.
set_temperature is also far more usefull at least for me like setting the
That makes the scheduler faster to adjust and use. Thermostats only work if the oil condensed heater is on so if that is turned off I do not have to care about temperature around 4°C oder 8°C. If it is on the thermostats should keep the temperature above 12°C as the lowest possible temperature. I also avoid that other users can accidantly change such temperature too low and that happens most likely for a room rarely used and you would not get behind that.
type: custom:scheduler-card
title: ""
include:
- climate.thermostat_1_kaminzimmer
time_step: 5
show_header_toggle: false
display_options:
primary_info:
- "{action}"
- "{time}"
action: null
secondary_info: []
icon: action
sort_by:
- state
- relative-time
tags:
- THERMOSTATE
discover_existing: false
standard_configuration: false
customize:
climate.thermostat_1_kaminzimmer
exclude_actions:
- heat # hide the built-in action to avoid duplicates
- set mode # we won't use this
- set preset # we won't use this
actions: # add the custom actions
- service: set_temperature
service_data:
hvac_mode: auto # do not use heat cause all actions and controls woudl reappear
variables:
temperature:
min: 12
max: 24
step: 1.0 # 0.5 is possible too
unit: '°C'
icon: 'hass:fire'
name: "heat[ to {temperature}]" # replace with local translation for 'heat' and 'to' if desired
FINAL REMARKS:
You are adding a customized solution as the title “customize:” is telling you.
Therefore you need to take care for the translation yourself
“Heat” will be displayed as HEAT action and also in the schedule UI as “heat to 24°C” unless you replace that with your translation like here the German one with “Heizen” and “auf” instead of “heat to” - but do not translate temperature cause that is a variable which has to stay representing the target temperature like “heat to 23 °C”
icon: 'hass:fire'
name: "Heizen[ auf {temperature}]" # replace with local translation for 'heat' and 'to' if desired
So far this works really great now.
No unwanted actions distracting us anymore and no more unnecessary “click the check box” needed to simply adjust the temperature.
Quite happy that it is working now.