That was why I suggested the Shedule. To simplify this. There is no need to make changes to the backend to edit a schedule.
Yes it would be easier with a schedule card so you did not have to use the pop-up but we don’t have one (yet).
1 Like
OK thanx Tom_I yes I tried to add the schedule to the UI but couldn’t find either a dedicated scheduler card or how to add something that would display the schedule…now seeing your example I think i know how you did that with a separate entities card. Then when you click that entity it opens the pop up.
I really don’t know why the timer and scheduling are more user friendly. As I previously said Im an amature enthusiast and have not coding or IT experience so these things are much harder to achieve without the great help and support from people like yourself. Thank you.
I would like to suggest that Frenk who created the Scheduler could consider to add the ability to use “input_values” in the scheduler template and the problem/complexity would be greatly reduced. Of course its his free time and I would not even know where to start on something like that…so I appreciate the hard work of others and try my best to learn from you guys.
Needed a restart after changing back to the schedule integration.
Yep, that’s what I said way back up there 
That negates the whole simplicity of setting the schedule through the UI.
Easier access to the schedule in a card is all that is required.
I respectfully disagree. My UI card that I made allows times to be easily set from either a computer with keyboard or a mobile device using fingers and give a much more granular time settings. On my mobile device it is really hard to set the scheduler times as the whole table moves while trying to click and crag using my finger.
But I also appreciate that it is peoples own time that they invest in this project so anything is greatly welcomed and appreciated always.
Once again thank you for your great support and advise on what is actually possible now…still wish I could understand why my original choose options that have a filter for the actual day of the week kept passing another days information.
Thanx again Tom_I,
This is my current best case set up thanx to your help:
And if its worth anything here is my Automation, I duplicated the same automation 7x for each day of the week just to keep the automation coding to a reasonable length:
alias: Central Heating Schedule - Mondays
description: Central Heating Schedule
trigger:
- platform: state
entity_id:
- schedule.central_heating_2
attribute: next_event
condition: []
action:
- choose:
- conditions: []
sequence:
- choose:
- conditions:
- condition: state
entity_id: input_boolean.downstairs_heating_mon
state: "on"
- condition: state
entity_id: schedule.central_heating_2
state: "on"
sequence:
- device_id: 318e6c3855b310c8162ca1c1e7625cb0
domain: climate
entity_id: climate.downstairs_heating_local
type: set_hvac_mode
hvac_mode: heat
- choose:
- conditions:
- condition: state
entity_id: input_boolean.kitchen_ufh_mon
state: "on"
- condition: state
entity_id: schedule.central_heating_2
state: "on"
sequence:
- device_id: cbf47d57c0cc6ef49d19936c65d0e240
domain: climate
entity_id: climate.kitchen_ufh_local
type: set_hvac_mode
hvac_mode: heat
- choose:
- conditions:
- condition: state
entity_id: input_boolean.upstairs_heating_mon
state: "on"
- condition: state
entity_id: schedule.central_heating_2
state: "on"
sequence:
- device_id: a99bcd187d587a5d620276ccecb27823
domain: climate
entity_id: climate.upstairs_heating_local
type: set_hvac_mode
hvac_mode: heat
- wait_for_trigger:
- platform: state
entity_id:
- schedule.central_heating_2
to: "off"
- condition: time
weekday:
- mon
- device_id: 318e6c3855b310c8162ca1c1e7625cb0
domain: climate
entity_id: climate.downstairs_heating_local
type: set_hvac_mode
hvac_mode: "off"
- device_id: cbf47d57c0cc6ef49d19936c65d0e240
domain: climate
entity_id: climate.kitchen_ufh_local
type: set_hvac_mode
hvac_mode: "off"
- device_id: a99bcd187d587a5d620276ccecb27823
domain: climate
entity_id: climate.upstairs_heating_local
type: set_hvac_mode
hvac_mode: "off"
trace:
stored_traces: 10
mode: single
For me it would be fantastic if someone in the know-how made a proper scheduling UI card and if there was a way to disply the current day timer setings on the above UI that I made. All of that could be achived if the schedule integratino would accept “input_datetime” from a helper.
How would I be able to pull the schedules next event and display in a UI card? I see that the schedule has attributes of next event:
EDIT: found this: state: {{ state_attr('schedule.central_heating_2','next_event') }}
Just need to research time formatting…
Use an entities card. It supports displaying attributes.
There are examples at the bottom of the page.
1 Like
Thanx once again Tom_I,
I got to this stage. now trying to find if I can format the time to a shorter version so it can be seen on the Entities card on mobile and tablets:
I tried the format command but doesnt seem to work:
tried this:
Entities card. Not entity card.
1 Like
aaahhhh the little things in life! Thank you for spotting my mistake.
type: entities
title: Heating Schedule & Next
entities:
- type: divider
- type: attribute
entity: schedule.central_heating_2
attribute: next_event
format: time
state_color: true
1 Like
Tom_l, thank you for all the insight!! I have a couple questions about your card setup. Do you have buttons in the header and footer to create the setup shown in the screenshot? How did you get the buttons you have to look that way (ie. The temp bar instead of a number)? Did your thermostat come with the entities of “heat set” and “cool set” as part of its integration or did you manually add those entities?
Background: I have a Honeywell T9 thermostat that I just purchased and am trying to automate night vs day temperatures.
The temperature bar is this custom card: Lovelace: Bar Card
The heat set and cool set are just input number helpers I use when automating my thermostat.
How do I tie the schedule helper to the entity I want to control from the entities card? For instance, the T9 thermostat or maybe a light I want to control on a schedule?
With an automation.
trigger:
- platform: state
entity_id: schedule.whatever
to: 'on'
action:
(do your thing here)
1 Like
This was all a HUGE help!! Thank you!
Hi tom_I
How did you get the temperature bar corners radius? I couldn’t find any examples and card radius seems to be for the outed card corners…
Please can anyone in the know about template icons help me with this. can I add yaml to the UI card to give animated icons for on and off?
type: entities
title: Heating Schedule
entities:
- entity: schedule.central_heating_2
name: Central Heating status
icon: blank
- type: attribute
entity: schedule.central_heating_2
name: Next Event (On/Off)
attribute: next_event
format: time
- entity: input_boolean.heating_schedule_off_on
icon_template: >
{% if is_state('input_boolean.heating_schedule_off_on', 'on') -%}
mdi:timer-outline
{%- elif is_state('input_boolean.heating_schedule_off_on', 'off') -%}
mdi:timer-off-outline
{%- endif %}
state_color: true
This is what I added to the Card editor but needless to say that it doesn’t work to change the icons for on and off
You can’t just go adding whatever options you want. Look at the supported options in the docs. That’s it. And most core cards do not support templates. If you search for “Lovelace templates” you will find a third party solution.
1 Like
The scheduler is working perfectly for my Thermostat AND my office lamp. For my thermostat (someone can let me know if there is a more organized way) I created a schedule for ‘daytime’ and a schedule for ‘nighttime’ and I simply told my automation that when the ‘daytime’ schedule turns ‘on’ to set the high and low temperatures where I want (as I input in the action) and then I did the exact same thing with the ‘nighttime’. It is working great!!