Strange endtime when triggering PROGRAM_STARTSCRIPT

You found a bug or have any issues? Please post them here!
Post Reply
Thijmen
Posts: 39
Joined: 16 Jul 2019 20:19

Strange endtime when triggering PROGRAM_STARTSCRIPT

Post by Thijmen » 07 Aug 2020 12:28

Hi,

I am using PROGRAM_STARTSCRIPT and provided a scriptname, a date (1 minute after now() moment) and False.
When doing this, the current program looks like this:

I believe this is a bug. Or am I doing something wrong?

Thanks in advance.

Thijmen
Attachments
2020-08-07_12h26_48.png
2020-08-07_12h26_48.png (9.48 KiB) Viewed 1278 times

User avatar
radio42
Site Admin
Posts: 6373
Joined: 05 Apr 2012 16:26

Re: Strange endtime when triggering PROGRAM_STARTSCRIPT

Post by radio42 » 07 Aug 2020 13:11

Have you given an end date or duration with the command?
If not, the display is correct, as the current program itself has no end date.
But note that when using the continuous schedule mode, that the next program determines the physical end.

Thijmen
Posts: 39
Joined: 16 Jul 2019 20:19

Re: Strange endtime when triggering PROGRAM_STARTSCRIPT

Post by Thijmen » 07 Aug 2020 15:09

No, the command does not support an end date according to the docs:

Starts a script in a new or given playlist at the given time.
Parameter: (string) playlistname|scriptname|starttime|stopimmediate
Reply: OK|ERROR
playlistname: leave empty to open a new playlist; scriptname: leave
empty to use the current one; startTime: in format yyyy-MM-dd
HH:mm:ss; stopimmediate: True|False. Note: This also stops any
other running script.

User avatar
radio42
Site Admin
Posts: 6373
Joined: 05 Apr 2012 16:26

Re: Strange endtime when triggering PROGRAM_STARTSCRIPT

Post by radio42 » 07 Aug 2020 16:00

That’s what I meant ;-)
Either you use the Program Scheduler; or you switch programs manually and in that case, a started program would run indefinitely until a next program is started. And as a manually started program run indefinitely there is no end date.

So I don’t see any bug there.
Do you see one?

Thijmen
Posts: 39
Joined: 16 Jul 2019 20:19

Re: Strange endtime when triggering PROGRAM_STARTSCRIPT

Post by Thijmen » 07 Aug 2020 16:36

Ah, I was also running the Program Scheduler. I was under the assumption the endtime of the program would be the starttime of the new scheduled program. The 9999 confused me, but it makes sense :) Maybe change it if it has that date, the text to "indefinite"?

User avatar
radio42
Site Admin
Posts: 6373
Joined: 05 Apr 2012 16:26

Re: Strange endtime when triggering PROGRAM_STARTSCRIPT

Post by radio42 » 07 Aug 2020 17:16

No, in continuous mode (which is the default) the end time even for scheduler programs is completely ignored and the current program actually ends, when the next program starts.

Post Reply

Who is online

Users browsing this forum: No registered users and 12 guests