Unless it’s my own lack of understanding of cron, what i can do with cron is to schedule the job every first and third wed, or the second and fourth wed, but the cron job schedule breaks when it moves from a month with four Wed to a month with five Wed.
My bad, I just had no doubt cron should be able to do that easily. But from what I’ve read exactly this is just not possible with cron.
But, you can do it the Homey way, without any app:
Just trigger at the desired time, and filter on day and even/odd weeks.
1 Like
Wow thanks! This is a nice hack!!
1 Like
Hi Fredrik. Thanks for creating this great App! I want to use to start actions using a matrix of time-slots (9 in total) and per month (108 different times). As we are now in April I created a series of events for April that trigger at 06:12, 07:44, 09:17, 10:49, …, 18:32. The series for the other months are different. Is there a trick to also include the other months, or is the way forward to create 12 schedules (one for January, one for February, …) and then combine it with a Date & Time (as AND) to have it up and running? Thanks again, great App! 
Best regards, Jan
This is now how I implemented this (series of times per month). Next step is now to use the forecast(s) into my (to be set-up) HEMS-system.
Hello,
I’m using the app to program heaters at home, thanks for this good app, really reliable.
I have 2 new features suggestions :
1/ Allow a “by default” value of the variables for initialisation. If the app loads it’s configuration & tags are not defined, load default values.
In my case, i just migrated Homey from 2019 to 2023 model, the Advanced scheduler configuration war correctly loaded, but initial tags values associated to schedules were empty after migration.
=> all my scripts can not start with non number values, so i had to create a special event on all my schedules to allow initilisation of the tags without waiting for the next events.
I remembered that i faced the same difficulty during creation of the scripts, so i think it could be a good (& small) evolution of the app.
2/ order schedule events
if you add a schrdule at 15:30, it will appear at the end of the list, even if some other events are scheduled after 15:30. Not easy to manage when you configure a lot of events.
thanks a lot for this app 
Bye
1 Like
I was about to request the same feature: a default tag value.
This is a great app by the way! Tremendously useful to reduce complexity of flows. Amazing!
Thank you for these suggestions. It would likely be very easy to implement your suggestions, but unfortunately I have no time to spare for this at this point. Currently I do not even have a development environment to do and test any changes in. If you know of someone that is willing to co develop this app with me, I would gladly invite them.
