[App][Pro] Advanced Scheduler

Yeah, i might be interested in updating and maintaining it!

@Sharkys indeed and thanks!
This is indeed my kind of app.

6 Likes

@Arie_J_Godschalk: That is VERY good news for me and the approx 1000 users of this app. I will send you a private message.

1 Like

So now there is a SDK3 test version out, thanks to @Arie_J_Godschalk. Thanks for that!

Please everybody, if you have the time, test it here: Advanced Scheduler | Homey

4 Likes

@Fredrik_Palsson does this version also contain the fix for daytime saving issue?
(We will be able to actually test it in a monthšŸ˜‰)

I will install the test version and see how it works

Please note that there was a small error in the last test version. I“ve published 0.4.2 for testing, so please try that version.

Unfortunately no fix for the DST issue yet, but while I“m working in this I will try to hunt that bug down.

3 Likes

Hi Fredrik,
just in case log will not contain relevant info… 0.4.2 version

Solving it now and will send a Pull Request.

Edit:
Small bug solved by XeroxQ Ā· Pull Request #20 Ā· fpalsson/com.fp.advanced-scheduler (github.com)

Hey @Fredrik_Palsson , there is a pull request.

1 Like

I was VERY optimistic and thought the app would run on SDK3 if it would compile and build. But there seems to be a lot of small things to correct.

  • SDK handles all times in GMT, so logic needs to be adjusted.
  • There are runtime errors a little randomly when tokens are added and removed.

The good news are that sometimes flows are triggered if setup times are adjusted to match GMT. There is hope.

I suggest you all reinstall the current version of the app while I try to get the SDK3 version flying.

4 Likes

So now there is a version in test that seems promising. Quite some refactoring done, so some errors might pop up. Also It was so late here, there are no sun events possible to test. Please try out this version and let me know your results.

Might also have corrected the DST bug at the same time… Fingers crossed

2 Likes

If you are testing, please let me know if the test version is working for you.

Also, could any native speaking Dutch and German persons check this new flow card translation for me?

ā€œhintā€: {
ā€œenā€: ā€œTriggers when a shedule item time or sun event in selected shedule is occuring.ā€,
ā€œsvā€: ā€œAktiveras nƤr en schemahƤndelse eller solhƤndelse i valt schema intrƤffarā€,
ā€œdeā€: ā€œWird ausgelƶst, wenn eine Zeitplanelement oder ein Sonnenereignis in ausgewƤhlten Zeitplan auftritt.ā€,
ā€œnlā€: ā€œWordt geactiveerd wanneer een schema gebeurtenis of een zongebeurtenis in het geselecteerde schema plaatsvindt.ā€
},

Well, it doesn’t read good imho, as in, i don’t imidiantly understand what’s it about, but i have the same feeling about the English:

The ā€œtimeā€ get’s removed from the translation, so back in English, your Dutch translates to about:
Get’s activated when a schedule event or time event in the selected schedule occurs.

Does that sound right to you?

If so, i still think this is better:
Activeert wanneer er een schema(tijd)- of zongebeurtenis in het geselecteerde schema plaatsvindt.

The (tijd) is a questionmark for me, depends on what the flowcard is about.
But, personally, i think this reads a bit nicer.

1 Like

I’ve been using some of the event triggers for a long time. I did some simle checking yesterday and found that sunset and sunrise triggers at the correct time, but midnight is one hour off.

Forgot to mention that my testing was for time zone GMT +1.

Do you by midnight mean a timebased event, set to 00:00?

Sorry for the late response. Yes, I have a Schedule event for all week set at 00:00. It triggers at 01:00.

1 Like

But I guess other time based triggers trigger at the correct time, right?

I created a new schedule with timbased event at 07:00. This one triggered at the right time. I have also made separate schedules with triggers for 23:59 and 00:01 just to verify. I’ll will update with status after midnight or tomorrow morning.

1 Like

It seems that everything set for triggering between 00:00 and 01:00 triggers at 01:00 if you are at GMT+1. Will investigate.

Hi @Fredrik_Palsson. You are right. All timebased triggers between 00:00 and 01:00 triggered at 01:00. This seems to be corrected in the newest version.

Thanks for your effort and hours spent for this app.
Rgds.
Jan Olav

2 Likes

Thanks, your feedback is appreciated. I’ve spent several hundreds of hours on this app, as I didn’t know any of the stuff needed for this (I’m an old c# developer). I had to learn JS (node), Typescript, Homey SDK, Vue :slight_smile:

4 Likes