X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Topic started by: glacier991 on December 21, 2012, 11:41:40 PM
-
We all know the most up-to-date AHP software has some bugs... and once the CM-15 seemed to disappear, I held little hope that there would be any reason for X-10 to revisit it and fix the bugs, let alone add upgrades/updates. But, now (and thank you X-10, as promised) the CM-15 appears to be back, can we expect some "freshening up" of the accompanying AHP software? Or at least bug fixes? Please?
Thanks
Chris Swanberg
-
Not too many official X10 employees frequent here these days.
Hopefully someone at X10 will see this and answer your question.
My gut feeling is nothing will happen. I don't believe they have many programmers anymore.
-
Brian, I fear you may be right. Sad thing is, the rapidity with which they sold their first production run of the "new" CM-15 should serve notice that there is a robust market for their type of HA out there, and with a little attention they could rebuild what their prior benign neglect effectively was killing.
Chris
-
Sad thing is, the rapidity with which they sold their first production run of the "new" CM-15 should serve notice that there is a robust market for their type of HA out there, and with a little attention they could rebuild what their prior benign neglect effectively was killing.
:)%
Very true words.
-
I don't know whether this is the right place for this. If not, I'm sure someone will let me know.
I have been running an x10 system with ActiveHome Pro (CM15A) on a pc running Windows 7 (64bit) for some time with no problems. I have an older version (3.236) with about 5 plugins registered in it. I'd like to upgrade to the newer version of AHP but am not sure of how to go about it. Do I just upload it over the existing version or do I have to completely uninstall the old one first? Then what happens to the plugins that are registered after the upgrade?
Can someone describe the process or point me to a procedure if it already exists? Thanks
-
There is an update file in the software center. For existing installations.
It should update AHP and all the plug-ins.
http://www.x10.com/support/support_soft1.htm
-
Upgrading is as simple as downloading the new version (either the "update" or the "full version"), and installing it over the old one. That will update any installed plugins, too.
One important thing to keep in mind when you upgrade from the version you have:
If any of your dimmable modules (lamps and/or wall switches) are the older ones (without the SoftStart feature - see below for an explanation), you will need to edit the modules, and change the category from "Lamps" to "Old Lamps - NoSoftStart," and then re-select the module type. Mixing both "old" and "new" modules on the same HouseCode/UnitCode combination (ex: two lamps in the same room you want to go on/off together) is not recommended. The modules will not work correctly if you do. In that case, you should either switch the mis-matched modules around so they are all the same type, or define them all as "Old Lamps."
If you aren't sure if your modules have SoftStart or not, see my explanation below (you can skip the rest of this post if you already know what SoftStart is, and how to tell if your modules have it).
Explanation of SoftStart, and the ramifications of picking the wrong module category:
Back around 2008, X10 changed the design of their dimming modules (plugin lamp modules and wall switches), and added in the "SoftStart" function and the ability to be controlled using "Extended Dim" commands. The new design allows you to set a module to a specific dim level directly, without having to go to "full on" first. The new modules will slowly "ramp up" to the desired level when turning on, instead of going on immediately at full brightness (like the older ones). The newer modules will respond to "Extended Dim" commands, but the old ones won't. However, the new modules will still respond to the older "Percent Dim" commands just fine. Unfortunately, they didn't change the model numbers when they changed the design. The easiest way to determine which ones you have (and you might have a mixture of both) is to watch them when they turn on. If they immediately jump to full brightness, they are the older ones. If they "ramp up" to full brightness, they are the newer ones.
Starting with version 3.302, X10 added support for the newer (SoftStart) modules. Since the module numbers are the same between the old and the new, they decided the "Lamps" category should be the newer ones (the ones any current customers would be buying), and added a second category, "Old Lamps - no SoftStart," for the older ones. AHP sends Extended Dim commands to control the newer modules, and it sends Percent Dim commands to control the older ones (the "off" command is still the same for both).
-
Upgrading is as simple as downloading the new version (either the "update" or the "full version"), and installing it over the old one. That will update any installed plugins, too.
I'm still having problems upgrading from version 3.236 to 3.318. I have tried installing over the old version. It seems to go ok but when I try to start AHP afterwards, it gets to the part where it's registering the plugins and stops responding with Windows eventually closing it. I can do a system restore and everything if fine but back on the old version. I've tried it with both the update and the full version. Anti-virus software was disabled. Does anyone have any suggestions?
-
Try backing up all your .ahx files to separate memory then delete AHP 3.236 totally. One that is done, install 3.318 and when it's installed you can then reinstall your ahx files. Good luck!!
-
Try backing up all your .ahx files to separate memory then delete AHP 3.236 totally. One that is done, install 3.318 and when it's installed you can then reinstall your ahx files. Good luck!!
How does that affect the Plugins? Do they have to be registered again?
-
They *might* need to be re-registered.
However, you can try it as a two-step process.
First, back up your AHX files.
Then, REMOVE the AHX file that AHP it trying to open at startup, and it should give a small "file not found" error, but still open up.
If that works, then try opening up that AHX file.
One other thing you can try first, (certainly can't hurt) would be to download and install the full version.
Then, download and install each of the plugins (shouldn't be necessary, they should get updated with the 3.318 install, but try it anyway).
Did you:
1. Download the installer before running it (instead of running it right from your browser's temp folder)?
2. Run the installer "As Administrator"?
3. Try running AHP "As Administrator"?
-
They *might* need to be re-registered.
However, you can try it as a two-step process.
First, back up your AHX files.
Then, REMOVE the AHX file that AHP it trying to open at startup, and it should give a small "file not found" error, but still open up.
If that works, then try opening up that AHX file.
One other thing you can try first, (certainly can't hurt) would be to download and install the full version.
Then, download and install each of the plugins (shouldn't be necessary, they should get updated with the 3.318 install, but try it anyway).
Did you:
1. Download the installer before running it (instead of running it right from your browser's temp folder)?
2. Run the installer "As Administrator"?
3. Try running AHP "As Administrator"?
OK, I tried all of your suggestions some of which I had already tried. And nothing worked until I completely uninstalled the old version. Then I installed the full new version. Everything was ok then. Next I started installing the plugins (Smart Macros, Iwatchout, Onalert and Myhouse). Everything was fine until Iwatchout was installed. As soon as it was installed, AHP would stop working during the plugin registration process and then close. At lease I know what component is causing it. Any ideas on why it may be doing it? Thanks
-
Iwatchout REQUIRES a camera to function, or AHP will NOT start! I have an old Logitec usb camera plugged into my computer, and Iwatchout likes it and AHP starts.
-
Iwatchout REQUIRES a camera to function, or AHP will NOT start! I have an old Logitec usb camera plugged into my computer, and Iwatchout likes it and AHP starts.
Yes, I have a USB webcam that seemed to satisfy the older version of AHP. But it won't satisfy the newer version.
-
HHmmm... well DARN IT! I know I had that problem with Iwatchout and that is what I did to solve the problem.... I'm outta suggestions... sorry
-
Iwatchout REQUIRES a camera to function, or AHP will NOT start! I have an old Logitec usb camera plugged into my computer, and Iwatchout likes it and AHP starts.
Yes, I have a USB webcam that seemed to satisfy the older version of AHP. But it won't satisfy the newer version.
Try getting 3.310. It's stable and can handle both "Old Style" and soft-start modules. It's been suggested 3.318 is a buggy version of AHP.
-
Try getting 3.310. It's stable and can handle both "Old Style" and soft-start modules. It's been suggested 3.318 is a buggy version of AHP.
Dan -
1. 3.310 was buggy, too. They fixed a bunch of those bugs in later versions (while introducing new bugs).
2. I don't know if 3.310 will fix the problem with IWatchout or not. Since you don't use (or have any use for) any of the plugins, you have no way of knowing if that's the case or not.
-
Iwatchout REQUIRES a camera to function, or AHP will NOT start! I have an old Logitec usb camera plugged into my computer, and Iwatchout likes it and AHP starts.
Yes, I have a USB webcam that seemed to satisfy the older version of AHP. But it won't satisfy the newer version.
As far as I know, the IWatchout plugin for AHP needs a camera connected via a VA11A/12A/13A (The VA11A is not supported in Windows Vista/7/8. For those, you would need the 12A or 13A). Some people have reported success with other USB cameras, but X10 certainly doesn't support that in any way.
If you aren't using AHP with a camera, then why install the IWatchout plugin?
You can disable individual plugins by editing the "ahp_plugin.xml" file in the AHP folder, and remove the line for the specific plugin.
for IWatchout, it is this one:
<plugin id="AHXAVX"> href="avx.dll"/>
Removing that line doesn't uninstall the plugin, but it de-activates it. That should be enough to allow you to use the rest of AHP.
Instead of removing it, you can also just change the "plugin" to "noplugin", to see if that works. Installing an update, however, will re-enable the plugin. (so you'll probably have to re-disable them again if you re-install another update afterward).
-
Try getting 3.310. It's stable and can handle both "Old Style" and soft-start modules. It's been suggested 3.318 is a buggy version of AHP.
Dan -
1. 3.310 was buggy, too. They fixed a bunch of those bugs in later versions (while introducing new bugs).
2. I don't know if 3.310 will fix the problem with IWatchout or not. Since you don't use (or have any use for) any of the plugins, you have no way of knowing if that's the case or not.
Noam,
You are wrong about 3.310. I've been using it for over two years with NO problems whatsoever. I did try 3.318 and it did not work, timers were off by 15 to 20 minutes, so back to 3.310 I went.
-
Dan, just because you don't have a problem with it, doesn't mean others don't have a problem with it. They might be using plug-in's which you don't have a need for.
-
Dan; Just because it works fine for you. Doesn't mean it was bug free and worked for everybody else.
So calling the 3.310 version the cure all for everybody is not correct.
-
Has anyone ever posted here that had problems with 3.310? It handles both Old Style and Soft-Start modules. I don't need any of the plug-ins. I have 1 macro that turns off lights with "A5 OFF"on a Mini-Controller. X10 does for me what I want it to do.
-
Has anyone ever posted here that had problems with 3.310? It handles both Old Style and Soft-Start modules. I don't need any of the plug-ins. I have 1 macro that turns off lights with "A5 OFF"on a Mini-Controller. X10 does for me what I want it to do.
Dan, here again just because someone doesn't post here about something doesn't mean they don't have problems with it. They might have done what this forum is for. READ! If they read the answer that someone else already posted why would they post the same thing again? The problem the user has is WITH the plug-ins. Everybody knows by now that you don't have any and don't want any. So, my question would be "why are you posting about something you don't even have and don't want?" Now everyone here knows you have ONE macro.
And as for x10 doing everything you want it to do, Good for you! But this is NOT about you this is about a user that has problems with "PLUG-INS!"
-
@Noam... I was using the Iwatchout plugin to control the P/T's. I have other IP cameras mounted on the P/T and am NOT using the V1x usb interfaces and found out by accident that my Logitec camera was recognized by AHP.
That camera is just hanging behind my computer and I am not using it's video for anything, just to satisfy AHP and Iwatchout, but it IS seen by AHP.
Guess I am just lucky?
-
Try getting 3.310. It's stable and can handle both "Old Style" and soft-start modules. It's been suggested 3.318 is a buggy version of AHP.
Dan -
1. 3.310 was buggy, too. They fixed a bunch of those bugs in later versions (while introducing new bugs).
2. I don't know if 3.310 will fix the problem with IWatchout or not. Since you don't use (or have any use for) any of the plugins, you have no way of knowing if that's the case or not.
Noam,
You are wrong about 3.310. I've been using it for over two years with NO problems whatsoever. I did try 3.318 and it did not work, timers were off by 15 to 20 minutes, so back to 3.310 I went.
Dan -
As others already pointed out (but for some reason I feel the need to say it myself), just because YOU don't experience any problems with 3.310, doesn't mean it is the best version for EVERYONE. At the same time, just because YOU had problems with 3.318, doesn't mean everyone else will, too.
Yes, there were a number of bugs fixed with 3.310, but there were a number of bugs fixed in the 7 versions after it, too. If you're curious, you can see the AHP revision history page here: http://www.x10.com/support/rev_ahp.htm.
-
...I've been using it for over two years with NO problems whatsoever....
That's an interesting claim, considering it is impossible. 3.310 was released on 03/25/2011.
According to MY calendar, you can't make that claim until at least 3/26/2013.
-
@Noam... I was using the Iwatchout plugin to control the P/T's. I have other IP cameras mounted on the P/T and am NOT using the V1x usb interfaces and found out by accident that my Logitec camera was recognized by AHP.
That camera is just hanging behind my computer and I am not using it's video for anything, just to satisfy AHP and Iwatchout, but it IS seen by AHP.
Guess I am just lucky?
Okay, that explanation makes sense.
According to the AHP Revision History (http://www.x10.com/support/rev_ahp.htm), there were a lot of changes that affected the IWatchout plugin between versions 2.326 and 3.318 (or even 3.310). I'm guessing they changed whatever it was that was allowing a non-X10 Video capture device to work.
I don't know if there is another way around this, something that would allow you to use IWatchout *without* a VA1xA plugged in.
I don't know if there is software out there that can "trick" the computer into thinking the VA1xA is connected (since you don't use it anyway), but perhaps someone else here knows of something.
-
...I've been using it for over two years with NO problems whatsoever....
That's an interesting claim, considering it is impossible. 3.310 was released on 03/25/2011.
According to MY calendar, you can't make that claim until at least 3/26/2013.
Noam, this subject is closed rofl
-
Noam, this subject is closed rofl
rofl
And to think; some people actually have to pay for entertainment.