Print

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

[davideinmd]

I had this working properly at one time. (Backup those AHX files folks!) Now I can't get it. I have followed everything in the forum posts I can find.
I have installed the remote in AHP and the DS7000. I have made the macro and run it with the install setting on the DS7000 but the DS7000 won't beep and register the AHP code that seems to be being sent. I have tried transcieving the HC and not trancieving it. Any thoughts?

[davideinmd]

May be it would help to know that when I run the macro and watch the activity monitor it says Transmit RF A Pause, Transmit RF A Unknown.

[Puck]

I believe the PS561 has a limit of 8 remotes that can be registered. Unfortunately there are no LEDs to indicate what number you are on, unlike the zone LEDs. You may have to do a complete reset & reinstall of your PS561 remotes and security devices.

[davideinmd]

I did the complete reinstallation of the DS7000 and reinstalled the remotes in AHP. Still no luck. I can't help but think there is a problem where the Activity Monitor is showing an ambiguous transmission message as stated previously. It would help me to know what other users are seeing in thier Activity Monitor when AHP issues an arm command.

[J.B.]

I was getting a random M code from one DS10A when it tripped.
I set a new security code on it and still received the M code. I removed the batteries for a min, reinstalled them and then issued another new code.
I then reset my security console, reinstalled all sensors, re-registered the sensors in AHP and finally stopped seeing the random code.
Quite time consuming if you have a lot of sensors and security remotes in use, but the only thing I was able to do to fix the issue.

[Puck]

I was getting a random M code from one DS10A when it tripped.

If you were getting a random House Code "M" signal, it wasn't coming from the DS10A. X10 security devices do not generate the normal House Code / Unit Code signals.

If you have OnAlert assigning your DS10A signal to House Code "M", then you likely had a noise or signal reception issue. House Code "M" is not the best choice for assigning a device to since it is made up from all zeros; this makes it more susceptible to being corrupted by noise.

[J.B.]

I'm thinking it may have been that the sensor was automatically assigned an M HC at one point and retained its security code when I recently moved.
I normally right click the security modules in AHP, change the module type, assign the HC/UC I want, change module type back to its original one. I then check that the module is showing the codes I assigned using AHPs tools/Find other computers function.
I don't recall ever using HC M for a security module but where AHP auto assigns a code with OnAlert unless you change it, it may have used M for this particular one.
I assigned it an H HC in OnAlert but it still said M Unknown until I removed the batteries and then reinstalled it.
Must have had to do with OnAlert and AHP.
I was only seeing this M code when that specific DS10A was tripped.
Once I followed the steps of removing and reinstalling the batteries and then issuing another new security code, the M codes stopped.
I have just setup a fresh .ahx file, so the previous one may have been corrupt. I've also since removed the sensor from OnAlert and have mapped it as a standard HC/UC in my V572RF32.
I'm aware the DS10A and other x10 security sensors do not send a standard HC/UC which is why I mapped the sensor in OnAlert and now, instead, with my V572.
I've also seen this with an A code.
The AHP activity monitor has shown A Unknown and also A00TV.
This seems to be a stray signal or one of my devices are reading as A00TV.
I DO see this when using Windows Media Center with my Icon remotes and CM15A, but am still seeing this when I'm not using them.
I have gone over my setup thoroughly and am using an XTB-IIR and a handful of XPPFs and have not noticed any of my previous noise issues since adding these pieces to my system.
Nothing else has been added electronically and the noise was not generating any x10 codes previously, just causing intermittent module response with certain modules (more likely would have been signal suckers eg: running multiple PCs unfiltered at the time).

One other thing that may have caused an issue. I have actually had 2 sensors generate and register with the SAME security code.
Where this is so unlikely, it took me a while to notice this.
Weather this caused my issue at the time or not, I don't know.

[Puck]

I was only seeing this M code when that specific DS10A was tripped.

Once I followed the steps of removing and reinstalling the batteries and then issuing another new security code, the M codes stopped.

I'm aware the DS10A and other x10 security sensors do not send a standard HC/UC

Just so someone who is not familiar with how X10 security devices work and interact with AHP through OnAlert, doing a complete reset of the DS10A to have it select a new 4-byte security code did not actually fix your problem. The problem was never with the DS10A, because as you know, it can't send a House Code signal.

Resetting the DS10A's security code did however stop that sensor from triggering the fault within your AHP setup (most likely something corrupt within your AHX file). So doing this may have masked the problem, but the root cause still existed; and if that DS10A was part of a DS7000 system, a complete reset / re-register was required, but it could have been avoided.

I know you recreated your AHX file, and from what you described, I'm sure that was the correct fix for your problem.

As for davideinmd's problem, you may want to try a new (temporary) AHX file to create and test your remote and it's ability to arm your DS7000. Unfortunately the AHX files can get corrupted when changes are made to it. Issues like this are why I stopped using AHP a while ago. Hopefully someday they will actually fix the software.

[J.B.]

Issues like this are why I stopped using AHP a while ago. Hopefully someday they will actually fix the software.

I agree, they need to fix bugs in AHP.
I've had versions of AHP work flawlessly for long periods of time, only to randomly go on the brink.
This can make it much more difficult to troubleshoot issues.
I'll admit though, there have definitely been issues caused by user error on my part, too.


As far as a fresh .AHX file, that would definitely be a good step to try to see if issues stop.

[mike]

not sure why we should have to rebuild a .ahx file.....  if you look at them in text editor they are very straighforward and if there is any garbage in them it is obvious. 

Puck, since you quit using ahp what are you using now?  Ihouse?

[Knightrider]

Just so someone who is not familiar with how X10 security devices work and interact with AHP through OnAlert, doing a complete reset of the DS10A to have it select a new 4-byte security code did not actually fix your problem. The problem was never with the DS10A, because as you know, it can't send a House Code signal.

Not sure how this relates, but check out these threads:

http://forums.x10.com/index.php?topic=10419.0

http://forums.x10.com/index.php?topic=12808.msg70486#msg70486

[davideinmd]

Ok, now that this thread has gone fairly off the track, I still have no clue as to what my problem is. 
I am using Win7 and the newest shineyest version of AHP with all the bells and whistles. I have tried all these suggestions and I still can't get my DS7000 to arm with AHP. Any last thoughts (on this topic or the other)?

[Puck]

Ok, now that this thread has gone fairly off the track,

The information added may have detoured from your particular problem, but it still concerns the same topic, added operational info and produced a prime suggestion for you to try.

I have tried all these suggestions and I still can't get my DS7000 to arm with AHP.

You should elaborate more on what you tried and what the results were. Saves people from further guessing and giving you useless suggestions. It's hard to help troubleshoot a problem when you don't know what has or hasn't been tried, and what results you are seeing.

[davideinmd]

OK Puck, I'll go over these posts more caefully and reply all I have tried in my next post.

[davideinmd]

Neato! I installed the update for AHP to 3.296 and now this issue is resolved! In fact, the little icon in the status bar shows armed home, away, or not armed. Plus, another issue I had with 2 lights working together that had 2 different unit codes fixed as well. Nice!