M1 Gold problem

tunafishhkg

New Member
Hi,
  I have the M1 Gold and have a problem with it not taking the password at the keypad.  It has been going off on alarm for the past 6m when entering my code, usually at the last digit but it did not do this all the time maybe 6 times then ok for three. Now it will not take my master code  and I have to go in with RP on laptop hardwire at the M1 to reset syst, then can hit code on keypad and leave. If I go back in, it will not take code and I have to start all over again. This new problem started after a power outage and my Gen did not kick in so was out for 30hrs. I believe my back up batt is still dead in the M1 till I do a charge would that cause a prob with keypad code? I installed another keypad with no results. Also I have a spare MXEP that says old firmware and need to know how to flash new firmware or will the M1 send it to it if installed, since that has all the new firmware?
Thank you!!  
 
it wont get the firmware automatically - you need to flash each component individually; your problem sounds like a data bus problem - something isn't terminated properly or something like that.
 
Update, Turns out it was a simple programing fix, admin temp password check box issue that never came up since I  was only one to arm syst since last program and always hit exit to arm. I sent someone to house and when he left he hit his code instead of exit and since the admin password was temp, his now became only password to disarm syst. Still not sure why it sometimes went off on alarm while disarming with my master code after exit to alarm or why it did not do it all the time but after this fix, I should be all set.  Thanks for the replies!!
 
If you're referring to the Master Programming Code, it doesn't disarm the alarm - that's by design so your alarm installer can have a programming code that only works if the alarm is disarmed - it won't let them enter your house and disarm the alarm.
 
Work-
I believe what the OP is referring to was that his code had the "temporary" attribute assigned to it - which would only allow that code to disarm when that same code was used to arm the system.  Therefore, once the other person put in their code to arm the system it essentially locked him out!
 
That's definitely an interesting feature!
 
The OP made mention of the Master Code - I just wanted to be clear in case he was attempting to use the programming code to disarm which won't work.
 
Yeah... I started to use it myself. Originally, I had a standard user code tied to a task with a timer that I would enable when needed and it would disable once the timer expired. Then I realized it would just be easier to use the temporary code feature for the rare times we actually need it. Plus it eliminates the need for the automation frontend to be accessed.
 
Back
Top