Announcement

Collapse
No announcement yet.

Security alert status has been reset to Normal.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Security alert status has been reset to Normal.

    After arming BLSecurity, after the first event that triggers the Alert status, the system immediately resets the status to Normal (see log messages below).
    Oct-01 1:01:46 PM BLSecurity Info Security alert status has been reset to Normal.
    Oct-01 1:01:46 PM BLSecurity Warning Device: BLRF-16817 (Foyer Motion) has triggered an alert!
    Oct-01 1:01:45 PM BLRF MS10 MS10 (Foyer Motion) is ON
    Oct-01 12:59:38 PM TTS Speak ():The system is now armed.
    Oct-01 12:59:38 PM BLSecurity Info BLSecurity mode is now set to ARMED!
    Oct-01 12:57:38 PM TTS Speak ():Attention. The system will arm in 120 seconds.
    Oct-01 12:57:38 PM BLSecurity Info BLSecurity will be set to ARMED in 120 seconds!
    After the next trigger, the system stays in Alert mode as expected (presumably for 5 minutes as per the setting below):
    Number of minutes to reset alert status (mins)
    Note: This is the number of minutes that must elapse without a triggered alert before the alert status is reset back to Normal.
    Any idea why the status resets on the first trigger? I've turned off everything I think might be interfering to no avail. This is consistent (and, in my view, wrong) behavior.

    #2
    Bumping this post since I'm evaluating the plugin and I'm having the same issues that the alarm condition is reset immediately after having been triggered.

    I tried to emulate the original posters "success" of having the following trigger maintain alert mode, but that only happened once where's all other repeat attempts are reset immediately. I also tried waiting an extended period of time (25min plus) thinking there might be a slight delay where alerts are ignored but that doesn't seem to make a difference.

    Code:
     
    6/9/2019 8:01:38 AM Reset System alerts have been reset
    6/9/2019 8:01:37 AM Alert (Mode: Armed) System received an alert -- Device: Hallway MOTION (Q62)
    6/9/2019 7:52:38 AM Reset System alerts have been reset
    6/9/2019 7:52:38 AM Alert (Mode: Armed) System received an alert -- Device: Hallway MOTION (Q62)
    6/9/2019 7:25:54 AM Arm System was set to Armed mode (User: Main)
    6/9/2019 7:23:09 AM Disarm System was set to Disarmed mode (User: Main)
    6/9/2019 7:14:45 AM Reset System alerts have been reset
    6/9/2019 7:14:45 AM Alert (Mode: Armed) System received an alert -- Device: Hallway MOTION (Q62)
    6/9/2019 7:05:49 AM Reset System alerts have been reset
    6/9/2019 7:05:49 AM Alert (Mode: Armed) System received an alert -- Device: Hallway MOTION (Q62)
    6/9/2019 6:36:12 AM Reset System alerts have been reset
    6/9/2019 6:36:12 AM Reset System alerts have been reset
    6/9/2019 6:27:49 AM Arm System was set to Armed mode (User: Main)
    6/9/2019 6:23:28 AM Disarm System was set to Disarmed mode (User: Main)
    6/9/2019 6:22:04 AM Alert (Mode: Armed) System received an alert -- Device: Hallway MOTION (Q62)
    6/9/2019 6:00:09 AM Alert (Mode: Armed) System received an alert -- Device: Hallway MOTION (Q62)
    6/9/2019 6:00:09 AM Reset System alerts have been reset
    6/9/2019 5:58:03 AM Arm System was set to Armed mode (User: Main)
    6/8/2019 9:09:25 PM Disarm System was set to Disarmed mode
    6/8/2019 9:05:00 PM Reset System alerts have been reset
    6/8/2019 9:04:59 PM Alert (Mode: Armed) System received an alert -- Device: Hallway MOTION (Q62)
    6/8/2019 9:00:25 PM Arm System was set to Armed mode (User: Main)
    6/8/2019 8:58:16 PM Disarm System was set to Disarmed mode (User: Main)

    Comment


      #3
      I think there may be some misumderstanding between "State" and "Mode"
      The "state" is whether the system is "Waiting to be triggered" or "Triggered". The "mode" would be "Armed", "Perimeter" or "Sleep.
      The message "reset" only applies to the "state" not the "Mode" so the alarm is still in the same "MODE" unless you specifically change to "Disarmed Mode" via a user code.
      Hope that helps
      /Marcus

      Comment


        #4
        Back to the original post.
        BLSecurity would reset the "status" back to normal because you don't want the status to remain as "Alerted".
        The "Mode" of the alarm is NOT reset. It remains "ARMED"
        /Marcus

        Comment


          #5
          I understand that it would be reset back to normal after the time-out period of 5 minutes and/or when you disarm/re-arm the system,
          the problem is that it does it right away and the trigger is ignored.

          I've been playing around with it and it seems it's only happening after the plugin is re-started and once you get one alarm to trigger properly, that you can arm/disarm a million times and it seems to work just fine.

          1st trigger is ignored as it's reset right away.
          ‚Äč



          If you trigger it twice within the timeout time it will set off the alarm and after that everything works fine (until you restart BLS/HS again).
          Click image for larger version  Name:	Capture3.PNG Views:	0 Size:	37.9 KB ID:	1323098



          At least I have a work-around for now so I think I'll end up buying the plugin, but if you (Blade) need me to try something else and/or grab logs let me know.

          Thanks

          mrM

          Comment


            #6
            As an FYI to the community....

            Blade has been very helpful in resolving the issue above and 2.0.45 Beta is working great for me.

            Comment

            Working...
            X