Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Walt2]

I have Timer Events which are specified to run only on very specific dates.  For example, I have a  Timer Event which I want to execute only on this year's Labor Day.  So, it has a start date of 09/01 and an end date of 09/01. 

My problem is, it seems to execute on random days.  For example, it executed three times in the past week (and this is only August !!    ).

These are "old" Timer Events which have worked correctly for many years.  Well, worked correctly until I updated to AHP 3.228.    Now, all my Timer Events which are specified for only specific dates, seem to execute almost randomly on other dates.
 
I have read reports here that others found that upon upgrading to 3.228, that their Timer Event dates changed or reset back to a start date of 01/01 and an end date of 12/31.  I have verified mine didn't.  And I even re-entered all their dates, as part of my desperate debugging,  just in case.   Didn't help.
 
Other than for the one-day long execution "window" (start date = end date), all my Timer Events are just standard old Timer Events.  Nothing special.
 
I have tried every debugging trick I can think of, from my many years of experience with AHP.  Nothing seems to work.   

Does anyone else have Timer Events which are setup to execute just on one particular day?  Are they working for you with AHP 3.228 ?

[Walt2]

I did a bit more debugging.  Here is the contents of ahpeeprom_r.txt.  This appears to be correct and consistent with what I programmed into AHP.
 

Code: [Select]


   Su Mo Tu We Th Fr Sa , from 1-jan to 1-jan
         time on  01:00
            set flag 4 on
         
   Su Mo Tu We Th Fr Sa , from 26-may to 26-may
         time on  01:00
            set flag 4 on
         
   Su Mo Tu We Th Fr Sa , from 4-jul to 4-jul
         time on  01:00
            set flag 4 on
         
   Su Mo Tu We Th Fr Sa , from 1-sep to 1-sep
         time on  01:00
            set flag 4 on
         
   Su Mo Tu We Th Fr Sa , from 27-nov to 28-nov
         time on  01:00
            set flag 4 on
         
   Su Mo Tu We Th Fr Sa , from 25-dec to 25-dec
         time on  01:00
            set flag 4 on
         
   Su Mo Tu We Th Fr Sa , from 1-jan to 1-jan
         time on  23:30
            set flag 4 off
         
   Su Mo Tu We Th Fr Sa , from 26-may to 26-may
         time on  23:30
            set flag 4 off
         
   Su Mo Tu We Th Fr Sa , from 4-jul to 4-jul
         time on  23:30
            set flag 4 off
         
   Su Mo Tu We Th Fr Sa , from 1-sep to 1-sep
         time on  23:30
            set flag 4 off
         
   Su Mo Tu We Th Fr Sa , from 27-nov to 28-nov
         time on  23:30
            set flag 4 off
         
   Su Mo Tu We Th Fr Sa , from 25-dec to 25-dec
         time on  23:30
            set flag 4 off
 

Here is the contents of the file ahpeeprom_w.txt.   It differs from the above, differs from what I programmed into AHP, and appears to be down right wrong.   Note that the "extra" wrong lines, even contain dates which don't even exist in the calendar (like Jan 0, and Dec 33)!!!
 

Code: [Select]

 Su Mo Tu We Th Fr Sa , from 1-jan to 1-jan
         time on  01:00
            set flag 4 on
         
  Su Mo Tu We Th Fr Sa , from 0-jan to 5-may
         time on  01:00
            set flag 4 on
         
  Su Mo Tu We Th Fr Sa , from 26-may to 33-dec
         time on  01:00
            set flag 4 on
         
   Su Mo Tu We Th Fr Sa , from 4-jul to 4-jul
         time on  01:00
            set flag 4 on
         
   Su Mo Tu We Th Fr Sa , from 1-sep to 1-sep
         time on  01:00
            set flag 4 on
         
   Su Mo Tu We Th Fr Sa , from 27-nov to 28-nov
         time on  01:00
            set flag 4 on
         
   Su Mo Tu We Th Fr Sa , from 25-dec to 25-dec
         time on  01:00
            set flag 4 on
         
   Su Mo Tu We Th Fr Sa , from 1-jan to 1-jan
         time on  23:30
            set flag 4 off
         
   Su Mo Tu We Th Fr Sa , from 0-jan to 5-may
         time on  23:30
            set flag 4 off
         
   Su Mo Tu We Th Fr Sa , from 26-may to 33-dec
         time on  23:30
            set flag 4 off
         
   Su Mo Tu We Th Fr Sa , from 4-jul to 4-jul
         time on  23:30
            set flag 4 off
         
   Su Mo Tu We Th Fr Sa , from 1-sep to 1-sep
         time on  23:30
            set flag 4 off
         
   Su Mo Tu We Th Fr Sa , from 27-nov to 28-nov
         time on  23:30
            set flag 4 off
         
   Su Mo Tu We Th Fr Sa , from 25-dec to 25-dec
         time on  23:30
            set flag 4 off

HELP!!!!

[Charles Sullivan]

You're saying that what's written to the CM15A is wrong but when the binary is read back from the CM15A and translated, it looks correct.
Could you have the two file names reversed?

[Walt2]

The "written" file I quoted is what's generated by the new version of AHP.

The "read back" file I quoted is indeed an older file from the previous version of AHP. A version that worked.  It just happens to be what I still have available to use as a reference (I don't have an old "written" file anymore).

I was just attempting to show the difference between old download code that worked, and new download code that doesn't work.   As I pointed out, the newly generated code, has some really odd things in it, like dates of "Jan 00" and "Dec 33".

BTW, both versions of AHP are using the same .AHX file.  I haven't made any changes in my .AHX for well over a 9 months.

[Charles Sullivan]

OK, now it's clear.  Well I guess you know the drill - reprogram from scratch and see if that works.

BTW, does the debug uploader tool no longer work under 3.228 ?

[Walt2]

Yea, I am trying to avoid starting all over from scratch.  Especially since I have convinced myself that it would not help. 

The same .AHX file produces a good download with the old version of AHP, and a bad download with the new version of AHP.   I just got to believe that a totally new .AHX will still produced a bad download, with the new version of AHP, if I enter the same Timer Events, the same way.
 
I think there is really a newly introduced bug in the latest version of AHP.   Not only because of my problems, but also from the reports posted here by others who had some really odd things happen with their Timer Event start/end dates after they upgraded AHP. 
   
I am more wishing that X10 would listen (I miss Mike C), and fix it, than I am looking for a work-around.