Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[gdmaclew]

I am trying to control an X-10 Wall Module (old style WS467) with AHP and a CM15A, basically doing a pre-vacation test.

With the CM15A plugged into the wall and connected via USB to my PC here's what happens.
When I try to turn on the lights, nothing happens. It is set to send a repeat signal to the switch.
If I add another module exactly the same as my current module (WS467) and then delete it immediately, I can turn on the lights clicking on the original module.
What gives?

[Brian H]

Did you pick the WS467 from the "Old Before Soft Start" tab?
So AHP doesn't use Extended X10 Commands an old WS467 will not understand.

[gdmaclew]

No I did not.
But I don't understand the relevance.
As I mentioned before, upon entering AHP, the lights will not turn on for that module until I add another module exactly the same and delete it immediately.
The original one will work until I exit AHP and then when I re-launch AHP, the module is again unresponsive until I add another exact module again and then delete it.
It's almost as if AHP "wakes up" to the presence of the original module when I add a module of the same type and code (Lamps, Wall Switch module) and then delete it.

[Brian H]

If you used a soft start type on an older WS476.  That will cause AHP to use Extended Commands that the WS467 does not understand.
Why adding a second one changes things I can't say.
I would strongly suggest you try again with the proper choice and see if things get better.

[gdmaclew]

Thanks Brian.
I deleted the original module and created a new non soft-start wall switch.
The switch now responds normally each time I enter AHP.
I downloaded the settings to the CM15A and disconnected it from my PC.
The switch responded perfectly to the CM15A.
Problem solved.

[Brian H]

Well I also have to thank you for finding this abnormal behaviour.
I tried what you where pointing out.
Started a new program with one soft start WS467 and it send Extended Commands. Added a second WS467 on the same address and deleted it.
AHP reverted to the older On and Off protocol until I exited AHP and it again reverted to Extended Commands.
So adding a second WS467 did correct your problem until it was restarted and reverted back to Extended Commands. The old WS467 didn't recognize.

[gdmaclew]

You are most welcome Brian.

[Noam]

Well I also have to thank you for finding this abnormal behaviour.
I tried what you where pointing out.
Started a new program with one soft start WS467 and it send Extended Commands. Added a second WS467 on the same address and deleted it.
AHP reverted to the older On and Off protocol until I exited AHP and it again reverted to Extended Commands.
So adding a second WS467 did correct your problem until it was restarted and reverted back to Extended Commands. The old WS467 didn't recognize.

It looks like the "cleanup" when the second module is deleted is broken. However, closing and re-opening AHP fixes the problem. Yes, it is a bug, but I don't know if it is worth adding it to the list. Does it only happen with the WS467? Does it only happen when there is only one module in the AHX file?
There are already a number of "SoftStart vs. non-SoftStart" bugs, and I don't know if this one is truly different (we already know that you will have "inconsistent behavior" if you mix module types on the same HC/UC.
I haven't seen any signs that indicate X10 is still doing any work on AHP. I don't know if they have any developers left. If they are working on a replacement for the CM15A, my guess would be that they would be building new software for it. I could be wrong, however. Perhaps they will modify AHP to work with the new controller (or design the new controller to mimic a CM15A when it talks to AHP).

[Brian H]

I may try some added things.
I had one WS467 in the file then added a second one. Then deleted it.
Could also use a SS LM465 for the second one and delete it. Same results.
Probably not needing to be added to the list.

I also doubt X10 is putting time into AHP. Maybe if the new controller is in the works. Then things maybe looked at.

[gdmaclew]

Well I also have to thank you for finding this abnormal behaviour.
I tried what you where pointing out.
Started a new program with one soft start WS467 and it send Extended Commands. Added a second WS467 on the same address and deleted it.
AHP reverted to the older On and Off protocol until I exited AHP and it again reverted to Extended Commands.
So adding a second WS467 did correct your problem until it was restarted and reverted back to Extended Commands. The old WS467 didn't recognize.

It looks like the "cleanup" when the second module is deleted is broken. However, closing and re-opening AHP fixes the problem. Yes, it is a bug, but I don't know if it is worth adding it to the list. Does it only happen with the WS467? Does it only happen when there is only one module in the AHX file?
There are already a number of "SoftStart vs. non-SoftStart" bugs, and I don't know if this one is truly different (we already know that you will have "inconsistent behavior" if you mix module types on the same HC/UC.
I haven't seen any signs that indicate X10 is still doing any work on AHP. I don't know if they have any developers left. If they are working on a replacement for the CM15A, my guess would be that they would be building new software for it. I could be wrong, however. Perhaps they will modify AHP to work with the new controller (or design the new controller to mimic a CM15A when it talks to AHP).

Yes Noam it only happens with the WS467.
I have never tried it with only one module.

[Brian H]

I have done it with Soft Start LM465s also.
I added three pairs {two on an address} to AHP
As I deleted and emptied the trash bin. The remaining one reverted to old On from Extended Messaging.
The other pairs still used Extended messaging until one if its mates was also deleted and dumped from the trash.
Restarting AHP and Extended messaging again was used.