X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Topic started by: Noam on February 15, 2011, 12:18:07 PM
-
AHP version 3.306 was released today.
Here are the changes:
Version 3.306 Updated 02/14/2011
* Added support for new security modules and hardware.
* Updated Command processing.
You can download the new version here:
http://www.x10.com/support/support_soft1.htm
Here is a link to the revision list:
http://www.x10.com/support/rev_ahp.htm
-
Please note that it is listed as being updated 2/14/2011, but it was only uploaded to the servers today (2/15).
I kept the "official" release date intact, to reduce confusion later.
-
Wow,
An update I did not think we would see one again. Thank you x10 for the continued support. My problem is since a year ago my PC that runs activehomepro is no longer connect to the internet. How can I get the update for that PC. I do have flash drives that I can use on my netbook to copy the file over with. I downloaded the update on the netbook but as suspected when I ran it on my desktop it wants an internet connection. My netbook wont share the internet with the desktop I have window7 starter on the netbook any help would be appreciated.
:-[
-
this should not be hard for them to make a file that downloads correctly.
on xp sp3 it downloaded, installed, and says ver 3.305 still
on win7 64bit it downloads 4% and locks up - from 3 sites.
-
Mike,
Try downloading from the alternate site.
I have better luck with that site! ;)
>!
-
I have had trouble in the past - it was due to caching on my proxy server at work!
Caching in the browser can be an issue, as well.
Try clearing your cache, and then downloading again.
-
I had no trouble downloading it. Once installed it ran fine, all timers and the single macro.
-
When you guys are installing these updates, do you have to re-register everything?
Seems like every time I add a plugin or update, I have problems registering.
-
When you guys are installing these updates, do you have to re-register everything?
Seems like every time I add a plugin or update, I have problems registering.
You shouldn't have to re-register anything when you install and update.
-
As Noam stated:
You shouldn't have to re-register anything when you install and update.
However If you do a lot of updating (testing/debugging of other X10 Apps) it is possible that you'll need to re-register.
So make sure you have the info! ;)
I had to re-register this time but I was updating the SDK and testing some thirdparty x10 software and X10 drivers. ::) :'
>!
-
As Noam stated:
You shouldn't have to re-register anything when you install and update.
However If you do a lot of updating (testing/debugging of other X10 Apps) it is possible that you'll need to re-register.
So make sure you have the info! ;)
I had to re-register this time but I was updating the SDK and testing some thirdparty x10 software and X10 drivers. ::) :'
>!
If I remember correctly, the only time I have ever had to re-register the software was if I did an uninstall of it, and then re-installed it on the same PC. Other than on my test setup (my laptop at work), I don't remember having to do that on any other PC.
-
You do have to re-register if you uninstall your current version before installing the new version. Doing that prevents several versions being installed over each other. If no wacky things (like timers and macros failing) happen you are fine, but you never know. I use the registration code I got in July of 2005 and it's still good.
-
You do have to re-register if you uninstall your current version before installing the new version. Doing that prevents several versions being installed over each other. If no wacky things (like timers and macros failing) happen you are fine, but you never know. I use the registration code I got in July of 2005 and it's still good.
Exactly what I said. Only I haven't had to uninstall when upgrading.
-
I have had trouble in the past - it was due to caching on my proxy server at work!
Caching in the browser can be an issue, as well.
Try clearing your cache, and then downloading again.
nfg. cleared cache. still downloads 4% then times out.
-
I have had trouble in the past - it was due to caching on my proxy server at work!
Caching in the browser can be an issue, as well.
Try clearing your cache, and then downloading again.
nfg. cleared cache. still downloads 4% then times out.
That's really strange.
Since the installer is only a stub, can you download it on another PC, and move it over on a USB drive (or CD, or e-mail)?
-
oh? How? Only stuff that downloads is the little 300k thing you call a stub i think.... of course I download it to other computers but again only the 'stiub' downloads. Please tell me how to download the real McCoy please!
-
oh? How? Only stuff that downloads is the little 300k thing you call a stub i think.... of course I download it to other computers but again only the 'stiub' downloads. Please tell me how to download the real McCoy please!
It's not 300K, the installer is 132K. The installer downloads the rest to do the full install. If you are getting a 300K download it is WRONG!!!!!! I keep EVERY installer for AHP from version 3.175 to version 3.306 on a 250MB Zip Disk.
-
if you send me a private message with your e-mail address, I should be able to e-mail you the stub installer as an attachment.
When you run the installer, it connects to X10's server, pulls down the full version of the installer, and then installs the app.
-
Oh, you are saying just use a stub installed from another machine that worked..... OK - thought you meant I could go somewhere and download the update not just the 'stub.'
Sorry about not saying 'about 300k' I just meant it is a little dinky size thing not the 2-3mb I would expect the real McCoy is. Ya, all 7 tries from both sites are 134,600bytes.
Will hamachi myself the one that downloads right from across town machine at the office (altho it still says ver 3.305) and see if it works here....... isn't that weird..... it downloaded & seemed to install....also still says 3.305 ver tho. Install log for both machines (xp & win7) do not list the installs - looking at previous installs in log file they do not write to the log file until the end of the install so when it fails it doesnt seem to even note why or where.
Any ideas how to find out where the install stops and fails to complete?
-
Yes, the stub basically kicks off the download and install of the full program.
I would suggest clearing your cache, and downloading again. You should get 3.306.
As for the install itself not completing on Windows 7, perhaps you should try running it "as administrator." To do that, simply right-click on the installer, and choose "run as administrator."
-
hmmm... nothing different. just reran one of the 8 stubs downloaded yesterday and this time it went thru and installed.wierd.
-
hmmm... nothing different. just reran one of the 8 stubs downloaded yesterday and this time it went thru and installed.wierd.
so you have 3.306 now?
Might have been something with your ISP, perhaps.
-
yes, 3.306 now. maybe an isp thing for a couple days. thanks for your help.
-
I recently ordered IwatchOut Mobile Pro (which doesn't work with the company's servers, what else should I have expected out of X10?) and when I installed it, the program updated everything. Great, right? Ever since, my Activehome crashes every couple days. Usually, what happens is I wake up in the morning and see that there's a couple hundred error messages stacked up regarding lack of communications with my USB device (the CM15a). For once in my life, I found myself wishing the software writers would have left well enough alone. I had a working system, but after the install, I have these random crashes (yes, I reboot, unplug the interface, etc, but I can't waste hours every day wiping and reinstalling this software) plus I had to redo ALL my timers using the timer-calls-the-macro system that others have mentioned elsewhere.
No more updates, please!
As soon as I can afford it, I'm buying HomeSeer...
-
I recently ordered IwatchOut Mobile Pro (which doesn't work with the company's servers, what else should I have expected out of X10?) and when I installed it, the program updated everything. Great, right? Ever since, my Activehome crashes every couple days. Usually, what happens is I wake up in the morning and see that there's a couple hundred error messages stacked up regarding lack of communications with my USB device (the CM15a). For once in my life, I found myself wishing the software writers would have left well enough alone. I had a working system, but after the install, I have these random crashes (yes, I reboot, unplug the interface, etc, but I can't waste hours every day wiping and reinstalling this software) plus I had to redo ALL my timers using the timer-calls-the-macro system that others have mentioned elsewhere.
No more updates, please!
As soon as I can afford it, I'm buying HomeSeer...
What version did you update from?
If it was prior to 3.302, which was released on 1/10/2011, then you may be having problems with SoftStart modules.
Around 2008, X10.com redesigned the Lamp modules and Wall Switches (the dimming ones), to use "Extended Dim" commands, and "SoftStart". If your modules are the older version, they cannot respond the the newer "Extended Dim" codes.
With version 3.302, AHP switched the default behavior of these modules to use the SoftStart commands. Older modules are now listed under the "Old Lamps (no SoftStart)" category.
The simple test for this is using a hand-held remote, turn the light on. If it dims up to full brightness, then it is SoftStart. If it comes on immediately at full brightness, then it is non-SoftStart.
If you find you have the older modules, changing them to the older type in AHP usually resolves the issue.
In addition, if you have the older SDK installed, you will need to update that to the newest one. The older SDK is not compatible with the newer AHP.
-
As soon as I can afford it, I'm buying HomeSeer...
$0.02
You won't look back.
However HomeSeer isn't flawless, but most of the software team at HomeSeer have been there since the beginning. My biggest gripe with HomeSeer is they have gone to paid support, which is probably necessary as too many users are simply too lazy to read documentation to find out how to do something and call Support asking questions that are clearly answered in the docs. However I think they should have a short period of waiving support fees after every major release. Also I do not know if HomeSeer supports CM15A RF receive or transmit functions.
-
My older version was definitely pre-2011, since nothing had been upgraded for a year or more before that (when I bought the X20 wireless camera setup and monitored home security setup). I tried replacing my modules with the non-dimming ones in the software, but that didn't always work, either. My best results have been with the timer-calls-the-macro method. My thanks go out repeatedly to the X10 forum community, because the people that I get on the phone for support long ago proved to be a substandard resource. Those of you that have powered through this tech and post on the boards are much appreciated!
When we build again, I will abandon X10/powerline entirely. Already as we've added more CFLs to our home, I've had to make adjustments to my system to keep the powerline signals reliable. If I am moving to new tech such as RF mesh like Insteon/Lutron/Zwave/etc, there's no reason to keep subjecting myself to ActiveHome. Just a hard sell to my wife when I mention the $300+ price point of Homeseer. Yikes!
Thanks all for the responses!
-
I wasn't suggesting replacing with the non-dimming modules, but with the "non-SoftStart" versions of the lamp modules (and wall switches). If they were purchased pre-2008, then they are most likely the older model. It has been a common issue here, and is a pretty quick issue to resolve (if that is really the problem).
I recommend testing your modules to see which type they are, and correcting them in AHP if needed.
As for the app crashing, and USB communication errors, there are a number of possibilities with that, as well.
How long is your USB cable? Are you using any type of USB extender to go beyond the "standard" USB limits?
Going beyond the USB design specs (3-5 meters, depending on the USB version) can cause strange results. I had major USB connectivity issues using several different commercial USB-over-CAT5 extenders, too. They would frequently disconnect and reconnect at random, which caused big problems for my CM15A and AHP.
Have you tried replacing the USB cable? I had an issue with a bad cable a few years back, which produced some of the same symptoms you describe. Replacing the cable resolved the issue in that case.
-
I wasn't suggesting replacing with the non-dimming modules, but with the "non-SoftStart" versions of the lamp modules (and wall switches). If they were purchased pre-2008, then they are most likely the older model. It has been a common issue here, and is a pretty quick issue to resolve (if that is really the problem).
would u get mad if I asked u to tell us what the symptoms are we are supposed to have? I have never understood the descriptions previously given for the symptoms. probably 18 of my 25 or so modules are old and not softstart, but i do not believe I have any symptoms, they just seem to work. i do NOT use dimmed commands so is that why I have no problems or symptoms? I use ON or OFF only. It seems if only ON/OFF is used there are no problems or symptoms of not reprogramming to OLD style? Or am I missing something?
-
Symptoms for incorectly configured lamp modules are timers will begin to fail.
It doesn't mater if you use dim, bright, on or off.
All modules should be configured correctly in AHP if possible to avoid issues
>!
-
I wasn't suggesting replacing with the non-dimming modules, but with the "non-SoftStart" versions of the lamp modules (and wall switches). If they were purchased pre-2008, then they are most likely the older model. It has been a common issue here, and is a pretty quick issue to resolve (if that is really the problem).
would u get mad if I asked u to tell us what the symptoms are we are supposed to have? I have never understood the descriptions previously given for the symptoms. probably 18 of my 25 or so modules are old and not softstart, but i do not believe I have any symptoms, they just seem to work. i do NOT use dimmed commands so is that why I have no problems or symptoms? I use ON or OFF only. It seems if only ON/OFF is used there are no problems or symptoms of not reprogramming to OLD style? Or am I missing something?
I'm happy to try and answer your question. It takes a lot to get me mad here. ;-)
The "Extended Dim" codes that the SoftStart modules use by default in AHP are used for ALL brightness settings, even "On" (which is 100%) and "Off" (which is 0%).
If the modules is defined in AHP as one that has SoftStart, then AHP will always send the Extended Dim codes, even for "On" and "Off."
If, for example, you define an Appliance module as a Lamp Module, AHP will try to send the Extended Dim codes, and the Appliance Module will not understand the commands, so it will do nothing.
The same goes for an "Old" (non-SoftStart) Lamp Module. It also doesn't understand the Extended Dim codes, so it also won't respond.
That's why it is very important to properly define all of your modules in AHP. This became especially important with the release of version 3.302, which added support for the SoftStart modules. Any Lamp Modules that were already in AHP were asssumed (by the software) to be SoftStart ones. If they are the older ones, then they won't respond properly until you redefine them as the old style modules.
In general, most modules (SoftStart Lamps, non-SoftStart Lamps, Appliances, etC) WILL respond to a simple "On" or "Off" command. However, AHP won't always send a simple command for SoftStart modules.
If you define a lamp as an Appliance module, which only gets an "On" or "Off" sent from AHP, it probably will work with a timer just fine. However, that's isn't the optimal way to use it. You can also define a dimming module as a non-dimming one (like the "Florescent Decorator Switch").
There is an option for the macros, to "Issue On in place of Bright 100". This option sends an "On" command to those modules, which could explain why the macro worked for you, but the timers didn't.
I suggest that you try re-defining your modules correctly within AHP, and then testing the timers again. I have a feeling that may resolve your issue.
-
My "ON" timers are not working since I upgraded...any suggestions.
Using windows 7 32 bit
-
My "ON" timers are not working since I upgraded...any suggestions.
Using windows 7 32 bit
Once again, if these are Lamp modules (or wall switches), and they are older than about 2008, then they are likely non SoftStart.
You need to re-define them in AHP. Just edit the module, and change the "Lamps" drop-down to "old Lamps - no SoftStart." Then select the module again from the second drop-down.
The tet to see if this will work is to use a hand-held remote, or to to turn on the lights manually in AHP. If they come on immediately, they are non-SoftStart. If they slowly come on to full brightlness (takes about a second or two), then they ARE SoftStart.
Starting in AHP version 3.302, the default behavior for Lamps is to use the SoftStart. If your lamps are older, (and don't have that feature), then you just need to change them to the old type in AHP.
It only takes a few seconds to do each one, so even the most complex setups shouldn't take more than a few minutes to complete.
-
Well I have to say I was at my wits end, and could only place the blame on a Windows update and or a ATI video driver update that caused my white flashing video when trying to use AHP. Going from working just fine to white flashing video overnight just didn't make sense. I tried all the uninstalling and reinstalling I could handle, even restoring from back-ups and whatever else I could think of and for whatever reason, nothing worked.
Tonight is the first I've heard and came across the "Update" for AHP on 2/14/2011 and I about ****. I couldn't believe my eyes, and am wondering is I'm still not dreaming. rofl Anyways, to make a happy ending, I installed the update and it took care of all my issues with the flashing white screen.
-
Automatic update checking within AHP hasn't worked since version 2.204. This has been broken in every later version, so you need to go to the website to check for a newer version.
I've been told by the developers that this is on their list of things to fix.
-
ok, so I took the hour to change most of my fake switches to OLD STYLE. Not sure what should have happened: nothing did. still works more or less as good as it did b4 the changes..... so I am still not sure specifically what this did for me. all (30?) but 1 of my wall switches, lite modules, fake switch modules, were old style and changing them didnt seem to make anything work better or worse. they still work like before in my smart macros and if I click them on or off with a remote.... guess I still dont see what the issue was. sorry for being dense. (:
-
mike the issue was old style light switches and Timers Not Macros.
One other thing, You shouldn't use light modules as Dummy\fake modules.
You should be using standard appliance modules as the fake modules.
-
ok, thanks
-
Version 3.310 was just released.
Here is the link to the new thread:
http://forums.x10.com/index.php?topic=23042.0
I'm taking off the "sticky" property of this thread now.