Demo Errors

[QbaF]

Hi, first of all it looks like node cronlus could be the best multi-time-management node in Node-Red environment, congratulations!

I just started with that node so I imported Examples because docs in the area of dynamic changing schedules were not sufficient for me. Unfortunately some examples return errors. e.g. In dynamic schedules

• "remove every 8" - "Invalid payload! Control topic 'remove' expects the name of the schedule to be in msg.payload"
• "start every 6" - "Invalid payload! Control topic 'start' expects the name of the schedule to be in msg.payload"
• "Get list of schedules" - "Invalid payload! Control topic 'list' expects the name of the schedule to be in msg.payload""

It looks like when you use command name (e.g. start) in topic, you shouldn't use it again in payload. At the other hand, when you have topic stop-all, using as a payload again command {"command": "stop-all"} does work.

In using dates

• "Add a 2 dynamic date sequence entries, 30 sec and 1 min from now" return "TypeError: (intermediate value).addSeconds is not a function"

Additional questions:

1. does command list = status?
2. what is payload.result.status.**modified** for?
3. Is there a chance to have Pause/Stop for a period of time?
4. is there a chance for prettyNext2/nextDescriptionShort which will be shorter (eg. "1 day 1h30'25"?

[Steve-Mcl]

Hi,

first of all it looks like node cronlus could be the best multi-time-management node in Node-Red environment, congratulations!

Thanks for the compliment - appreciated.

Unfortunately some examples return errors. e.g. In dynamic schedules... my apologies on the demos, quite a few changes were made recently & I could have sworn I updated the demos - I will get them checked ASAP.

It looks like when you use command name (e.g. start) in topic, you shouldn't use it again in payload. At the other hand, when you have topic stop-all, using as a payload again command {"command": "stop-all"} does work.

the general method of control is...

• plural items (stop-all, stop-all-dynamic, start-all etc) dont need a payload (it is ignored)
• single control items (stop, pause, start) that require a schedule name to be provided - this is expected in the payload
• batch control - use an object payload with command name and other parameters - this can also be an array of command objects for actioning multiple commands)

does command list = status?

Yes - its a legacy thing

what is payload.result.status.modified for?

For static entries that are changed at runtime

Is there a chance to have Pause/Stop for a period of time?

Unfortunately not - but its quite easy to achieve using delay or even another cron node I will however keep your suggestion in mind

is there a chance for prettyNext2/nextDescriptionShort which will be shorter (eg. "1 day 1h30'25"?

That certainly is possible but if I were to implement that I would likely expose a whole bunch of additinal formatting options (everyone's taste differs)

Hope that helps in some way.

I will update you on progress.

Cheers, Steve.