NAC Firmware 1.13.0 Scheduler Issue

[MarkHenry]

Have updated a couple of NAC's to v1.13.0 and noticed that the schedulers are not working as expected.

From my understanding if there is no enable group added to the scheduler and the scheduler is active, the schedules should then operate the same as before the update.

As the schedule enable didn't exist in previous version all schedules show unused in the enable group.

What I am seeing is that NO schedulers that existed before the update are currently running.

Interesting that if I create a new schedule that doesn't have a enable group after the update it works, so im guessing something is broken when the update occurs.

[Asli]

Hi Mark,

We are looking into the issue at the moment, and we will update you.

thank you,

[DarrenMullighan]

Hi Mark,

I have been giving this a go over the past few hours, and sadly, have failed to replicate.

Do you have any specifics that I might be able to use in my testing? Firmware versions you came from, applications used, did you use sunset/sunrise? any information at all would be great.

Thanks

[MarkHenry]

Hi Darren,

Was running 1.12.0 prior to update. Have had the issue on a NAC2 and NAC.

Schedules run various applications, some a just lighting, trigger or user parameter.

Various fixed timers, sunset, sunrise etc

Updated firmware to 1.13.0

All looked fine until the next day when schedules failed to run.

Sunrise failed trigger schedule, Fixed timers in morning failed to trigger

Started a log for traffic and monitored during the day, no schedules ran.

Created a new schedule as a test, used fixed timer and random group and it worked.

My current workaround for this is below:

Opened each schedule then added an Enable Group, then saved then removed and saved again.

Not much fun when there are around 50 schedules running.

All schedules now working without enable groups in them.

Hopefully this makes sense, if not let me know.

[adammcleod]

Hi Mark & Darren,

Yep same problem here.

Error log showing a scheduling issue since updating to 1.13

None of my schedules are now functioning.

 

Let me know if you need anything else.

Regards

Adam

[DarrenMullighan · Accepted solution]

Hi Adam,

Just to confirm, are you running a script called "schedulers"?

[DarrenMullighan]

@MarkHenry Do you get the same errors in your error log as well?

[MarkHenry]

Yes logs for both NAC's showed around 30 of the same error.

[Mr_C]

Thank you for reporting the issue with Schedulers not running after updating to 1.13.0 Firmware on the C-Bus automation Controllers. 

The cause of this issue has been identified and will be resolved in the next release of firmware.  The details of this issue and how it occurs are:

The issue only applies to a device with a project that contains one or more schedules created in the project when the firmware build was version 1.6.0 and where these schedulers have never been modified or saved on a unit when it had a later firmware version 1.9.0 or later. (Please note the issue is on Schedulers being saved, and not the saving / modification of a Scheduled event)

Only Schedulers created in 1.6.0 firmware are impacted by this issues, schedulers created under firmware version 1.9.0 and later will still run .

Hence the issue does not impact every upgrade and is dependent on the scheduler history within the project. it may also appear as some schedulers running and some not.

The issue is worked around by editing the scheduler (not the scheduler events) and saving it (no changes to the scheduler are required) the save event will update the null value to a defined value and the scheduler code will no longer encounter an exception. This is a workaround if encountering this problem with 1.13.0 firmware.

The next firmware release to be announced will contain a fix to handle the null value and thus will not require any workarounds when upgrading units or restoring projects to units with this firmware and above.

[Asli]

Hi Mark and Adam,

The latest version (V1.14.0) of the Controllers' Firmware has been uploaded to the site, addressing your submitted issue. You can check this link for details.

C-Bus team