Page 1 of 1

Strange endtime when triggering PROGRAM_STARTSCRIPT

Posted: 07 Aug 2020 12:28
by Thijmen
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

Re: Strange endtime when triggering PROGRAM_STARTSCRIPT

Posted: 07 Aug 2020 13:11
by radio42
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.

Re: Strange endtime when triggering PROGRAM_STARTSCRIPT

Posted: 07 Aug 2020 15:09
by Thijmen
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.

Re: Strange endtime when triggering PROGRAM_STARTSCRIPT

Posted: 07 Aug 2020 16:00
by radio42
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?

Re: Strange endtime when triggering PROGRAM_STARTSCRIPT

Posted: 07 Aug 2020 16:36
by Thijmen
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"?

Re: Strange endtime when triggering PROGRAM_STARTSCRIPT

Posted: 07 Aug 2020 17:16
by radio42
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.