X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Help & Troubleshooting => Topic started by: s0urc3f0ur on December 22, 2011, 06:15:43 PM
-
I have a macro that I run that used to turn my living room lamps on at the same time. but since the update to AHP, they now turn on one at a time, i.e. one than the other. I 've reverted back to version 3.306 but still the same thing. Does anyone remember what version allows for this?
-
Are they all on a different X10 Address?
-
no. I didnt change anything. the only thing that changed was I had to reinstall ahp and and got the updated version. and now they come on one at a time. it really messes up my theater lights dimming effect. it's not as impressive when it's one then the other and not at the same time. :'(
-
I'm thinking one is softstart the other the old non softstart.
-
Are they on the same HouseCode/UnitCode, or on separate ones?
What does the Activity Log show for that macro when it runs?
-
THing is it worked before the update. my activity log says: transmit b2(left lamp) b off, transmit b1(right lamp) b off
-
My guess is the old version was one before soft start and the new version is 3.318 and the ahx file is from the old version. The only way all 3 lamps would come on all at the same time is if all are on the same house and unit code. s0urc3f0ur needs to use the Lamps and Older Lamps (no SoftStart) for each type of modules he has and resave his .ahx files.
-
I just changed them to older lamps and I still get the same effect
-
Dan, I'm using a smart macro for this called living room on.
-
1. How are the lamps defined in AHP (are they all defined as "Lamps," "Old Lamps (no SoftStart)", or "Appliances")?
2. Unless you need to be able to control them separately, it is better to put them on the same HouseCode/Unitcode. If you do need to control them separately, however, you'll need to keep them on their own UnitCodes, though. In any case, make sure they are on the same HouseCode, at least.
3. In a macro, units of the same type being sent commands one after another (with no delays in between) get grouped together.
For example, it SHOULD send "B2, B1, B off". In that case, B2 and B1 "wake up" and listen for the next order, which they both react to at the same time.
However, it seems like in your case AHP either has delays between the actions in the macro, or the modules aren't all defined as the same type in AHP. (It is very much NOT recommended to mix module types (SoftStart, Non-SoftStart, Appliances) on the same HouseCode/UnitCode combinations).
So, it is sending something like this instead: "B2, B Off, B1, B Off). In this case, only B2 "wakes up" before the first "B Off," and B1 doesn't turn off until the second one.
So, check your module definitions, and check your macros again. The answer might be in there somewhere.
Also, empty the trash in AHP. Stuff in there has been known in the past to cause some issues.
-
as of now the lamps are defined as old lamps no soft start. I do need to control them seperatly. like I said this worked before the update. I had to re-install AHP(it wouldnt open) and now it doesnt, even reverting to an older version(3.306) doesnt fix it. I did empty the trash and still nothing. The only thing I can think of is that the file is corrupt, it actually doesnt register in my un install programs list. The name is there but no icon and when i click on it to unistall it says that it may have already been removed and asks me to delete it from the list. I had to delete the file folder to remove it before I reinstalled.
-
as of now the lamps are defined as old lamps no soft start. I do need to control them seperatly. like I said this worked before the update. I had to re-install AHP(it wouldnt open) and now it doesnt, even reverting to an older version(3.306) doesnt fix it. I did empty the trash and still nothing. The only thing I can think of is that the file is corrupt, it actually doesnt register in my un install programs list. The name is there but no icon and when i click on it to unistall it says that it may have already been removed and asks me to delete it from the list. I had to delete the file folder to remove it before I reinstalled.
It is possible your AHX file is corrupt.
You can try creating a new AHX file, and seeing if that helps.
In the macro, make sure there are no delays between the two commands.
If both units are SoftStart, then it is better to define them both as SoftStart modules.
-
Sounds like you may have to re-write the macro. Don't worry, it can be done in the manner you wish. Simply call all the addresses BEFORE you send an action command. Look over in the right pane in the macro designer pane for the calls.
-
Sounds like you may have to re-write the macro. Don't worry, it can be done in the manner you wish. Simply call all the addresses BEFORE you send an action command. Look over in the right pane in the macro designer pane for the calls.
You have to use the "advanced" sction to find the individual commands, as opposed to using the "modules" in the macro.
Also, if your lamp modules are SoftStart, I highly recommend using the Extended Commands for them.
-
Not sure what you mean by calling all the addresses before I send an action. But I did re-write the macro and I sitll get the same result. I just don't get why it worked fine before the update and now it does not.. Maybe someone could test this on their end and see if it works for them? it's a simple on macro: trigger B6 on, Macro: right lamp B1 , left lamp B2 both are set to absolute on.
-
Can you post the macro here so we can see what's going on, plus a list of the modules addresses involved?
-
Well it's definatley a bug in the newer software versions of AHP. I reverted back to 3.204 and all works fine now. I tried to call tech support but got no answer after 45 minutes of letting the phone ring. I wonder if someone could contact the Developers and inform them of this issue.
-
Maybe a holiday for X10 support.
Many companies used today for Christmas because it was on a Sunday.
Some even have closed for the whole week.
-
Well it's definatley a bug in the newer software versions of AHP. I reverted back to 3.204 and all works fine now. I tried to call tech support but got no answer after 45 minutes of letting the phone ring. I wonder if someone could contact the Developers and inform them of this issue.
Have you tried AHP 3.310? I use it with zip problems. I have no plug-ins and only 1 soft-start wall switch in an upstairs storage room and everything works fine for me. All other modules are all "old style" and I have working modules with X10, Motorola, RCA, Radio Shack, IBM on them and they all work fine.
-
No I havent. I had AHP installed on old Pc and checked the version on it and it was 3.204. I figure if it works I aint messing with it. ;D
-
No I havent. I had AHP installed on old Pc and checked the version on it and it was 3.204. I figure if it works I aint messing with it. ;D
That falls squarely in the "If it ain't broke, don't fix it." department. I used 3.228 for years until 2011 when I tried a few of the 2011 AHP releases I settled on 3:310 as it caused ZERO problems. I keep a 250MB Zip drive with virtually every version of AHP since 2005 and a backup of all my .ahx files, which I have a bunch of for the various seasons of the year.
-
Well it's definatley a bug in the newer software versions of AHP. I reverted back to 3.204 and all works fine now. I tried to call tech support but got no answer after 45 minutes of letting the phone ring. I wonder if someone could contact the Developers and inform them of this issue.
Well, I'll send them an e-mail letting them know about it, but I don't know when I might get a reply.
Let me make sure I have this correct.
You have two SoftStart LM465's on two different addresses on the same housecode.
You have a macro that turns both of them on.
Using 3.204, the macro combines the commands, so the lights come on together.
Using 3.318, the commands are kept separate, so the lights come on separately.
Do I have it right?
-
You have two SoftStart LM465's on two different addresses on the same housecode.
You have a macro that turns both of them on.
Using 3.204, the macro combines the commands, so the lights come on together.
Using 3.318, the commands are kept separate, so the lights come on separately.
That is correct. I remember that I updated past 3.204 several months ago and the macro worked. Unfortunatly I don't know what version it was that I updated to. The only reason I am using 3.204 is because that's the version that I have on an old PC and I know that works.
-
I believe 3.203 is where X10 added the Soft Start Modules in the Lamps Area and added theOld before soft starts list.
Where they defined a soft start or maybe an LM14A as that was the fix for older versions of AHP.
-
The only reason I am using 3.204 is because that's the version that I have on an old PC and I know that works.
Most of the older versions (the ones that were released, at least) are available for download.
Check out the Revision History here:
http://www.x10.com/support/rev_ahp.htm
There are links to most of the versions, and you can download and install them.
-
I don't have my "test setup" available to me right now.
Can anyone else out there with 3.318 try to duplicate this problem, so I can add it to the Bug List?
I don't generally add items to the list unless I can either confirm it myself, or get one or two other users to confirm it. Sometimes it is just a fluke in one user's system, and not a bug in the software.
Also, with additional testing, we sometimes get a workaround, or another fix for it.
Thanks.
--Noam
-
Well, I remoted into one of my systems, and I think I was able to reproduce this on 3.318.
I added two Lamp modules, calling them E1 and E2.
I created a simple macro that simply turned them both on.
When I ran it, the commands ran one at a time (based on the activity log).
Next, I changed both lamps to "Old" lamps.
The same thing happened (although the commands did change from the Extended ones to the "%Dim" ones).
That's enough proof for me. I'll add it to the list, and let the developers know that the bug is on the list.
If anyone wants to test further, and try to find a fix for this, feel free.
--Noam
-
Not sure what you mean by calling all the addresses before I send an action. But I did re-write the macro and I sitll get the same result. I just don't get why it worked fine before the update and now it does not.. Maybe someone could test this on their end and see if it works for them? it's a simple on macro: trigger B6 on, Macro: right lamp B1 , left lamp B2 both are set to absolute on.
B1 will light first, B2 will light second, etc. If you want both/all to go on at once they must all have the same unit code :B1.
-
I added two Lamp modules, calling them E1 and E2.
I created a simple macro that simply turned them both on.
That's the same macro I've been using. A simple on and off.
-
Not sure what you mean by calling all the addresses before I send an action. But I did re-write the macro and I sitll get the same result. I just don't get why it worked fine before the update and now it does not.. Maybe someone could test this on their end and see if it works for them? it's a simple on macro: trigger B6 on, Macro: right lamp B1 , left lamp B2 both are set to absolute on.
B1 will light first, B2 will light second, etc. If you want both/all to go on at once they must all have the same unit code :B1.
It used to not be this way. In previous versions a macro that had B1 turning on followed by B2 turning on would send something like this: "B1, B2, B On". Both modules would "wake up" when their address was called, and they would both respond to the command at the same time. It is actually a lot more efficient to do it this way.
I haven't tested with earlier versions in a while, but I know that is how it used to work (it is even in the X10 protocol spec to do it this way). When I tested this in 3.318, I couldn't get it to work that way. It didn't matter if the modules were defined as "new" or "old" ones.
However, I think you can use the "advanced" functions of the SmartMacros, and send the individual addresses, followed by the command, and it should work (I think I tested that yesterday, not 100% sure).
-
Well, I remoted into one of my systems, and I think I was able to reproduce this on 3.318.
I added two Lamp modules, calling them E1 and E2.
I created a simple macro that simply turned them both on.
When I ran it, the commands ran one at a time (based on the activity log).
Next, I changed both lamps to "Old" lamps.
The same thing happened (although the commands did change from the Extended ones to the "%Dim" ones).
That's enough proof for me. I'll add it to the list, and let the developers know that the bug is on the list.
If anyone wants to test further, and try to find a fix for this, feel free.
--Noam
I added this to the Bug List yesterday, and e-mailed one of the developers. I got a reply back from him this morning. He is out of the office this week, but he told me he would look into this when he gets back.
-
Has there been any update on this?. I've tried updating to the latest version but it still has the same bug.
-
Has there been any update on this?. I've tried updating to the latest version but it still has the same bug.
I haven't heard anything. We haven't had a new version since October 2011. I haven't seen the developer online here in a while. I'm not sure if he even still forks for X10 (X10 Repair Depot might be able to tell us that)
I have a feeling X10 won't be spending much (if any) effort on AHP, since the CM15A has been discontinued (for now, at least).
-
Has there been any update on this?. I've tried updating to the latest version but it still has the same bug.
Technically it is NOT an bug, so, like Noam, I doubt X10 will spend any time to fix. Did you try Noams December 28, 2011, 10:11:45 AM reply? If AHP allows you to bunch addresses on the same House Code, then send the "HC ON" command, all lights that were addresses should come on. If you have a "Maxi Controller" you can test whether softstart and regular (old) X10 lamp modules and wall switches the same, but I think they will. I can test this weekend when I am home.
-
Used a "Maxi-Controller".
Didn't check wall switches.
Checked Soft Start and Old LM465s.
Before CFL Friendly and CFL friendly Appliance Modules.
LM14A and AM14A two way lamp and appliance modules.
Any set of addresses using the same house code. Sent before a function command was sent. Those modules all responded to the function command.
Like B1, B4 then BOn. Both B1 and B4 Modules would turn On.
B1,B2, B4 then BOn. The B1,B2 and B4 modules would respond.
B1,B2,B3 and B4 then BOn. All four would go ON. Then send a B1, B4 then BOff. Only the B1 and B4 Modules would go Off. B2 and B3 stayed On.
I would also agree with the others. With the CM15A discontinued and its successor only a thought for now. I would not expect any AHP Updates to be released.
-
I have also tried this out using the latest version of AHP setup using 2 socket rockets selected directly from the new lamps section and added to room livingroom set to codes A4 and A9.
I tested with a macro set to activate when code A1 is pressed.
I tried setting the macro to have livingroom all lights on, I tried selecting the modules and setting them to on, I tried setting to address code on for each and all of these produced one light on before the other.
Then i tried setting the advanced function command code A4 and A9 before I did each of the above and none of them made significant difference.
One time the lights came on both at the same time and I saw this reflected in the activity monitor but even without changing the macro to something different this only happened once, most of the time the lights still came on one after the other and this was reflected in the activity log, so for some reason even with a macro setup that did work one time it did not work every time, and a few times it even only turned on one of the lights and the other didn't come on at all.
Why might this be?