scheduled event did not run

[MikeB]

A few weeks back, with the old firmware, I had a scheduled event that did not run. It was a daily event, and the 'last run time' column listed the previous day, so the ISY-26 didn't even seem to try and execute the event. I had been doing some switch programming around that time, so figured the ISY-26 was busy and simply missed the event. I posted up on here, and Michel thought it might have been a bug. Since then, the few events I had configured have been running fine.

 

I installed the beta firmware last night, and created a lot more scheduled events. Last night I had 3 events that were supposed to run.

 

9:30pm - front door lights off. This ran fine.

11:00pm - holiday inside lights off. This did not run.

11:30pm - holiday outside lights off. This ran fine.

 

So, this AM I saw my 'holiday inside lights' were on. I went to log into the ISY-26 interface, and it gave me a java error after typing my username and password. The interface window would try to open, but it was blank.

 

I ended up rebooting my PC, then logged into the ISY-26, and noticed that some events had nothing in the last run time (probably events that hadn't run yet), some events had accurate dates/times for when they last ran, but others - including my event that did not run - had today's date (not last night's) with all zeros listed for the time.

 

I ended up powering down and powering back up the ISY-26 this AM, and I will try again to see if I have any issues.

 

Anyone see anything like this before?

[Mark Sanctuary]

I am finding that all the old pre beta schedules/triggers are not reliable so I have since replaced them. There is also a saving changes problem on the old schedules/triggers too, so you might want to read up on that as well.

[MikeB]

Thanks for the reply.

 

I recreated all my schedules with the new version.

 

My changes seem to be saving OK. Even after rebooting the ISY-26, they're all there.

[Mark Sanctuary]

Sounds good, the old schedules/triggers really gave me problems with running and saving.

 

I am trying to "break" it for bugs and find good "suggestions" right now so I thought I would chime in on your issue.

[MikeB]

I appreciate it.

[sfhutchi]

I am finding that all the old pre beta schedules/triggers are not reliable so I have since replaced them. There is also a saving changes problem on the old schedules/triggers too, so you might want to read up on that as well.

 

Interesting. I have seen some of my schedules not executing a percentage of the time also... or partially executing. I have also seen notices of non-communicative devices more often. For the schedule issue, did you simply recreate with the same code? UDI, Have you seen this on your end?

 

About the device communication? Has anyone else seen more communication problems since the update.. or is it just me? I don't see it all the time, but have seen an increase in occurence. This touches on another persons suggestions that if the ISY could collect some reliability data based on querys or commands sent, this would be helpful as we diagnose system problems.

[MikeB]

Haven't seen any communications issues, but my Insteon install has always been very reliable.

 

My events have been running fine since this, but I'm still curious what could have caused this. I'll report back if I have any missed events in the future.

[Michel Kohanim]

MikeB,

 

Thanks for the update. We are currently retesting the migration step for any inconsistencies.

 

With kind regards,

Michel

 

Haven't seen any communications issues, but my Insteon install has always been very reliable.

 

My events have been running fine since this, but I'm still curious what could have caused this. I'll report back if I have any missed events in the future.