03-31-2022, 11:33 AM
When the c++ program starts and all that data is printed if you look at the schedule section it will look something like this.
readSchedules--------------------------------
totalSchedules - 2
scheduleID ----- 10, 8,
scheduleName ----- test, tsstrs,
scheduleTypeID ----- 2, 1,
scheduleRuleID ----- 0, 0,
schedulePinID ----- 36, 5,
scheduleOffOn ----- 0, 1,
scheduleStart ----- 10800, 41100,
scheduleSun ----- 1, 1,
scheduleMon ----- 1, 1,
scheduleTue ----- 1, 1,
scheduleWed ----- 1, 1,
scheduleThu ----- 1, 1,
scheduleFri ----- 1, 1,
scheduleSat ----- 1, 1,
scheduleRepeatDays -- 0, 0,
scheduleEnabled ----- 1, 1,
scheduleEmail ----- 0, 0,
scheduleAlert ----- 0, 0,
scheduleCreated ----- 2022-03-31, 2022-03-31,
nextScheduleTimeStamp - 1648803600000, 1648833900000,
The last line is the next run time in milliseconds for each schedule found. If you copy that number into this website it translates quick so you can verify. This is how I verify things.
https://www.epochconverter.com/
readSchedules--------------------------------
totalSchedules - 2
scheduleID ----- 10, 8,
scheduleName ----- test, tsstrs,
scheduleTypeID ----- 2, 1,
scheduleRuleID ----- 0, 0,
schedulePinID ----- 36, 5,
scheduleOffOn ----- 0, 1,
scheduleStart ----- 10800, 41100,
scheduleSun ----- 1, 1,
scheduleMon ----- 1, 1,
scheduleTue ----- 1, 1,
scheduleWed ----- 1, 1,
scheduleThu ----- 1, 1,
scheduleFri ----- 1, 1,
scheduleSat ----- 1, 1,
scheduleRepeatDays -- 0, 0,
scheduleEnabled ----- 1, 1,
scheduleEmail ----- 0, 0,
scheduleAlert ----- 0, 0,
scheduleCreated ----- 2022-03-31, 2022-03-31,
nextScheduleTimeStamp - 1648803600000, 1648833900000,
The last line is the next run time in milliseconds for each schedule found. If you copy that number into this website it translates quick so you can verify. This is how I verify things.
https://www.epochconverter.com/