Print

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

[Walt2]

If you were a previous AHP user (Version 3.228 on down) please use this thread to post any differences that you see with 3.236.

Wow, I am having a LOT OF REALLY ODD PROBLEMS now that I "upgraded" to v 3.236 !!!

For example, I have a very simple Timer Event that turns an outside light on at dusk, and turns it off at 11:00PM.  I have been using that Timer Event for many, many years without a problem.  However, upon "upgrading" to 3.236, the outside light turns off at around 8:00PM.  And it isn't a superfluous X10 signal doing it either, because if then manually turn the light back on, it does not later turn off at 11:00PM.    It is like 3.236 has lost all reference to real time.   

Another example, I have another Timer Event that turns an inside light on at 5:45AM each morning.  After "upgrading" to v 3.236, that light turns on, but the chime module that rings when there is motion detected outside, now rings at 5:45AM too.

Again, I am talking about simple Timer Events, not complicated conditional macros with flags or something.

Some really weird stuff is happening with v 3.236 !!!!

How can I get back to v3.228 ? ? ? 

[Dan Lawrence]

Oddly, the only problem I had with 3.236 was a somehow corrupted Christmas file.  Some, but not all timers failed to turn off outside decorations off at 12:30 AM.  I happened to discover it when I looked outside at 6:15 AM the next morning and all the outside decorations were still on.   

I cleared the interface, shut AHP down, deleted the offending file, reopened AHP and created a totally new file with all the modules and timers, saved it with the same file name as the old one and uploaded it to the CM15A. 

ALL timers work properly now, on and off times are correct. 

[Tuicemen]

Walt2  
You can get back to 3.228 by installing 3.204 then let it auto update. It won't see 3.236 At least mine didn't on testing!

[Dan Lawrence]

Since there is a consensus that 3.236 is another buggy release like several older buggy ones in the AHP Software History, I backdated to 3.204 and upgraded to 3.228 from it.  Better safe than sorry.

[Walt2]

Since there is a consensus that 3.236 is another buggy release like several older buggy ones in the AHP Software History, I backdated to 3.204 and upgraded to 3.228 from it.  Better safe than sorry.

Me too.   I went back to ver 3.228, and all my new problems disappeared!   

I don't think my .ahx file was bad because that file didn't change when I went from 3.228 to 3.236 (I never did a re-save).  Plus, I would hope that such a minor version change (going by their numbers), would maintain full .ahx file compatibility.

Though, let me ask, those of you who aren't having a problem with 3.236, are you running with your PC constantly connected to the CM15A?  The reason I am asking, is that when I was attempting to debug my 3.236 problems, I left my PC running with the Activity Monitor open with the hopes to catch an erroneous X10 command.  During those 24 hours, I didn't have a problem.  However, when I disconnected my PC, the problem resurfaced over the next 24 hours.  Now, I am not sure if that was just a conscience or not, and I was just too fed up with 3.236 to want to debug it any further.

[BaBaLou.]

Hi Walt2,
I guess I am one of those NOT having a problem with 3.236. YES the CM15A is connected 24/7 to the computer running XP. I have tried running the system so far with AHP running and not and so far no problems for me. I did not and wont be trying to  disconnect the CM15A from the computer and seeing what happens. I do have have it set up with Jeff's wonderful XTB-IIR and a V5782R32 transceiver. The system is running flawlessly and I can only say that 3.236 is working for me.

Though I do have 3.228 running on my system at the business and dare not yet upgrade to the 3.236 yet. I am still experimenting with VA12A on that system compared to the
home system.

It seems the point you make about having the CM15A connected or not may hold some ground. Those having the same problem may help to answer that one.

UPDATE: I will try it with computer off for a day a remove any video or email macros and then will see. I guess when I closed AHP on the computer It would almost be the same scenario since the system still worked correctly for me but that was only for a short time. will try for a day or so and get back to you.

[stevex10]

I have version 3.228 and the only reason why I updated to that was because the whole daylight savings issue. I now seem to see that my timers tend to go away after about 4 or 5 days. Not sure exactly how many days it takes but this xmas I have 3 differnt timers for lights around the house. I have to re-download to the CM15 and all is fine for a few days. I have my dawn/dusk resolution at 8 days~1.5%. I am now trying to see what "daily~13%" will do. So far only a day has passed and so far so good.

The day they all quit working. I can still use my remotes and all sensors seem to be fine.
I'm using XP and my computer is not connected all the time. All my timers reside in the interface.

Thanks and I hope there's a fix.

[Dan Lawrence]

What version did you upgrade from?  I have 3.228 (upgraded from 3.204) and ZERO problems.  This particular topic is for version 3.236, which I did have (downgraded to 3.204, than upgraded to 3.228) which appears to be a buggy release.

[Walt2]

I have version 3.228 and the only reason why I updated to that was because the whole daylight savings issue. I now seem to see that my timers tend to go away after about 4 or 5 days. Not sure exactly how many days it takes but this xmas I have 3 differnt timers for lights around the house. I have to re-download to the CM15 and all is fine for a few days. I have my dawn/dusk resolution at 8 days~1.5%. I am now trying to see what "daily~13%" will do. So far only a day has passed and so far so good.

The day they all quit working. I can still use my remotes and all sensors seem to be fine.
I'm using XP and my computer is not connected all the time. All my timers reside in the interface.

Thanks and I hope there's a fix.

Yep, timer problems with  3.236.  And the problems don't show up immediately.

Sounds very familiar!   

[Dan Lawrence]

You copied stevex10's post, but mentioned 3.236, when he said he has 3.228.    He has yet to reply to my post's questions.

[USdangerboy]

On the strange stuff, I must agree!!

I have a VERY simple setup with a macro on a 24hr EE sensor to raise the kitchen lights, only if after dusk, by 30%, wait 4 minutes (this is the sensor delay) then dim 30%.  It works off of a flag to know it's the one that did the dimming and the flag is cleared by a DuskSetupMacro. 

So at Dusk, a macro runs to clear the flag for all macros, and set the lights accordingly. 

When every sensor fires, they check the flag, if clear then fire, and set the flag.  When the delay is over, dim the lights and clear the sensor.  Simple and efficient, SO FAR!!!

Now, I get this strange issue where the lights now dim to zero and raise to 100 then dim to 0 then raise to 100 ... it's a "flashing" kind of thing ... anyone get this?!?

[Walt2]

You copied stevex10's post, but mentioned 3.236, when he said he has 3.228.    He has yet to reply to my post's questions.

Possibly, I misread it.  Yes, he mentioned 3.228, but also added that he updated.

[USdangerboy]

How do you get the previous version?

[Walt2]

I restored the entire "C:\Program Files\ActiveHome Pro\" directly from a backup copy I have with 3.228.   Also, you might see if you have a Restore checkpoint from just before you updated to 3.236.

[Tuicemen]

How do you get the previous version?

As I mentioned before You have to revert to 3.204
it will overwrite the 3.326 version.
Once that is done on start up it will detect there is an update to 3.228( it won't see 3.236) let it update  and your set!