After upgrading M1 control firmware to 5.1.4, I get a Security Alert on powercycle

[johnnynine]

I just upgraded my M1 control firmware to 5.1.4 today.

Whenever I powercycle my M1, the keypad beeps and displays "SECURITY ALERT", on Zone 17.

If I clear it by entering a code, the "alarm acknowledged" annunciation occurs, but after a second or two the cycle repeats itself for up to 30ish seconds.

When I check Zone 17 in the ElkRP Status window it shows EOLR(-) 7.3 volts, which is consistent with most zones.

 

[BraveSirRobbin]

Off the top of my head... zone 17 is the first zone "off" of the main board (probably your first expander). Maybe check or re-enroll this module??

 

[IVB]

were there any other upgrades required along with the M1? (I.e., keypad/expander/ethernet/etc)? Are you out of sync?

 

[johnnynine]

were there any other upgrades required along with the M1? (I.e., keypad/expander/ethernet/etc)? Are you out of sync?

Good thought, but my keypad firmwares are up to date.

 

[cliffs]

I don't know if this is the same problem, but I had a power outage they other day and when the
power came back all the keypads went into alarm(like they lost communications, but they didn't) and couldn't clear the
alarm without power cycling the system from the switch on the M1G. Good thing I was home
and not on vacation otherwise the a keypad alarm would have went off for days.

Cliff s

 

[gatchel]

I think this was fixed in the latest release (5.1.4) I am using 4.5.4.

This is from the release notes:


9. Found and corrected a problem which could cause an alarm from an input expanders after a total power failure and
subsequent power restoral.



I used to get this from all zones on input expander 1 that were configured. I just power cycled the M1 and got alarms on zones 20 thru 23. They cleared and showed no faults within seconds of the announcement.

I don't really see this as a major issue. The zones report fine. As long as your backup battery is fresh a power blip would be ignored.


Maybe there is still an issue? Spanky?

 

[Mike]

Interesting, when I did my batch of updates (everything except insteon, a few weeks back I think) at one point (not sure on which one) my alarm went off when it cycled after the firmware upgrade. I just silenced it, verified it was not reported (it was not) and continued.

I do have an input expander as well.

 

[Spanky]

Check the zone definition of zone 17 and see if it is set for EOL supervised on open. This type of zone definition triggers a beeping keypad and Security Alert on the keypad if the zone is opened and the system disarmed. It is normally used for the back door of a building to know when someone opens the door.

Upon power up the input zone expander can take up to 1 minute to check in, in which time the zone is considered violated until it checks in.

 

[johnnynine]

Check the zone definition of zone 17 and see if it is set for EOL supervised on open. This type of zone definition triggers a beeping keypad and Security Alert on the keypad if the zone is opened and the system disarmed. It is normally used for the back door of a building to know when someone opens the door.

Upon power up the input zone expander can take up to 1 minute to check in, in which time the zone is considered violated until it checks in.

Zone 17 is set to 3=EOL Supervised on Short.

The M1 may have seen this zone as violated for a minute when booting up but the kepads never beeped with a message. Also the voltage on it (and all the other zones on that input card) is 7.3.