SHAC FIRMWARE V13.0 UPDATE

This issue has been reported and is currently been investigated, However it seems to that this is not affecting everyone, who has updated, It would be good if anyone who is updating to 1.13.0 firmware could report on this problem with the following details .

Firmware Version updated From, I.E 1.6.0 to 1.13.0 or 1.12.0 to .13.0
Number and Type of Schedules, I.E Number of Schedule Category's, or no Category defined, or Script Schedules
Did all Schedules not run or only some of them , if only some of them what kind of object were they scheduling and what values for scheduling where they running, I.E Date Specifical or All dates, Time specific or Sunset/Sunrise, where Holidays having an effect to run / not run.

Currently the issue as reported has been hard to reproduce both in the Lab and also in the Field, It is quite clear that there is an issue out there but not everyone would appear to have it, so anyone on this forum who is updating the firmware to 1.13.0 of existing projects before taking the steps in the post it would be good to validate if the schedules run on their own first. And if you're having this problem Please post a reply with details to help.

In the mean time we Do hope that you find value in the updates to scheduler with the ability to enabled and disable Schedulers and Scheduled events with objects.

 

Can you check the Error Log , or alert Log in the unit for any entry's about schedulers after the update was done.

 

Thanks to those who gave the feedback, there is no further need for additional feedback now as we have indeed identified the root cause, and are now working on a fast fix firmware release to address the issue. this will be a 1.14.0 firmware release.

But to keep you informed of the root cause of how and when this applies.

This 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 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 having 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.