Amazing progress! This new time schedule is exactly what I was looking for!
I have a couple of doubts/suggestions.
Also maybe a bug? Or a misconfig from my side? This used to work though.
cards:
- type: custom:scheduler-card
standard_configuration: False
include:
- input_number.tariff
customize:
input_number.tariff:
actions:
- service: input_number.set_value
service_data:
state: 0.13
# state: {{input_number.peak_tariff_utility}}
name: "Peak"
- service: input_number.set_value
service_data:
state: 0.04
# state: {{input_number.partial_peak_tariff_utility}}
name: "Partial Peak"
- service: input_number.set_value
service_data:
state: 0.01
# state: {{input_number.off_peak_tariff_utility}}
name: "Off Peak"
No error per se in the debug logs, just debug level messages:
2020-10-02 11:34:24 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new switch.scheduler entity: switch.schedule_609bf9
2020-10-02 11:34:24 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event entity_registry_updated[L]: action=create, entity_id=switch.schedule_609bf9>
2020-10-02 11:34:24 DEBUG (MainThread) [custom_components.scheduler.switch] executing service input_number.set_value
2020-10-02 11:34:24 DEBUG (MainThread) [homeassistant.core] Invalid data for service call input_number.set_value: {'state': 0.04, 'entity_id': ['input_number.tariff']}
The new scheduler entity is not saved.
Not the fault of scheduler-component. Change state to value to fix.
Here is your fault:
standard_configuration: False
It should be replaced with:
standard_configuration: True
Or even:
@neliss can you comment on this one please? It is flooding the HA logs and the debug logs in the browser. I had to completely remove the card to stop it. (I don’t know if it only logged this continuously when I tried to change the time, or all the time while the card was added)
TouchInput constructor is only defined in Firefox if you are using a touchscreen?
Maybe use PointerInput which is said to be working with touch AND mouse too.
Any bugs with me just replacing all occurrences in a PR?
The touch events are used for supporting mobile devices. With only listening for mouse events the dragging does not work on a phone.
I did not test with Firefox specifically. But in chrome and safari (windows/android/iOS) all works OK for me.
I could try to see if I could catch the errors you are seeing. But I’m not sure if I can reproduce them here.
For me it’s fine if you remove the card (or avoid using it with Firefox) in the meantime.
Its a work in progress, so your experience is useful feedback.
Can you open an issue on GitHub for follow-up on this? Also provide details for reproducing and error logs if you can.
@LeadUr Never mind the Github issue, I made a v1.7.1 release which should fix your problem.
I installed Firefox to test and had the same problem.
But the errors only occur when you start dragging, so I don’t really get what the fuss was all about.
It remains an experimental feature, hence the big disclaimer on the page 
The new scheme option is fantastic! One thing to note with the update: language is not correct. It’s a mix of Dutch and English right now. Not a huge issue, so I understand if you work on that once the new scheme option is final. But wanted to let you know.
Hey!
Thanks! It wasn’t a fuss. I just checked the HA logs and saw the TON of errors I showed to you. (Ton meaning hundreds of lines)
I really wanted to try out this feature (since I was the first one mentioning that a schedule is needed to fire even if HA is restarted or it is turned on and the time already passed).
It is indeed working now for me in Firefox! Thanks again!
Now the only question remains is how @KTibow was able to modify the time on the Time Scheme in Firefox if it really needed a fix, and was not working for you either?
@KTibow did you try this on a device which has touch input?
I am very much aware of the mess that you will get with long list of schedules.
Currently I am a bit struggling with a good solution for this.
The problem is:
I don’t have any problem with adding all of these features (in fact: the scheduler_component already supports it), but I want the card to remain easy to use.
You are proposing to group the overview by entities. Which I think, is an excellent idea 
The problem is: what if schedules contain multiple entities?
Would you like to see these schedule being ‘ripped apart’ and listed multiple times, with a duplicate for each entity?
Or would you bundle these entities in the overview as a single group?
Or something else?
I could really use some ideas here 
Yeah I know. Translations are getting a bit messy.
The real problem is that drastic changes are needed.
In English you would say: ‘On Wednesday’ and ‘Every day’ (or ‘Daily’), but ‘In the weekend’.
And ‘at 12:00’ or ‘from 12:00 to 16:00’ .
But some languages work completely different. In Spanish for example: ‘a las 12:00’ but ‘a la 01:00’ , and also female/male differences in some words.
I really don’t know how to make this universal.
Plenty of work for improvement here
Hope it doesn’t bother too much.
I personally don’t think you should add too many features like this, because the card can get too bloated, confusing and hard to manage. Having ‘one card to do all’ is not something maintainable. Also, where does it stop. Next thing you now, it’s an automation wizard and defeats the purpose: fast and easy way to setup simple schedules. There are other cards people can use in conjunction with this card to sort stuff, like swiper card and state-switch.
You have added the feature to create separate schedular cards already. This should be enough honestly, because now people can use your card inside other cards to manage their schedules. But people need to get creative and use the possibilities that lay in front of them.
For instance: you want separate schedules for each room or entity type? Simple: use state-switch card and button-card and setup multiple schedule cards inside. Then just switch between schedules with an icon.
No work needs to be done by you for this and people can get creative and use a kinda of solutions.
I’ll create a short example of what I mean later today, to give a practical example.
No problem
Well, I think you will get disappointed honestly.
I am noticing that at HA startup it is really unpredictable in which order devices are waking up.
It’s not that easy to make the scheduler wait until HA is fully started and all devices are operational, since the ‘home assistant started’ event is fired way before that.
I am noticing this already with native HA integrations, including the weekday sensor, but also MQTT devices.
Also listening for state changes in devices doesn’t really work, because the unavailable->available transition does not seem to fire any event in HA. At least not at startup.
This is a work in progress, because I agree with you that it I really important that you can rely on the time slots doing what they should do.
Yeah… HA always have had these problems with startup unfortunately.
For me, it would be a good enough implementation if you just do something like this when you try to run the action of a schedule:
multiplier = 1
action_confirmed = false
while (multiplier < 5 and !action_confirmed) do
{
do action
action_confirmed = get confirmation of the action (like: is the temperature really set?)
if (!action_confirmed)
wait 10 * multiplier
multiplier++
}
if (!action_confirmed)
show a warning, or send notification to let the user know, that you could not do the action for some reason.
Of course this is just an example. What I’m saying is it does not have to be perfect. It just have to be good enough
That is the most beautiful piece of python I have ever seen! 
But I get the point, exponential backoff could be a good way.
I was hoping to be able to just register a callback for when the device comes back alive, rather then polling it.
But documentation of the HA functions is really poor, don’t know yet if this is doable…
Hello, just say that is a great work with the last update.
If i can just have a suggestion, it would be to collapse the schedule in order to have a compact view.
Replying to my own message for an update:
This is what I meant. Using button-card and state-switch in conjunction with schedular-card.
Ofcourse this is just an example, but this gives an idea why it’s unnessecary for schedular-card to have this built in and become too bloated. There are already other ways to organize this since schedular-card has the discover_existing variable. Swiper card is also a nice solution instead of state-switch
If people are interested how to recreate this, code below. Ofcourse don’t copy/paste since I use my own stylings and entities. But it’s very simple if you take the time to understand how state-switch works (which is simple to use).
type: 'custom:state-switch'
entity: hash
default: scheduler_woonkamer
states:
scheduler_woonkamer:
cards:
- cards:
- deep_press: true
layout: icon_name
name: Woonkamer
aspect_ratio: 2.5/1
show_icon: true
icon: 'mdi:sofa'
show_label: false
show_name: true
styles:
card:
- background-color: var(--card-background-switch)
icon:
- color: var(--switch-entity-color)
label:
- color: var(--button-text-color)
name:
- color: var(--button-text-color)
- font-weight: bold
- font-size: 12px
tap_action:
action: navigate
navigation_path: '#scheduler_woonkamer'
haptic: medium
type: 'custom:button-card'
- deep_press: true
layout: icon_name
hold_action:
action: more-info
haptic: heavy
name: Keuken
aspect_ratio: 2.5/1
icon: 'mdi:stove'
show_icon: true
show_label: false
show_name: true
styles:
name:
- font-weight: bold
- font-size: 12px
tap_action:
action: navigate
navigation_path: '#scheduler_keuken'
haptic: medium
type: 'custom:button-card'
- deep_press: true
layout: icon_name
hold_action:
action: more-info
haptic: heavy
name: Slaapkamer
aspect_ratio: 2.5/1
icon: 'mdi:bed'
show_icon: true
show_label: false
show_name: true
styles:
name:
- font-weight: bold
- font-size: 12px
tap_action:
action: navigate
navigation_path: '#scheduler_slaapkamer'
haptic: medium
type: 'custom:button-card'
type: horizontal-stack
- title: false
discover_existing: false
time_step: 5
standard_configuration: true
groups:
- name: Schakelaars
icon: hexagon-multiple
include:
- switch
exclude:
- switch.ryzen*
- name: Verlichting
icon: lightbulb
include:
- light.woonkamer_*
- name: Entertainment
icon: youtube-tv
include:
- media_player.tv
- media_player.playstation_4_pro
- switch.ryzen
- name: Scènes
icon: auto-fix
include:
- input_boolean.moviemode
- input_boolean.gamemodus
- input_boolean.muziek_scene
include:
- light.woonkamer_*
- input_boolean.moviemode
- input_boolean.gamemodus
- input_boolean.muziek_scene
- media_player.tv
- media_player.playstation_4_pro
- switch
exclude:
- switch.*_bluetooth
customize:
light.woonkamer_plafond:
name: Woonkamer Plafond
light.badkamer_plafond:
name: Badkamer Plafond
type: 'custom:scheduler-card'
type: vertical-stack
scheduler_keuken:
cards:
- cards:
- deep_press: true
layout: icon_name
name: Woonkamer
aspect_ratio: 2.5/1
show_icon: true
icon: 'mdi:sofa'
show_label: false
show_name: true
styles:
name:
- font-weight: bold
- font-size: 12px
tap_action:
action: navigate
navigation_path: '#scheduler_woonkamer'
haptic: medium
type: 'custom:button-card'
- deep_press: true
layout: icon_name
hold_action:
action: more-info
haptic: heavy
name: Keuken
aspect_ratio: 2.5/1
icon: 'mdi:stove'
show_icon: true
show_label: false
show_name: true
styles:
card:
- background-color: var(--card-background-switch)
icon:
- color: var(--switch-entity-color)
label:
- color: var(--button-text-color)
name:
- color: var(--button-text-color)
- font-weight: bold
- font-size: 12px
tap_action:
action: navigate
navigation_path: '#scheduler_keuken'
haptic: medium
type: 'custom:button-card'
- deep_press: true
layout: icon_name
hold_action:
action: more-info
haptic: heavy
name: Slaapkamer
aspect_ratio: 2.5/1
icon: 'mdi:bed'
show_icon: true
show_label: false
show_name: true
styles:
name:
- font-weight: bold
- font-size: 12px
tap_action:
action: navigate
navigation_path: '#scheduler_slaapkamer'
haptic: medium
type: 'custom:button-card'
type: horizontal-stack
- title: false
discover_existing: false
time_step: 5
standard_configuration: true
groups:
- name: Verlichting
icon: lightbulb
include:
- light.kitchen_bulb
- light.small_bulb
- name: Scènes
icon: auto-fix
include:
- input_boolean.dinermode
include:
- light.kitchen_bulb
- light.small_bulb
- input_boolean.dinermode
exclude:
- switch.*_bluetooth
customize:
light.woonkamer_plafond:
name: Woonkamer Plafond
light.badkamer_plafond:
name: Badkamer Plafond
type: 'custom:scheduler-card'
type: vertical-stack
scheduler_slaapkamer:
cards:
- cards:
- deep_press: true
layout: icon_name
name: Woonkamer
aspect_ratio: 2.5/1
show_icon: true
icon: 'mdi:sofa'
show_label: false
show_name: true
styles:
name:
- font-weight: bold
- font-size: 12px
tap_action:
action: navigate
navigation_path: '#scheduler_woonkamer'
haptic: medium
type: 'custom:button-card'
- deep_press: true
layout: icon_name
hold_action:
action: more-info
haptic: heavy
name: Keuken
aspect_ratio: 2.5/1
icon: 'mdi:stove'
show_icon: true
show_label: false
show_name: true
styles:
name:
- font-weight: bold
- font-size: 12px
tap_action:
action: navigate
navigation_path: '#scheduler_keuken'
haptic: medium
type: 'custom:button-card'
- deep_press: true
layout: icon_name
hold_action:
action: more-info
haptic: heavy
name: Slaapkamer
aspect_ratio: 2.5/1
icon: 'mdi:bed'
show_icon: true
show_label: false
show_name: true
styles:
card:
- background-color: var(--card-background-switch)
icon:
- color: var(--switch-entity-color)
label:
- color: var(--button-text-color)
name:
- color: var(--button-text-color)
- font-weight: bold
- font-size: 12px
tap_action:
action: navigate
navigation_path: '#scheduler_slaapkamer'
haptic: medium
type: 'custom:button-card'
type: horizontal-stack
- title: false
discover_existing: false
time_step: 5
standard_configuration: true
groups:
- name: Verlichting
icon: lightbulb
include:
- light.c1
- light.c2
- name: Scènes
icon: auto-fix
include:
- input_boolean.slaaproutine
- input_boolean.wakemode
include:
- light.c1
- light.c2
- input_boolean.slaaproutine
- input_boolean.wakemode
exclude:
- switch.*_bluetooth
customize:
light.c1:
name: Nachtkast
light.c2:
name: Plafond
type: 'custom:scheduler-card'
type: vertical-stack
Edit: here’s an example with swipe card.
Code:
type: 'custom:swipe-card'
style: |
:host {
background: none !important;
}
parameters:
spaceBetween: 20
pagination:
type: bullets
cards:
- cards:
- content: |
# Woonkamer
style:
.: |
ha-card {
height: 30px;
--ha-card-background: none !important;
box-shadow: none !important;
}
ha-markdown:
$: |
h1 {
font-size: 20px;
font-weight: bold;
font-family: Helvetica;
letter-spacing: '-0.01em';
}
type: markdown
- title: false
discover_existing: false
time_step: 5
standard_configuration: true
groups:
- name: Schakelaars
icon: hexagon-multiple
include:
- switch
exclude:
- switch.ryzen*
- name: Verlichting
icon: lightbulb
include:
- light.woonkamer_*
- name: Entertainment
icon: youtube-tv
include:
- media_player.tv
- media_player.playstation_4_pro
- switch.ryzen
- name: Scènes
icon: auto-fix
include:
- input_boolean.moviemode
- input_boolean.gamemodus
- input_boolean.muziek_scene
include:
- light.woonkamer_*
- input_boolean.moviemode
- input_boolean.gamemodus
- input_boolean.muziek_scene
- media_player.tv
- media_player.playstation_4_pro
- switch
exclude:
- switch.*_bluetooth
customize:
light.woonkamer_plafond:
name: Woonkamer Plafond
light.badkamer_plafond:
name: Badkamer Plafond
type: 'custom:scheduler-card'
type: vertical-stack
- cards:
- content: |
# Keuken
style:
.: |
ha-card {
height: 30px;
--ha-card-background: none !important;
box-shadow: none !important;
}
ha-markdown:
$: |
h1 {
font-size: 20px;
font-weight: bold;
font-family: Helvetica;
letter-spacing: '-0.01em';
}
type: markdown
- title: false
discover_existing: false
time_step: 5
standard_configuration: true
groups:
- name: Verlichting
icon: lightbulb
include:
- light.kitchen_bulb
- light.small_bulb
- name: Scènes
icon: auto-fix
include:
- input_boolean.dinermode
include:
- light.kitchen_bulb
- light.small_bulb
- input_boolean.dinermode
exclude:
- switch.*_bluetooth
customize:
light.woonkamer_plafond:
name: Woonkamer Plafond
light.badkamer_plafond:
name: Badkamer Plafond
type: 'custom:scheduler-card'
type: vertical-stack
- cards:
- content: |
# Slaapkamer
style:
.: |
ha-card {
height: 30px;
--ha-card-background: none !important;
box-shadow: none !important;
}
ha-markdown:
$: |
h1 {
font-size: 20px;
font-weight: bold;
font-family: Helvetica;
letter-spacing: '-0.01em';
}
type: markdown
- title: false
discover_existing: false
time_step: 5
standard_configuration: true
groups:
- name: Verlichting
icon: lightbulb
include:
- light.c1
- light.c2
- name: Scènes
icon: auto-fix
include:
- input_boolean.slaaproutine
- input_boolean.wakemode
include:
- light.c1
- light.c2
- input_boolean.slaaproutine
- input_boolean.wakemode
exclude:
- switch.*_bluetooth
customize:
light.c1:
name: Nachtkast
light.c2:
name: Plafond
type: 'custom:scheduler-card'
type: vertical-stack
One thing to keep in mind with swipe card: using sliders withing swipe card doesn’t work nice (since you are moving a slider and the swipe card itself). But you can also just press spots inside a slider (like I did in the video).
I was busy sleeping… Yes, I was testing on a Microsoft Surface with an external display, mouse, and keyboard hooked up.
Ahh… that’s the solution then. The former implementation was working with Touch Interfaces on Firefox, but not where Touch input is non-existent. Although it is already fixed, so everything is in order