In short, what’s missing from the current scheduled launch is the selection of an execution month, right?
For cron, that’s not the project’s philosophy. Gladys is a product that should be usable by the whole family, not just developers! I agree that maybe some options are missing, but we’ll add them as they have been implemented so far
Hehe !!^^
Honestly, I think I haven’t had the title for a while; many people have made good progress in scene management. As for me, I haven’t done any more since @VonOx so graciously gave me this title ^^
I’m waiting for major changes (for me) before continuing.
If not, if the schedule is more complex, I recommend handling it via your calendar, and adding the dates of your bin pickups there as recurring events.
Then, use the trigger « a calendar event is coming » to receive an alert at that time:
In that case why not put « Monday, Wednesday, Friday, Sunday »?
Watering is typically something that should be done in the evening when it’s dark; the interval doesn’t allow choosing the time and isn’t designed for that kind of use!
I think a good way to do that right now is to use the Calendar in Gladys:
You connect a CalDAV calendar in Gladys (Google Calendar, Apple Calendar, or even free services like fruux — it works very well)
In your calendar, you create your events. Imagine you have a « foot » outing every other week, you create an event that repeats every 2 weeks, for example in Apple Calendar:
So yes, but a home automation system that constantly depends on external services isn’t great from my point of view.
To me, a home automation system must be able to withstand an internet outage — well, except for the weather lol.
But you’re right, the calendar can be very useful and customizable, for example from a local nextcloud, worth looking into, but not suitable for the average person.