WAIT commands failed after EST to DST time change

[Nestor]

I have a program that I use at bedtime to switch off lights, etc, including  a WAIT command to set my thermostat after several hours. I woke up this morning to find my thermostat hadn't returned to normal temperature. 

Another program I have keeps a rolling average of lux values from my tempest. (Thanks, @GSpitale01 ) It too has a short WAIT command and quit just before 0200. 

My time zone is Canada, ON, Toronto; DST checkbox is disabled. 

The lux program is more recent, but the bedtime program was used without issue when I had the 994i.

Is this a bug in EISY or am I misunderstanding a fundamental concept about the WAIT command? 

 

 

Edited Sunday at 12:30 PM by Nestor

[larryllix]

This is a problem that will not ever go away with Wait commands. When the Wait command is encountered ISY installs an absolute time into a stack to to be checked for that exact time to trigger an event or return to your program.

Now when there is no absolute time between 2:00 AM and 3:00 AM (doesn't exist) your Wait expiry time never occurs.

This has been discussed ad nauseum in these threads. Other problems occur when the clock return to STD time.

The cure needs to evaluate each case on its own conditions and provide a fix to suit. IIRC there are about 6 different scenarios to be handled differently and they have not implemented anything that complex due to other technologies taking most of the development time.

I always use  some "all else fails"  retrigger conditions in my IF section to circumvent loops stalling forever such as:

If
    time is 7:00 AM
 OR
   time is 7:00 PM
 OR
   other trigger conditions

THEN
    repeat every 5 minutes
        do something

ELSE
    -------

I received a warning that my CAO Wireless tags heartbeat failed, based on a heartbeat signal every 5 minutes. I have since extended that test to 90 minutes to avoid these annoyances.

Dear Doug Ford,
  Please stop the DST time nonsense and who cares what NY or QC is doing?

Edited Sunday at 07:13 PM by larryllix

[Nestor]

Thanks for your answer. All this time with ISY/EISY and I never knew this bug persisted as it did.