But it, errm, doesn’t seem to be working properly? e.g. I can’t figure out a way to present a limited set of actions in a nice way - the screenshots show nice easy to use buttons for setting climate presets, etc. whereas now to turn the climate entity into “frost” mode I have to do:
Add action
Choose “Climate: Set preset mode” from the drop-down.
Pick the appropriate preset mode from another drop down.
At step (2), there are actions listed that aren’t relevant. In theory it seems that I could use exclude_actions to remove them from the list, but that doesn’t seem to work correctly - with the following config, the “Set preset mode” actions vanish from the list but “Set HVAC mode” is still listed:
Changing “set_hvac_mode” to “Set HVAC mode” causes all of the actions to vanish from the list.
The new look seems to be a huge step backwards. There is no way that I could expect anyone else in my household to change the schedules with the current configuration, whereas the card shown in the screenshots looks much more user friendly.
Hi, are the list of conditions available as a state of an entity or an attribute? I would like to have some kind of indication to show, which schedule is active based on conditions, however I can’t find these anywhere in the entities (most likely I’m blind). Any idea? Having a template sensors manually maintained for each schedule does not seem fun at all.
Cheers
Jacek
I’m also struggling with getting this scheduler working… I posted on Reddit here, and commented on a github bug, but just found this page about the integration too.
the basics of my issue are similar to @FireFury, where I can create the card, but there’s no default integration/entities… Even when I include a section in my configuration.yaml
Hi @all, this component is amazing and I’ve used it for many things.
With the re-design especially, and somewhat relevant to other comments, there is no indication in the edit dialog that a given schedule has conditions attached to it. You have to click on the settings gear and only then do you see any conditions. If I don’t remember I set a condition (or another user opens the dialog), you’d never even know the given schedule may or may not run as shown on the dialog.
I actually don’t know why you have to click the settings gear at all to show conditions. They are an instrumental part of the schedule, as it will only run if they are true. I can see possibly clicking the gear when creating a schedule to open the conditions up, but if they are set for a schedule you are editing, they should always show - I cannot see any user benefit to hiding them (other than just confusing the user).
Hello, I have a question about the conditions. I understand them to mean that one condition applies to the entire schedule. However, this leads to the problem that if the condition is met when the device is supposed to turn on, it switches on. But if the condition is no longer met at the scheduled switch-off time, the device does not switch off.
The documentation for scheduler-card is written for version v3.x.
I haven’t had the time yet to update the documentation to be in-line with v4, sorry about that.
I am spending the (limited) time I have available to fix issues in the card itself.
If you experience any problems with usage of the card, please open an issue in the GitHub project page.
I try to give attention to all issues opened here.
If you use the single mode option, then you can have the schedule end without the condition.
so instead of having one schedule scheme you will have two events in single mode. The first event, lets say switch on a device with the condition, and the second event switch off the device without the condition.
Do not understand sequence of creating a schedule.
Here is what I would like to do.
Have a light come on at 06:30 and off at 07:00 from November 15 to November 20th.
Can someone explain how to do this.
I have tried the from to, and does not work for me.
Also tried start time and end time, but end time box is clickable but can not change the time.
Am I the only one who has this issue? if I click on an already existing schedule on the card to update the days it will run on (I do this every week to set my radiators on/off depending on if I’m working from home or not), in addition to the days I select, it will sometimes add “everyday” as well. It already happened a few times and heated my house for nothing, so it’s a severe bug in my opinion (defeats the whole purpose of the scheduler).
The only way to see if it really happened is to check the “attributes” value on the thermostatic valve device. The “real” days are not even displayed on the scheduler card (only the one I selected in the dialog are displayed there), which makes this even more “dangerous” in my opinion.
The only way to remove that when it happens it to click on “back” on the days selection dialog, uncheck “everyday” (which I did not, at any point, check myself), and confirm.
It is possible to reduce scan interval? Ariston’s server is blocking requests from the integration because of a rate limit, often due to too frequent polling
I use it with my STR properties and what I’ve done is create a few different schedules that I switch between (via automation) based upon the status of the property. I would do something like that.
When we are away for a longer period of time, a physical button can be pressed. This activates a script that switches off all heating schedulers and sets all thermostats to Eco mode.
