Is "Code Range to Avoid" reliable?

[PajamaGuy]

I just added an MS14A (EagleEye) to my system yesterday and addressed it as H1.  It is the only "H" unit in my system.  Prior to yesterday, I had no icons on the "H" line in "Find Other Computers".  Now there's a RED, and 3 through 16 are YELLOW.

Makes me wonder if the YELLOWs  in the "A" line are real - since most of my sensord installed themselves in "A".

[Oldtimer]

I just added an MS14A (EagleEye) to my system yesterday and addressed it as H1.  It is the only "H" unit in my system.  Prior to yesterday, I had no icons on the "H" line in "Find Other Computers".  Now there's a RED, and 3 through 16 are YELLOW.

Makes me wonder if the YELLOWs  in the "A" line are real - since most of my sensord installed themselves in "A".

To be sure about what's going on try the following.  Open AHP, click on Tools and then click on Clear History.  This will clear the contents of the Activity Monitor.  Find Other Computers builds some of its display, over time, from the contents of the Activity Monitor, clearing history resets both reports.  Check back every day or so to see how the YELLOWs build back up.  If this happens again you may have to do some more hardware level research. I've never seen this fast a buildup exclusively in a single house code with only two unit codes in it.  Keep us posted.

[PajamaGuy]

Thanks - I regurarly clear the history - I haven't timed it, or forced sensor activity to see if the buildup is "all at once" but I'll do some testing tonight.  It's certainly hours or less, not days...

[Oldtimer]

Thanks - I regurarly clear the history - I haven't timed it, or forced sensor activity to see if the buildup is "all at once" but I'll do some testing tonight.  It's certainly hours or less, not days...

If I had your problem the next thing I'd do is to take the batteries out of the Eagle Eye to see if the YELLOW goes away.  In my mind that would indicate a defective unit.  I've never heard of it but who knows?

[PajamaGuy]

Since it hasn't yet - I think it was from setting the address on the sensor...