I would like the scheduler to only address climate devices and ignore the rest of the device types.
I would also like it to skip the selection phase of the device type (group) and when selecting to add an item, automatically select the climate group and move to the next step of selecting the entity to control.
Going further, I would like to define a card per AC (each AC unit will have its own card). In that case, when adding an item, automatically select climate and the entity, and go directly to selecting the action.
I would also like it to skip the selection phase of the device type (group) and when selecting to add an item, automatically select the climate group and move to the next step of selecting the entity to control.
I suppose that if you only have one group, this makes sense. I will have to add it though, currently you will still have to make an extra click. But good idea
Going further, I would like to define a card per AC (each AC unit will have its own card). In that case, when adding an item, automatically select climate and the entity, and go directly to selecting the action.
That makes sense. Could you make a feature request for it so i will remember?
Some users out here had kind of a strong opinion about this.
For now, I decided that the scheduler will only trigger actions on entering a timeslot.
Here entering includes:
The start time of the timeslot has been reached
HA just started up, and a schedule starts somewhere in a timeslot
Schedule was turned on (switch was flipped) and it starts somewhere in a timeslot
Schedule was just created or modified and it starts somewhere in a timeslot
The first condition is already in place, the card is pretty much done actually. I could release it somewhere this week.
But thereās a good chance that the scheduler-component will need a (big) update for supporting the remaining conditions, since there is currently no detection of a timeslot.
I expect that migrating the component will cause all the schedules to get corrupted (as in, your existing timeslot schedules will be wiped). Simply because the data stored in the entities will need to be changed.
I donāt know how people will react to these kind of breaking updates, so Iām a bit conservative here
I added a features request for the two features (action to set mode AC mode and temperature, automatic selection of group and entity). It will be great if you add these
Regarding addressing only the climate devices, when I set both switches to false as suggested, I get the device I defined in entities but only with the two options to set to cool and heat. How do I define to it to show all actions (cool, heat, temp, off)?
Iām not an advanced user, but I think there is a way to migrate entities between integration versions.
Take a look at async_migrate_entry function. For example this one. Hope this helps
@neliss Iāve raised an issue on Github with an issue I have experienced. It is;
I have defined 2 schedule cards in HA. One controlling schedules for some window vents, the other for defining activities in the Garden. The both have defined titles and are show on different pages in HA. When I move from one page to the other the title of the schedule card is not refreshing. I.e. when I am on the Garden page and move to the the vent page the schedule card displays āGardenā. Not sure if this is a card issue or a Chrome issue. If I press CTRL-F5 after moving pages it forces a refresh of the name of the schedule card.
One other observation. Is it possible to define groups of entities you want to schedule the same activity for? For example closing a set of blinds or putting on a set of lights? At the moment Iād have to define schedule events for each unique entity or have I missed something (againā¦)
These are minor issues by the way for an integration and card that are superb.
@isablend
I will check the issue with the titles when I have the time for it. I must say I never tested this scenario.
If it really bothers you, you could hide the title in both cards (and even place a markdown card as title replacement).
Regarding operating multiple devices at once, this is what scenes are intended for.
Ofcourse you could configure the scheduler to activate a scene.
But, I would like to allow picking multiple entities for a schedule in a future release.
It will have its limitations though, maybe only the same action, and same device type (so e.g. turn on multiple lamps). I donāt want to over-complicate the GUI.
Should be there in a couple of weeksā¦
Am I the only one who finds the time input to be confusing when trying to set something based on sunrise/sunset?
For example, I find it confusing the the sunrise/sunset icon on the bottom right is disabled and not clickable in this view:
If I increment the hour by 1 (e.g from 12:00 to 13:00), itās still not clickable:
However, I then increment to 5pm/17:00, and it suddenly becomes clickable:
Then if I tap, it the time entry becomes like the following, which Iām assuming means 1 hour before sunset?
My suggestion would be to have some option when configuring the turn on/off timing, to either select āTimeā or āEventā. If you choose Time, itās purely time entry.
If you then tap on āEventā, you use the same UI except Iād recommend using the words āSunriseā and āSunsetā (or āDawnā and āDuskā if thatās better) instead of just icons.
If I increment the hour by 1 (e.g from 12:00 to 13:00), itās still not clickable:
12:00 would be calculated to like 5 hours after sunrise
13:00 would be calculated to 5 hours before sunset
In my opinion, it doesnāt make sense at all to schedule something that is 5 hours away from sunrise or sunset.
So, I decided, that sunrise and sunset modes are only available when you are around (within 2 hours), of either.
I agree that this is something you have to figure out. But thatās why i wrote a manual for it. Once you get the hang of it, Iām sure you will be able to use it.
My suggestion would be to have some option when configuring the turn on/off timing, to either select āTimeā or āEventā. If you choose Time, itās purely time entry.
I think this is also a matter of taste. Personally, 1 hour before sunset doesnāt tell me much.
If I want to have my light turned on when its halfway of getting dark, I will wait for tonight and check at which time it seems half dark. At that time I program my schedule, let the UI calculate the offset.
If you then tap on āEventā, you use the same UI except Iād recommend using the words āSunriseā and āSunsetā (or āDawnā and āDuskā if thatās better) instead of just icons.
Agreed that the icons are not the best fit for the job. But I didnāt find more suitable ones. I would like to avoid using text as much as possible, since this is customary in Lovelace cards. And it will be quite some extra work to add translations to all languages.
In HA, go to Configuration > Integrations.
In the bottom right corner, click on the big button with a '+'.
...
Select it, and the scheduler integration is ready for use.
I had become accustomed to HACS integrations that install without further action from the user.
As far as I know this is not possible, but I would like to be proven otherwise.
Most custom_components are not true integrations, in the sense that they are not managed by the āintegrationsā page but in your configurations.yaml.
Why is the scheduler-component an integration? Because it is UI managed. This is the only way to have it automatically generate entities for you. Check out here for more info.
@fanuch@Misiu
As requested, if you feel like I deserve a donation, you can now do so.
Rest assured that donations are not needed to keep improvements coming, I do this for fun.
Ofcourse the gesture is very appreciated
I totally agree, but my proposed approach doesnāt mean you have to have that large of values. In the node red module I use for scheduling, what I really like is they allow you to specify an exact time or the event. See this drop down values they provide:
Whatās nice is you have more subtle options for daily events such as choosing between ādawnā and āsunriseā which are technically different.
However, in addition to this, they also have an āoffsetā which is what you are doing, which takes in a positive or negative value. e.g. ā-60ā is 60 mins before the event (such as 60 minutes before dawn).
Youāre right the UI input is a matter of taste. However, I disagree that ā1 hour before sunsetā doesnāt tell. you much. Your scenarios of āI want to have my light turned on when itās halfway getting darkā is dynamic and changes as days/weeks progress through a season due to changing sunset times. So the best way is to do offsets from one of those events (dusk/sunset, etc).
e.g. Turn this light on 60 minutes before dusk
Yeah, totally makes sense about the concern over translations. However, Iām really pushing on adding more event types as mentioned above due to the power it unlocks, so using words is unavoidable since you wonāt find good icons to differentiate dusk vs sunset.
To be clear, i love the card so far. Just giving input to make it really powerful (and so I can get ride of my dependency on Node Red for scheduling!)
Is it possible to use this with a group of switches? Iāve got 3 smart switches controlling exterior lights that I want on the same schedule. Iāve defined a group for them, but they donāt show up as options in the scheduler card.
Is this because groups like this arenāt able to be toggled on/off in Home Assistant, or is it a limitation of the Scheduler card in that it doesnāt work with groups?
