Issues with schedule

cphassistant · October 13, 2024, 8:47am

I use light scheduler node to randomize certain actions on a schedule. For some reason some of the schedule nodes at triggering at random times outside of the schedule. The have similar config as other nodes but seem to have their own life. I have no idea how to bug track.

Time settings are correct as other schedules will work fine.

The attached screenshot triggered an ON event at 2:09 AM. It’s set to schedule only and output when state changes.

Mikefila · October 13, 2024, 12:21pm

github.com/niklaswall/node-red-contrib-light-scheduler

Randomisation not working correctly (+ solution)

opened 11:17AM - 26 Jan 24 UTC

wouzer

I have been using this light scheduler for a couple of years now, almost to full… satisfaction. I did notice however that every so often the lights switch off outside the timeframe defined by the randomization. I have been looking at the code, and it seems in the randomization it uses the previous start(or end) time as basis, rather than the time as depicted in the scedule. Most of the time this levels out, but every so often it moves outside the bounderaries of 'scheduled time' +/- random minuts. And this can compound to quite a lot of minutes if the random nummer is To illustrate I have logged the times for a while each time the randomizeSchedule was called. The schedule was from 16.00 to 23.15, with 15 minutes randomisation. I have logged the resulting new start/end time, follewed by the basis it used for the calculation in brackets. As you can see, this basis is alway the previous starttime, not time as in the schedule (apart from the first line obviously). new - day 4 --> start : 15:56 (16:00), end : 23:29 (23:15) new - day 4 --> start : 15:51 (15:56), end : 23:40 (23:29) new - day 4 --> start : 15:52 (15:51), end : 23:29 (23:40) <---- end time outside schedule new - day 4 --> start : 15:40 (15:52), end : 23:17 (23:29) new - day 4 --> start : 15:39 (15:40), end : 23:04 (23:17) <---- start time outside schedule new - day 4 --> start : 15:47 (15:39), end : 23:03 (23:04) new - day 4 --> start : 15:56 (15:47), end : 23:11 (23:03) new - day 4 --> start : 15:47 (15:56), end : 23:12 (23:11) After some carefull digging in my javascript knowlegde, I discovered that in the map function used in the randomizeSchedule, the eventparameter is changed and returned to be stored in runningEvents. However, as the event object in the map function is passed by reference (and not by value), the original schedule ('events') is is also changed as in the map function changes each event. Solution is to deep clone the event into a new_event, change and return that. node.runningEvents = node.events.map(event => { var minutes = event.end.mod - event.start.mod let new_event = JSON.parse(JSON.stringify(event)) // deepClone the event, // Prevent randomization of event that start and end at midnight to // prevent "gaps" when the schedule continuous past midnight. // TODO: Handle all events that is back-to-back after each other. if (event.start.mod !== 0) new_event.start.mod = event.start.mod + offsetMOD() if (event.end.mod !== 0) { new_event.end.mod = event.end.mod + offsetMOD() if (event.end.mod <= event.start.mod) // Handle "too short events" new_event.end.mod = event.start.mod + minutes // Events can overlap, but we don't need to care about that } return new_event }) Works like a charm now. new - dag 4 --> start : 16:05 (16:00), end : 22:59 (23:15) new - dag 4 --> start : 16:03 (16:00), end : 23:00 (23:15) new - dag 4 --> start : 16:07 (16:00), end : 22:56 (23:15) new - dag 4 --> start : 16:08 (16:00), end : 23:14 (23:15) new - dag 4 --> start : 16:12 (16:00), end : 23:14 (23:15) new - dag 4 --> start : 16:12 (16:00), end : 23:26 (23:15) new - dag 4 --> start : 16:14 (16:00), end : 23:20 (23:15) new - dag 4 --> start : 16:17 (16:00), end : 23:13 (23:15) new - dag 4 --> start : 15:58 (16:00), end : 23:17 (23:15) I'll create a pull request for this.

cphassistant · October 15, 2024, 5:21pm

Thank you for the suggestion. However, I’m already using 0.0.18, which should include the mentioned fix.

Mikefila · October 15, 2024, 5:29pm

Well it seems that the merged fix isn’t working. You should post to that issue and explain that you are using the updated version, yet the problem persists.