Event occurred one day early.

Started by murphy, October 31, 2008, 10:40:36 PM

Previous topic - Next topic

murphy

I have an event set to happen on October 31.  Last year it worked correctly.  This year it happened on October 30 instead of October 31.  It would appear that the date calculation ignored the fact that this is a leap year.  I assume that my software is up to date since it doesn't try to download a newer version.
Really annoying.

-Bill- (of wgjohns.com)

Just for the record, what exactly is your AHP software version?
-Bill- (of wgjohns.com)
bill@wgjohns.com

In the real world, the only constant is change.

When I'm online you can find me in the Home Automation Chat Room!

murphy

Quote from: -Bill- (of wgjohns.com) on November 01, 2008, 12:49:30 AM
Just for the record, what exactly is your AHP software version?

Version 3.228
I have Smart Macros but none of the three subsequent plugins.

-Bill- (of wgjohns.com)

Quote from: murphy on November 01, 2008, 03:21:28 PM
Quote from: -Bill- (of wgjohns.com) on November 01, 2008, 12:49:30 AM
Just for the record, what exactly is your AHP software version?

Version 3.228
I have Smart Macros but none of the three subsequent plugins.


Thanks for the reply.

Sorry to say I don't have a solution for you, but I am trying to keep a mental catalog of issues that seem to have cropped up with the updates since 3.204.
-Bill- (of wgjohns.com)
bill@wgjohns.com

In the real world, the only constant is change.

When I'm online you can find me in the Home Automation Chat Room!

murphy

On a bright note, the 3.228 update, which is dated May 2008, seems to have fixed the DST switch problem for standalone CM15As.  On October 25 I forgot to connect my stand alone unit to a computer before I went to bed.  The time was still correct the next morning.  October 26 is when the return to standard time would have occurred under the old rules.  Intrigued, I didn't connect the computer on November 1.  The CM15A switched back to standard time this morning right on schedule.  That was a pleasant surprise.


steven r

I also had to rework my Halloween macros for this year. I don't have a repeatable sample of the problem I had but it involved the first macro in an else condition being skipped in a between date range with a flag condition also. AHP may not of liked that some of the elses were downloaded to the CM15A and some had to be run from the PC. In addition to all those variables, I'm only about 95% sure that I had the macro built before Halloween last year. Murphy has been know to creep into my house with less than a 1% probability so 5% of a chance gives him a field day to play. I'm reminded of the Improbability Drive.
BVC let's me tell my camera where to go!
:) Murphy is my beta testing pal. He helps me find problems whether I like it or not. :)

SMF spam blocked by CleanTalk