I’m in no position to criticise use of LLMs for programming as one wrote most of this project! I am a professional software engineer but just didn’t have time to learn the ins and outs of HA, I at least know what questions to ask. 
I’m about to release this version to production, it has a bunch of optimisations for card registration so hopefully will fix most of these issues.
v1.14.7 released and available in HACS, loads of fixes and updates in this one and I think the cache busting is finally working…
switch.schedule_<name>_<token> entitynext_trigger, next_slot, actions, and next_entriesclimate-scheduler-card.js and panel.jsclimate_scheduler.reload_integration (unchanged)switch.schedule_<name>_<token>)_compute_schedule_attributes() to derive entity from group name when missingclimate_scheduler_node_activated events now only trigger when node time changes (scheduled transition)setPreviousDayLastTemp() method to graph.js for cross-day continuitydatetime.now() calls with dt_util.now() in coordinator.py (11 instances)climate_scheduler_node_activated events fired by coordinator and the test events button didn’t match. entity_id is used if there’s a single entity but entities is used where there are multiple. In the future I will remove entity_id and have singleclimate_scheduler_node_activated events fired by coordinator and the test events button didn’t match. entity_id is used if there’s a single entity but entities is used where there are multiple. In the future I will remove entity_id and have singleHello
Great integration which reproduce more or less what I have implemented long time ago with automation, script … It will dramatically simplify my configuration.
I have several electrical heaters in different rooms. All of them must be monitored with two profiles : Home and Office on a day by day basis.
May I ask some questions :
Two small green boxes with red cross around 10:00 can be seen on the profile. What does it mean ? How to delete them ?
There are display errors.
The widht of the screen is set to 4
I will continue my tests in the following days.
Some enhancement suggestions :
Sorry for my english. If it’s unclear I will try to reformulate.
Hi, glad it’s useful!
I’ll start with the easy one to answer 
The green boxes show times when the schedule advance feature was activated, this instantly applies the next node in the schedule. For example, if you get home early you can activate this to warm up the house. It will show a green dot at the time you clicked advance and a green line to the next node, this shows it’s a temporary adjustment. If you then click “Cancel Advance” it goes back to the original schedule and leaves a red cross behind at the time you cancelled. I thought this useful so that you can see when people wanted the schedule to change and maybe adjust it.
“Advance” is used to mean “use the next” so I may need a term that translates better.
Under Settings on the schedule there is a “Clear Advance History” button, if you click this those icons should be cleared.
“Advanced Schedule”
“Advance Cancelled”
Regarding the UI, it’s a mess at the minute and something I’m concentrating on for the next phase of development. I only made this work as a full size panel, if you use “Panel (Single Card)” the layout should be better at least.
A profile is currently for the entire schedule so for individual days and weekday/weekend it applies the same to all periods, I hadn’t considered that people would want different profiles per day/period but I can add this in. I work from home so I’m always here and have a daily schedule with no profiles, I don’t hit a lot of these issues as a result.
When you change profile it currently refreshes the UI and defaults to showing the current day, I can understand why this is frustrating for sure! I’ll add it to the list to improve.
The Climate Scheduler doesn’t actually do anything smart, it just sets the climate entity to the settings you request at the time you set them in the schedule. The rate is just a sensor so that I can see how my rooms are behaving, they aren’t currently doing anything clever. Someone requested I expose data that Intelligent Heating Pilot could use to automate with but they haven’t been able to test it yet. That uses Versatile Thermostat underneath which I need to look at too as it’d solve a lot of my problems.
I’m starting to think I need to rewrite this whole thing to be a new front end for Scheduler Component to be honest, it has a foothold in the community and everyone has used it as the basis for other cool components and automations and would basically fix loads of problems others are asking about. I need to have a proper think about that.
Hello Keegan
Thanks for your explanation.
In the profile, you set a temperature which may be different from the preset-mode of the heater.
Don’t you think it would be clearer to set the preset-mode instead of a temperature.
Otherwise the climate-scheduler settings may be incoherent with the climate settings behind.
It should also help to define profiles for group with several heaters which may need different comfort temperatures in each room (eg because the isolation is different in each and to feel confortable in room you need 20°C whereas in another room you only need 19°C). Both rooms will use climate-scheduler switching to Comfort, but for one room Comfort = 20°C and for the other Comfort = 19°C), thus saving energy and money.
Discard my previous suggestion
Some enhancement suggestions :
Add the capability to send a message (with template) to the companion app to inform the user (when the heater starts or ends with the current, targeted temperatures, …)
Stupid idea = an automation triggered by the climate is better.
Going back to the rate, what does it measure exactly ? The temperature variation in degrees/hour ? That’s all ?
The rate is high when the heating cycle starts. The rate was 0.0°C/H when the heating cycle was finished.
What I use in my current settings is more/or less Intelligent Heating Pilot without Versatile Thermostat.
Home made because Versatile Thermostat didn’t work well at the time I implemented HA.
If IHP is embedded in Climate-Scheduler it would be very smart as you save a lot of energy by starting when needed. Right now, I have set in Climate-Scheduler a start time taking into account the slope to be warm at the right time.
Once again, thanks for your integration.
Regards
The idea behind this is that Climate Scheduler is the primary way climate entities are automated and that there shouldn’t be anything else behind the scenes altering things. It includes lots of actions that let you automate different things while keeping CS in the middle coordinating things. If anything is changed manually, for example on the wall thermostat in the physical room, CS will respect the change and not override it though.
I was thinking temperature first as that’s just how it’s done in the UK so it’s my way of thinking, I’m learning this is different around the world though and factored that in
One of the things CS can do is automate the changing of climate presets at each node, without changing the temperature too. Apparently preset based thermostats are very common in France and this was an early user requested feature.
In the example below I clicked on the middle node and the “no change” box, this removes the temperature change from that node. “Preset Mode” that is expanded are actually the presets that the underlying thermostat presents. I don’t use them but the ones listed are the defaults my devices come with.
If your underlying climate entity has some internal automation that is based off the presets it presents then this should work.
If you click “No Change” for each node in the graph and choose which preset you wish to use I think it’ll do what you want it to.
For the sensors, it’s just a very simple thing that calculates degrees per hour, it was an experiment more than anything.
Regarding the messaging you requested, it can be easily automated I think. When a node is activated Climate Scheduler creates a climate_scheduler_node_activated event. You should be able to create an automation that sends a notification I think, either way it’s a way for you to implement your request. I added as many things like this so that it’s versatile for people to create custom behaviours as they wish.
First off all, thank you for making this integration : D
Looking at the example from the documentation:
Disable heating when away
automation:
- alias: "Disable heating when away"
trigger:
- platform: state
entity_id: person.homeowner
to: "not_home"
for: "01:00:00"
action:
- service: climate_scheduler.set_active_profile
data:
schedule_id: All Zones
profile_name: Away
The schedule_id: “All Zones”, - is this a thing (getting a no-target-set message in the automation editor)?
If not, any way you can make this work (less helpers to maintain)?
And my my group sensor look like this climate.climate_scheduler_climate_schedule_bedroom
a bit to much when the sensor is created?
I had accidentally created a cyclic dependency in my automations involving Climate Scheduler: action setting schedule profiles + action triggered on schedule profile change. When I broke the cycle by adding additional conditions, the behavior was gone.
But then when I tried to build something similar to confirm, I could not reproduce anymore. 
So I really don’t know… problem is gone, but I’m not sure why.
Oh crap, there was a bug I thought I squashed where it will recreate entities with climate_scheduler_ in front of them for some reason. I had some that had recursed about a dozen times, I’m guessing as I so frequently updated…
“All Zones” isn’t a valid group, but I could look at adding something similar if it’d be helpful?
That’s a really odd one, I’ve not heard or seen that behaviour to be honest. If you look in Settings → Entities and search for “Schedule ” though you should be able to bring up the history, there are also virtual climate entities that represent your schedules too.
You could at least check what time it’s happening as if it’s always the same time it could narrow it down.
Thank you. I did look at the entities for the schedules, and I could also actually watch the schedule groups being deactivated live when I triggered these automations for the profiles by hand. As I wrote above, problem is solved now, but I don’t know exactly why, and I can unfortunately not reproduce.
Again, thank you for your work. Apart from the hickup certainly caused by my own automations, this works like a charm. Finally something intuitive enough for less nerdy family members to use, which is a huge plus. 
That was what I was aiming for, I want something my girlfriend can use without needing a tutorial. She’s astonishingly intelligent so it’s not that she couldn’t figure it out, the point is it needs to be simple enough no one has to.
At the minute I think it’s a good balance of being able to understand how it works at a glance once it’s set up, with enough stuff for automations underneath for the power user.
