New AHP Version 3.236

[USdangerboy]

My problem is, I started out with the latest version, on a new computer (lost prior software, so I only have the latest copy). 

I'm just trying to fix this flashing problem (NO, I'm not the flasher ... I'm the flashee!).  Seems my macros work fine for a while, then go haywire every now and then.

EE sensor is set to ON command macro -> Check flag 2, if clear, raise lights 30%, SET flag 2 ...
EE sensor is on 24 hr motion, so it keeps firing ON command during motion, but macro fails flag clear check, so is ignored.

EE sensor eventually stops detecting motion, does delay, 4 minutes, sends OFF command ...
EE sensor is set to OFF command macro -> If flag 2 SET, then dim lights 30%, CLEAR flag 2.

Now what started happening is the ON command is ignoring the flag state sometimes, to wit, the EE ON command raises lights 30%, then again, then again and THEN, it dims to 0%, then raises lights to 100% then back to 0% and so on.  It's a cool effect, but kind of confuses my guests :-)

I reloading the unit and all the basic stuff, so does this behavior sound like a VERSION problem soluble by downgrading?

Thanks in advance!!

[Tuicemen]

I reloading the unit and all the basic stuff, so does this behavior sound like a VERSION problem soluble by downgrading?

What do you have to loose? 
Version 3.236 has caused some strange things to happen for many. This many be another bug!
Back up your AHX file to a different folder (drive is better) do the dowload revert to prior version and test if it fails reload newest version!

[USdangerboy]

Not much I suppose.

Perhaps it is possible to determine FLAG STATUS programmatically via SDK?  Any ideas there?

I'm very close to using my own app anyway, still working on SQL logic, should be just a few more years, LOL. 

In the interim, I'll ask the lazy mans question, where is the download list for previous versions :-)  Will the 3.204 link you posted earlier work, it says its an upgrade?

THX T-men!

[Tuicemen]

The SDK will not see AHP flags but you can create your own in the SDK. You'll still need a good version of AHP if you plan on loading any AHP macros/timers onto the CM15A
I suppied the link to previous versions in previous posts!  yes it works as a down grade too!
If you want even earlier versions the links are available doing an Advanced Search! 
Dig a little deeper and I'm sure you'll find another method! 

[Dan Lawrence]

Not much I suppose.

Perhaps it is possible to determine FLAG STATUS programmatically via SDK?  Any ideas there?

I'm very close to using my own app anyway, still working on SQL logic, should be just a few more years, LOL. 

In the interim, I'll ask the lazy mans question, where is the download list for previous versions :-)  Will the 3.204 link you posted earlier work, it says its an upgrade?

THX T-men!

That file repository ( http://software.x10.com/pub/applications/activehome/) contains various versions of AHP.  3.204 there is the installer for that version of AHP. I got it when I had upgraded to 3.236 and found it was buggy (at least for me), so I got 3.204, installed it over 3.236, then upgraded to 3.228  though the upgrade link in AHP.

[USdangerboy]

Thanks T-Men/Dan, actually, strangely enough, after I installed the iWatchOut software, the problem went away, well, for the last day. 

Go figure.  But if it comes back, I'll follow your lead on the downgrade!

This forum is excellent!!

[PajamaGuy]

Well I finally did something right!  ...and at the right time!

Before running the link to downgrade to 3.204, I saved a backup of my AHX file.  I ran the downgrade (downdate?) and then let it run it's update to 3.228, and restarted.

My security modules were corrupted and not installed.  All of them.

I opened the backup, with baited breath, and there they were!!!!!!!!!!!!!!!

Backup paid off!

[x10dude]

Alright, I've been using 3.236 for the last month or so (when I first got into X10) and had been having LOTS of problems (macros not working, AHP faulting and closing after a day or two, timers going wacky, etc., etc.)

After reading all feedback on this and other posts, I moved to 3.204, which subsequently updated my system to 3.228.

Now, all of my security modules have disappeared from AHP (except for my DS7000 and powerhorns). Does this mean that I need to re-install everything?

I know it's been asked again and again, but does ANYONE know what the differences are between .236 and .228? Because I bought everything at the same time (last month), I don't know whether .228 supports all my components which, as I already noticed, X10 updates periodically w/out changing part numbers or anything that identifies the updates.

Thanks,

Frank

[steven r]

...does ANYONE know what the differences are between .236 and .228? ...

3.228 works more reliably as 3.236 has some known bugs. However, to get the best video with the VA12A I believe you need version 3.236.

[Puck]

Now, all of my security modules have disappeared from AHP (except for my DS7000 and powerhorns). Does this mean that I need to re-install everything?

If you are referring to door/window sensors (DS10A) and/or security motion detectors (MS10A), version 3.204 does not support those. What you probably need to do at that point is reinstall your OnAlert plug-in to bring your version to 3.206, then upgrade to 3.228. If you have your original backup copy of the *.AHX file, your security sensors should then appear.

[x10dude]

Thanks Puck, Steven

Fortunately, I did keep a copy of my *.AHX file. I put it back on the installation folder and now, I do see my door/window sensors again.

As for the video, it's true, now ALL of my cameras (XX16A) simply flash a white screen. I've reinstalled them to no avail. BTW, I use the VR38A receiver and the VA12A video module.

This really sucks. It seems that if I wanted support for my newer hardware, I have to have 3.236. However, with all the bugs, I can't reliably run my system 24/7. As I mentioned, AHP gives a GPF (general protection fault for those non-windows programming folks) after a day or two. Then, all my stuff is out of wack and need to reboot windows and reprogram a few things from scratch.

If I wanted reliability, I'd have to go to older versions, but give up my newer hardware - what gives?

Any other ideas? One of the reasons I got everything I did is to be able to use all my hardware.

Thanks all..

[steven r]

...If I wanted reliability, I'd have to go to older versions, but give my newer hardware - what gives?...

Sadly I believe we'll have to hold our breath and pray X10 releases an update that fixes things soon.

My guess is that the update to support the VA12A was from an earlier version of AHP than version 3.228 as I can't imagine how adding driver improvements for the VA12A could of added as many bugs as version 3.236 has. i.e. How could changing a a video driver interface effect unrelated pluggins and timers?

[Puck]

This really sucks. It seems that if I wanted support for my newer hardware, I have to have 3.236. However, with all the bugs, I can't reliably run my system 24/7.

Another example of how hard it is to help and support other users. X10 has really made a mess of the AHP software vs hardware integration. If they would at least test any changes they make and then provide information to the users & potential buyers of what versions work and don't work with each other, it wouldn't be so bad. Hopefully someday they will do the right thing and fix this mess.

[steven r]

...If they would at least test any changes they make...

Yes it is sad at times. While beta testing should never be a substitute for good alpha testing, I'm sure there are many of us that would be willing to test out things. Most likely for free and almost definitely in exchange for free swag. It really is hard to see how so many bugs could just appear with an update.

[x10dude]

Based on everything that I've been able to debug, it appears that the video driver is actually the GPF culprit, which means no cameras for me!

I admit that I'm guilty for not testing on time though. I took my time designing my architecture that I didn't get a chance to test everything before my 30-day trial period - darn!

On the other hand, I guess if I had to choose between having those crappy cameras work and getting a text message from AHP when someone breaks into my house, I'd choose the latter - not that I have choice.

I agree that beta testing would really help, but is there anyone at X10 that actually listens to their customers? It seems they only hire salespeople, who will do just about anything ("buy 1, get 10 things free", "porn sells", etc.) to get the merchandise out the door, but nobody that really knows much about programming and the like works there.

Regards,

Frank