M1PKNAV trouble

[chrisexv6]

As my wife was leaving today she attempted to arm the alarm like we always do (with the M1KPNAV by the entry door)
 
She said a message came up "something about an address" was her description, she was in a rush so couldnt do anything about it.
 
Get home a couple hours later and the system is in "trouble".  This is what the log shows:
 
21,Sat 5/4/2013,11:27,,1161 = EXPANSION MODULE RESTORE,Keypad 1
22,Sat 5/4/2013,11:27,,1141 = EXPANSION MODULE TROUBLE,Keypad 1
23,Sat 5/4/2013,10:59,,1161 = EXPANSION MODULE RESTORE,Keypad 1
24,Sat 5/4/2013,10:59,,1141 = EXPANSION MODULE TROUBLE,Keypad 1
25,Sat 5/4/2013,10:52,,1161 = EXPANSION MODULE RESTORE,Keypad 1
26,Sat 5/4/2013,10:52,,1141 = EXPANSION MODULE TROUBLE,Keypad 1
27,Sat 5/4/2013,10:27,,1161 = EXPANSION MODULE RESTORE,Keypad 1
28,Sat 5/4/2013,10:27,,1141 = EXPANSION MODULE TROUBLE,Keypad 1
29,Sat 5/4/2013,10:22,,1161 = EXPANSION MODULE RESTORE,Keypad 1
30,Sat 5/4/2013,10:22,,1141 = EXPANSION MODULE TROUBLE,Keypad 1
31,Sat 5/4/2013,09:56,,1141 = EXPANSION MODULE TROUBLE,Keypad 3
 
The trouble at 9:56 was when she attempted to arm the system.  keypad 3 is the M1KPNAV.  Whats interesting is that the trouble went to keypad 1 then stayed there.
 
When I got home the system was acting like it had when I first added the M1KPNAV with the default address (of 1).  Sure enough, holding the Clear button on the keypad showed me that the M1KPNAV was set back to address 1 and causing a conflict.  Changed it back to 3 like it was and now everything is fine again.
 
Any ideas why the KPNAV may have spontaneously reset its keypad address?

 

[BraveSirRobbin]

That is weird,  Did you re-enroll recently or any power glitches in the home?

 

[chrisexv6]

No power glitches Im aware of...we were home all morning and I didnt notice anything.
 
Also no re-enrolls.  The last addition was the M1KPNAV itself, about 3 months ago.  No issues then (except for the initial startup when it had the same address as my other keypad), and no issues since then either.

 

[Mp333]

I have KPNAV as address 02 for about 4 months. . No issues so far.

 

[chrisexv6]

Not thinking its an issue of using a Navigator on anything other than address 1, I just cant fathom why it would switch back to default by itself.
 
A couple things:
 
1.  I took the Navigator back off the wall and noticed I had left the brown and blue leads just dangling (they have no exposed conductors though).  Not sure if somehow a short on one (or both) of those could cause this?
 
2.  I had recently setup a Premise server and the Elk module (the night before this happened).  The s/w itself was not running at the time, so Im thinking its not an issue but figured Id throw it out there now that I remember it.
 
I sent the info to Elk support, will post back if they know of anything.  It looks like the Navigator was installed in early Feb, so we were running for 3 months without issue.

 

[TurboSam]

Any update on this from Elk?  
 
I had the same problem last night (in the middle of the night when the system was armed night mode):  three 1141 "Expansion Module Trouble" alerts for Keypad 1, Keypad 2, and Output Exp. 2, and half an hour later all three were restored with code 1161...

 

[chrisexv6]

Any update on this from Elk?  
 
I had the same problem last night (in the middle of the night when the system was armed night mode):  three 1141 "Expansion Module Trouble" alerts for Keypad 1, Keypad 2, and Output Exp. 2, and half an hour later all three were restored with code 1161...

 
Interesting, nice to see (well, not really!) that someone else had the same issue.  Elk doesnt seem to have ever heard of it and couldnt re-create it. 
 
I sent you more details in a PM.
 
-Chris