Just an a quick update regarding this issue:
I just posted the following message on the elk website to find out if they are actively doing anything about this issue.
Has Elk "officially" logged this issue as a bug and are there plans to correct it? I am experiencing the exact same issue as described in the previous post. For example, my wife accidentally tripped a back door zone (forgot to bypass it) and the alarm triggered as expected. When I check in the log I see the back door trip and then immediately following my 2 garage overhead doors trip (extended entry delay) and then the garage door to the house (standard entry delay). I have a pretty simple set up with only 8 zones defined in all. Currently 2 of these zones are set up for non alarm zones because I am trying out 2 motion detectors for sensitivity prior to making these active alarm zones.
This bug is a significant issue when trying to determine fales alarms becuase it falsely indicates that multiple zones have been tripped. I have recently added some rules to send emails based on zones being tripped so when I have an alarm I have good information regarding what is going on and possibly to understand if it might likely be a false alarm (such as if just one motion trips). This won't work if I am getting false zone trip information.
Thanks,
Matt