Jump to content

Programs stopped running last night


ppitkin

Recommended Posts

Something strange happened on my ISY last night at around 02:00...

My regularly scheduled programs all stopped running!

 

when entering the program summary section of the admin console I noticed that all the time last started and time last finished entries were empty! The same was true for the scheduled next run time.

 

The only entry that was still in there was the 03:00 entry for the query all process. It was almost as though the ISY had rebooted - but it had not.

 

Could this be something related to the change in DST?

 

I could understand it if some of the programs had stooped due to the time suddenly jumping by 1 hour ( as the test is time last run plus 15 mins) but it doesn't explain why all the time entries were blank in the admin console.

Link to comment

My apologies, I should have been more clear.

 

My run times were blank until I manually ran the "If" statement, but the programs still work as they should, I just tested one.

 

Now, that was an sensor-based program (I opened a monitored door), not a time-based one.

 

The next time-based event will be sundown, and I'll check this evening to be sure that ran.

 

The OP indicated his programs weren't at all, apparently

 

(I.... may have the same problem, come to re-read his post, but I won't know until roughly sundown.)

Link to comment

Hi Michel

 

This one stopped running after 2:00 AM:

 

If

- No Conditions - (To add one, press 'Schedule' or 'Condition')

 

Then

Repeat Every 3 minutes

Set Elk Zone 'OutLightLevel' Query Voltage

 

Else

- No Actions - (To add one, press 'Action')

 

 

And this one didn't run but it was set for 2 AM so I changed it to run at 1:45AM from now on.

 

If

Time is 2:00:00AM

 

Then

Set Scene 'Outside Lighting / Low Voltage Lighting' Off

 

Else

- No Actions - (To add one, press 'Action')

 

 

Gary

Link to comment

Hello all,

 

Thanks so very much for the update. This is indeed an intermittent bug which was supposed to have been fixed in 4.0.5 but it seems that there are certain corner cases that the fix has not addressed. I am so very sorry for the inconvenience. This should be fixed right after 4.1.3.

 

With kind regards,

Michel

Link to comment

Archived

This topic is now archived and is closed to further replies.


  • Recently Browsing

    • No registered users viewing this page.
  • Who's Online (See full list)

  • Forum Statistics

    • Total Topics
      36.9k
    • Total Posts
      370.3k
×
×
  • Create New...