X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Topic started by: Noam on January 20, 2011, 08:38:39 PM
-
AHP version 3.305 was released today.
Here are the changes:
Version 3.305 Updated 01/20/2011
* Fixed possible day/month inversion for custom Holidays in non-US region computers.
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
-
3.305 didn't fix the problem with SoftStart module dim status not being saved when exiting AHP.
Still waiting for that to be corrected.
-
Installs and runs but crashs after I load plugins B:(
-
Installs and runs but crashs after I load plugins B:(
I'm beginning to think the assorted plug-ins are the culprit. B:(
-
I have not tried loading plugins first, I'll try that next. I thought I had read this cured crashs with other version(s) ??? ???
-
I upgraded all my plugins first and then upgraded AHP. AHP did crash when trying to download timers and macros, but after using windows task manager to kill AHP and X10nets no more crashes. One thing that did happen with this upgrade and changing the older lamp modules to non-soft start, any macros using LM15a socket rockets had the "on" state change to "off". Drove me bonkers B:( till I examined each macro one by one. So far everything is working OK - fingers crossed!!!
DeliBaker
AHP 3.305 and all plugins except MyGarage/MyGarage Pro & iWatchMobile
-
Guess what. 3.305 is little more than 3.304 with some window dressing. I tried it and just like 3.204, it failed to properly run timers. NOTHING turned on according to the timers. SOOOO, back to 3.296 again, that works like AHP should.
-
I haven't noticed issues with timers as I have a hourly one set to annouce the time.
However I did notice my living room light failed to come on the last 2 nights.
I had thought this was because of my switching back and forth from different version of Windows while debugging a program.
I'll have to watch this one more closely to night!
>!
-
I keep virtually every version of AHP on a 250MG Zip Disk and I just moved 3.304 and 3.305 into the Buggy Versions folder along with 3.236 and one other version.
-
I haven't noticed issues with timers as I have a hourly one set to annouce the time.
However I did notice my living room light failed to come on the last 2 nights.
I had thought this was because of my switching back and forth from different version of Windows while debugging a program.
I'll have to watch this one more closely to night!
Other than one timer on Friday evening that failed to run, everything else has been flawless with my system since I solved by USB issue. Even before that, my CM15A would run the timers (unless the flaky USB connection locked it up), just the PC wouldn't see it. I've been upgrading to each version as they have come out, and haven't noticed any issues with my timers.
-
NOTHING turned on according to the timers.
I realize your setup is very basic Dan so when you say NOTHING can you be more specific?
were they light, or appliance modules that failed or Both.
I've notice my lamp module in the living room failed to come on! This was on a timer! ???
I'll have to look at it to see if it is set as a soft start or not!
Hummm where is that setting! ???
>!
-
There is now a separate tab in AHP for lamp type devices and another one for older non soft start lamp types.
So I would think any module now in the main lamp tab would be soft start.
-
Thanks Brian,
I don't know why I couldn't see that! ::) :'
Now to see if that fixed the timmer issue!
The X10 programmers weren't thinking when they set that up! ::) :'
This means anyone with a old setup has to reprogram their light modules in their AHP setup!
>!
-
NOTHING turned on according to the timers.
I realize your setup is very basic Dan so when you say NOTHING can you be more specific?
were they light, or appliance modules that failed or Both.
I've notice my lamp module in the living room failed to come on! This was on a timer! ???
I'll have to look at it to see if it is set as a soft start or not!
Hummm where is that setting! ???
>!
The timers are set for 40 minutes before dusk, when my wife came home at 5:15 not one light in the house was on. Every light in the Living Room, Dining Room, Breakfast Room and 2 lights outside failed to light.
When I backdated to 3.296, all timers worked as setup.
-
I wounder if you do the update from a version before the soft start modules where split out. To a newer version that does. The lamp and wall switch definitions get messed up.
-
Dan: the X10 programmers in their wisdom added soft start modules and defind them as regular lamp modules they made a new category for old non soft start lamp and switches.
A better idea -:) would have been for them to make a new module type for the new softstart!
If you update to a version with softstart you must reconfigure all your lamp module types to old non softstart! B:(
A picture is worth a thousand words!
>!
-
I wounder if you do the update from a version before the soft start modules where split out. To a newer version that does. The lamp and wall switch definitions get messed up.
A good programmer would have included an automatic, or at least a manual, conversion routine to handle this switch definition change.
Back compatibility with already existing .ahx files should really be an important requirement for any AHP upgrade. :'
-
Problem could be. Many never saw the wiki fix to call them LM14As. So they where LM465s and they don't ID what type they are. Insteons do. ;D
-
I use the same .ahx files. I only have 1 soft-start wall switch in in upstairs room that has no timers. Everything else is non soft-start modules. I have 2 soft-start modules (marked with a SS in indelible black ink) in my Spare Box that will probably never get used. All modules and wall switches are ones I've been using since the early days (mid-1980's) and every one works fine. X10 still needs to beaten with sticks for not changing the module numbers for soft-start modules.
-
I use the same .ahx files. I only have 1 soft-start wall switch in in upstairs room that has no timers.
Well that is one reason why your timers failed!
But there seems to be a issue with the dusk setting maybe even the dawn setting! I'll have to check that one as I don't usethe dawn setting! ::) :'
-
Since I read here that if you use 3.304 or 3.305 you have to rebuild every .ahx file you have it's another reason to avoid 3.304 or 3.305. Since I have 10 regular .ahx files that are used during the year plus 3 that are "special" .ahx files that are only used at certain times of the year or for special occasions, that's a LOT of .ahx files to be totally rebuilt. X10 "dropped the ball" again, they should have only added the soft-start modules in a list and left all the "old style" alone.
Good old 3.228 and 3.296 had none of that "hoo-how". B:(
-
Well I'm sure X10 isn't going to make it so old users don't have to update they're AHX file now!
Hey but stranger things have happened! rofl
-
I agree that this wasn't the best course of action to have taken.
However, the problem started a few years ago (before the current developers came on board), when the hardware engineers released a new module, but used the same number as the old one. Since the two are not 100% compatible, they should have changed the module number.
There should be a way for AHP to take an existing AHX file, and "convert" it so that any "lamp" modules become "old lamp" modules.
It is a one-time conversion, but for someone like Dan, with a dozen or so AHX files, it is a pain to do manually.
-
It is a one-time conversion, but for someone like Dan, with a dozen or so AHX files, it is a pain to do manually.
Well Dan has a small setup!
Many of us use multiple AHX files and some very complicated setups with more then two dozen lamp modules in each AHX file.
The fact is all the long time users had already learned to work with the smartstart modules and now we have to make changes again! B:(
The damage is done! Changing it back or making a AHX conversion is only going to add to the problem now!
The Programmers know this forum exists!
How difficult would it have been to start a simple request for suggestion thread? ??? ::) :'
But then X10 could say "Hey we're not paying for that idea! It's not yours!" ::)
-
Just for the record, my system isn't small, I have 32 modules of various types in my system 24/7/365/366 days, at Christmas time add 7 more modules (3m lamp and 2 appliance).
Just because I don't need or use any plug-ins doesn't mean I have a small system
-
I didn't mean to demean your setup Dan, but there are users that have over 200 modules in there setups!
256 is the maximum but even that could be stretched if one was creative, so by comparison your setup is on the small side.
>!
-
It does for us what we want it to do. My wife loves it, we NEVER come home at night to to a dark house. My only wish is for a dual module (wall switch type) that would control both the fan and the lights for our Dining Room fan/light. It would need a appliance module for the fan and a light switch to control the fan. If x10 or somebody here could create one, I'd gladly pay it!!!
-
It would be nice if X10 made a "Fan Module" of some sort. Would be nice as well as many other devices that would remove an obstacle or two for this person or that person. I am sure the folks at X10 like money as well as the rest of us... so they must think there isn't any money in it for them.
I found this: The Hunter Fan 27185 Light Remote Control is equipped with separate buttons for 6-fan speeds and an instant off. You'll also enjoy the option of full-range light dimming. Manual light operation is also possible with the wall switch access plate. A unique switch plate holder is included with this remote control.
It would be simple enough to buy one fan and an extra remote (http://www.amazon.com/Hunter-27187-3-Speed-Dimming-Originals/dp/B0014A13WO/ref=acc_glance_hi_ai_-2_t_1). Then hack the extra remote with Universal Modules.
I control a simple tower fan using a IR PowerMid device and a USB IR device on my HA PC. There is always another way to get to separate the fur coat from the kitty.
-
It would be nice if X10 made a "Fan Module" of some sort. Would be nice as well as many other devices that would remove an obstacle or two for this person or that person. I am sure the folks at X10 like money as well as the rest of us... so they must think there isn't any money in it for them.
I found this: The Hunter Fan 27185 Light Remote Control is equipped with separate buttons for 6-fan speeds and an instant off. You'll also enjoy the option of full-range light dimming. Manual light operation is also possible with the wall switch access plate. A unique switch plate holder is included with this remote control.
It would be simple enough to buy one fan and an extra remote (http://www.amazon.com/Hunter-27187-3-Speed-Dimming-Originals/dp/B0014A13WO/ref=acc_glance_hi_ai_-2_t_1). Then hack the extra remote with Universal Modules.
I control a simple tower fan using a IR PowerMid device and a USB IR device on my HA PC. There is always another way to get to separate the fur coat from the kitty.
Nice idea, Dave, but a bit too complicated for what I'd like. I'll stick with what I have (one standard light switch and two chains) unless x10 decides to make the module. (Fat Chance B:( )
-
It does for us what we want it to do. My wife loves it, we NEVER come home at night to to a dark house. My only wish is for a dual module (wall switch type) that would control both the fan and the lights for our Dining Room fan/light. It would need a appliance module for the fan and a light switch to control the fan. If x10 or somebody here could create one, I'd gladly pay it!!!
Ideally, they should have a "lamp" module for the light, which would allow dimming, and a three-level dimming module (most ceiling fans are three-speed).
The only problem is that if you want to use CFLs in your fan, you'd need an on/off (non-dimming) lamp module.
-
The X10 wiki was even updated to reflect the Soft Start list of modules in the later AHP versions.
http://kbase.x10.com/wiki/Newer_Wall_Switches_and_Preset_Dim
-
Nice idea, Dave, but a bit too complicated for what I'd like.
Thx.... and I know what you mean. I don't feel compelled X10/automate everything in my home ether. But this time of year (around here) the weather can restrict many of my normal activities. I often refer to this time of year as "Automation Season". Sometimes I create an automation project... merely because I CAN. To me... that's the hobby side of X10. Constructing a new project or adding a new feature to an automation setup exercises our X10 skills and keeps the interest alive.
A project that sounds too complicated.... but looks good on paper... can be a great bit of entertainment during these long winters.
-
I found a new way to convert old .ahx files to work with 3.305. Open AHP 3.305 and load an old .ahx file. Room by room, click on any module you need to change. For Lamp Modules, right click on the module and change it from Lamp to Old Lamp. You can do the same process for wall switches. For any lamp or wall switches that are soft-start and using the LM14A to control it, you can make them regular lamp or wall switch modules.
I've already converted 8 ahx files that way. Saves a bunch of time, about 6 minutes per .ahx file.
-
I found a new way to convert old .ahx files to work with 3.305. Open AHP 3.305 and load an old .ahx file. Room by room, click on any module you need to change. For Lamp Modules, right click on the module and change it from Lamp to Old Lamp. You can do the same process for wall switches. For any lamp or wall switches that are soft-start and using the LM14A to control it, you can make them regular lamp or wall switch modules.
I've already converted 8 ahx files that way. Saves a bunch of time, about 6 minutes per .ahx file.
How is that "new"? THAT's the say that we originally were doing it, but you said you had too many modules and too many AHX files to do it that way. What method were you using BEFORE doing it this way?
-
I found a new way to convert old .ahx files to work with 3.305. Open AHP 3.305 and load an old .ahx file. Room by room, click on any module you need to change. For Lamp Modules, right click on the module and change it from Lamp to Old Lamp. You can do the same process for wall switches. For any lamp or wall switches that are soft-start and using the LM14A to control it, you can make them regular lamp or wall switch modules.
I've already converted 8 ahx files that way. Saves a bunch of time, about 6 minutes per .ahx file.
How is that "new"? THAT's the say that we originally were doing it, but you said you had too many modules and too many AHX files to do it that way. What method were you using BEFORE doing it this way?
The answer is NOTHING!!!! I never did use 3.305 before as timers would not work, but now they ALL work. Plus you can convert a .ahx file in about 6 minutes. Plus you can get rid of every LM14 module you used for soft-start modules and wall switches. The plus to doing it this way is you don't have to use a text editor to make changes.
-
... I never did use 3.305 before as timers would not work, but now they ALL work. Plus you can convert a .ahx file in about 6 minutes. Plus you can get rid of every LM14 module you used for soft-start modules and wall switches. The plus to doing it this way is you don't have to use a text editor to make changes.
Dan -
I guess I misunderstood. I though that you weren't using 3.305 because it was too much work to go through all of your AHX files, and change the module types. That's why I looked into editing the AHX file directly. I figured that for really big files, using a "search and replace" method on the AHX file would be faster than manually changing each module within AHP.
I'm glad to hear that 3.305 is working for you.
-
Quick question - is there a reason that New AHP Version 3.304 Released 1/14/2011 (http://forums.x10.com/index.php?topic=22352.0) is stickied at the top of this forum, rather than this thread?
-
Because 3.305 was issued AFTER 3.304 was.
-
Quick question - is there a reason that New AHP Version 3.304 Released 1/14/2011 (http://forums.x10.com/index.php?topic=22352.0) is stickied at the top of this forum, rather than this thread?
Because I'm not a moderator, so I can't sticky/unsticky threads.
-
Will the 3.05 work with Windows 7 64bit without having to use XP settings? My old compuer craped out xp and I need to get a new one.
Thanks
Randy
-
Will the 3.05 work with Windows 7 64bit without having to use XP settings? My old compuer craped out xp and I need to get a new one.
Thanks
Randy
I've been running AHP on windows 7 Pro 64-Bit for over a year now. Started with version 3.236 on that PC (that was the most current version when I migrated over to that new PC), and have been running fine (no Windows issues) ever since. I've upgraded as each new version came out, and I'm on 3.305 with no problems.
-
Quick question - is there a reason that New AHP Version 3.304 Released 1/14/2011 (http://forums.x10.com/index.php?topic=22352.0) is stickied at the top of this forum, rather than this thread?
Fixed. It was just one of those things that slipped threw the cracks!
>!
-
Quick question - is there a reason that New AHP Version 3.304 Released 1/14/2011 (http://forums.x10.com/index.php?topic=22352.0) is stickied at the top of this forum, rather than this thread?
Fixed. It was just one of those things that slipped threw the cracks!
>!
Easy to see how that happened. For a few weeks, we were getting updates faster than we could report them, even. (One of us would report a bug or two, and all of a sudden there would be a new release).
-
Question
I am running AHP 3.3.01 and when I go to HELP and "CHECK FOR UPDATES", I get a box that states I have the latest version and no updates are needed?
And when I was looking for another problem on this forum, I came across this?
Just wondering why my AHP doesn't know there were 4 updates that I didn't get.
??? ???
Dave
-
Maybe just the way it is working these days.
I had 3.228 and it never flagged any updates for me either.
-
I believe 3.228 was when the "Check for update" stopped working!
It is listed as a known bug!
>!
-
I believe 3.228 was when the "Check for update" stopped working!
It is listed as a known bug!
>!
Correct! 3.204, released on 7/10/2006, was the last version where the "check for update" actually worked.
3.228, which was released on 5/9/2008, was unable to find the next version, 3.236, which was released on 9/5/2008.
So, the "check for update" function has been broken for nearly 3 years (since 2008).
-
Sounds familiar as I used 3.228 from its issue to 3.296 and 296 had the same thing as does 3.306. Seems a bit strange that nobody at X10 programming has never caught on in three years.
-
I actually asked one of the developers about this a few months back.
He told me that AHP goes out and checks for a certain file on X10's servers, to determine if there is an update or not.
Apparently, that file isn't getting updated properly (or the format of it changed, or something).
It is on their list to fix it (or so they say), but there is no way to know when (or if) it will ever get fixed.
EDIT: It looks like it makes a call to "http://software.x10.com/cgi-bin/checkfornewrelease.cgi", with a HEX value after the question mark. I'm guessing that hex value has something to do with the current version number.
However, that file doesn't exist, and you get dumped to the homepage.
I'm willing to bet that's a big part of the problem with the "check for updates" function not working.
-
I actually asked one of the developers about this a few months back.
He told me that AHP goes out and checks for a certain file on X10's servers, to determine if there is an update or not.
Apparently, that file isn't getting updated properly (or the format of it changed, or something).
It is on their list to fix it (or so they say), but there is no way to know when (or if) it will ever get fixed.
EDIT: It looks like it makes a call to "http://software.x10.com/cgi-bin/checkfornewrelease.cgi", with a HEX value after the question mark. I'm guessing that hex value has something to do with the current version number.
However, that file doesn't exist, and you get dumped to the homepage.
I'm willing to bet that's a big part of the problem with the "check for updates" function not working.
The only problem with my theory is that it seems that the function worked in 3.204, even after it didn't work in later versions (one could still install 3.204, and upgrade to 3.228, but couldn't go further).
I suppose I could take the time to roll back to 3.204, and then try to sniff again, and see if the request is different. It is just a bit of a pain to do, that's all.
-
I suspect not. The programmers that built 3.228 are long gone and I also suspect that every version after 3.228 were built on the "bones" of 3.228. The only "changes" in 3.305 and 3.306 are the Lamps (Soft-Start) and Older Lamps (No SoftStart).
-
Well, I got an e-mail from the developers yesterday about this.
They said that the problem is entirely on the back-end, and would not require any changes to AHP to correct.
They told me they were actively working on it yesterday, but I didn't get any ETA on when it would be fixed.
In the meantime, it isn't too hard for those of us who frequent the forums to find out about new updates. I usually post them as soon as I find out about them. (The developers sometimes give me a heads-up before the updates are posted to the server).