I am not a programmer and just started using home assistant that my dad installed. I created an automation to open my blinds at 9AM, but I don’t want it to open on Sundays, like I have with my alarm on the phone.
I would be much easier if I could select the When exactly like I do in my alarm:
Please consider adding that, it will be much easier for the users that are not technical.
Hi @Hellis81 I did not find a way to use schedule. I want to wake up with my blind 8:55 from Monday to Saturday. This calendar is different you add things in your agenda with a start time and end time. I don’t want to create anything complicated, as I said it is like I create an alarm on my phone. I tried all options on Home Assistant and did not find a way, this is why my dad told me it need a feature request.
In you automation you can add a condition for which days it works on.
Open the automation and click “Add Condition”. Select “Time and Location” then “Time”. At the bottom there is a selection called Weekdays. If you click this it will open a list of days where you can select which days you want the automation to run on.
Thanks @ShadowFist! It is exactly what I wanted. I think it is still strange that I have to put after 8:50 and before 9 if I want 8:55 fixed time before. Maybe it makes sense to add the same Weekdays field on When time It will make users less confused.
Weekday isn’t a trigger so cannot be in the When section.
It’s a condition, which is why it’s in the And If section. The only thing I’d agree with is that it’s not intuitive that it requires a time, which is why you need to add the after & before part.
It would be more intuitive if it was just a weekday condition on its own. The workday sensor doesn’t apply to cases such as yours.
You’re new here. Have a read through the docs & play around with automations. You’ll get the hang of it soon
As a software engineer and advanced user of HA, I would disagree with you.
Actually from the proposal from @barrelful the existing Time trigger could be extended to have an extra Weekdays field and the configuration would be possible exactly how he said. If you don’t select any Weekdays, it will execute on the time every day.
I believe also the interface would be much more intuitive to create automations that should be triggered in specific times only on selected days. Also I don’t see why we couldn’t make this post a valid feature request for this especific extension of Time trigger.
Let me try and break down why I think Weekdays make no sense as a trigger:
Monday as a weekday trigger goes off at 00:00, so that is when the automation gets triggered. In this specific case, it is triggered every week on Monday.
9:30 as a time trigger goes off at 9:30 daily, irrespective of the weekday.
Monday at 9:30 is a combination of two distinct triggers in your proposal. Triggers are always OR, therefore only one of those is required for the automation to start.
This makes weekday a classic description of a condition (despite my misgivings on the time dependency in that section). When the time is 9:30, the automation is triggered, then it will only continue to run on condition that the weekday is Monday.
The schedule helper proposed by koying above avoids the double trigger situation by running its own logic outside the automation engine. The state of the helper can be used as an automation trigger because it is now a single item which has no dependencies.
Ok, but you interpreted what I said different. I said to use it as an extension of existing Time trigger for fixed value. Then if I go to your points:
Monday as a weekday trigger goes off at 00:00, so that is when the automation gets triggered. In this specific case, it is triggered every week on Monday. → this should not be possible… Time trigger still needs a fixed time, you cannot just specify Weekdays.
9:30 as a time trigger goes off at 9:30 daily, irrespective of the weekday. → correct, this is how it works today for time trigger and should continue to work the same with the extended field.
Monday at 9:30 is a combination of two distinct triggers in your proposal. Triggers are always OR, therefore only one of those is required for the automation to start. → no, this is an extra field, so it of course will act as AND not OR. Exactly like an alarm interface shown by @barrelful .
This makes weekday a classic description of a condition (despite my misgivings on the time dependency in that section). When the time is 9:30, the automation is triggered, then it will only continue to run on condition that the weekday is Monday. → this is explained by the 3 points above.
Exactly I believe this would be feasible and simple interface for an end user. I never contributed before no HA code, but with some guidance on where changes are needed I would be able to do it. @Hellis81 are you a HA developer?
Don’t bother, this was denied recently. The change will not go through.
Changes to triggers are exceptionally hard to introduce. They need to discussed before code is even developed. If you do the work, there is no guarantee it will be added to core.