Announcement

Collapse
No announcement yet.

Active Zone no longer seeing motion

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

  • Active Zone no longer seeing motion

    Hi Blade,

    I am a bit stumped. Ive had BLRadar for some time, but went in to really start using it today. I found my system doesn't seem to be detecting the motion on events anymore, but is detecting the off events. I've checked the the motion sensors (1 in on, 0 is off). The motion sensor in BLRadar is setup to trigger on values. I can activate the motion sensor and the last activity time in BlRadar updates (and the zone device itself shows motion then no motion), however the Active Zone never turns on.

    Log attached. Look at device 2115 which is a Envislink motion device. The last Off is fine, the last ON is wrong.

    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Times(): ** Finished checking sensor --> 2227
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Times(): ** -----------------------------------------------
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Times(): ** Checking sensor --> 2115
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Times(): Code --> Zone 8
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Times(): Location --> Alarm
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Times(): Name --> Dining Room Motion
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Times(): Type --> Motion Sensor
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Times(): FirstOn --> 5/11/2018 11:30:46 AM
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Times(): LastOn --> 5/11/2018 11:30:46 AM
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Times(): LastOff --> 5/13/2018 6:41:56 PM
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Times(): DeadBattery --> False
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Times(): SensorRecoveryTime --> 60
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Times(): DeadBatteryTime --> -1
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Recovery() started
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Recovery(): * Start of sensor recovery check for Zone 8...
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Recovery(): theSensor.LastOff --> 5/13/2018 6:41:56 PM
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Recovery(): theSensor.LastOn --> 5/11/2018 11:30:46 AM
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Recovery(): no processing... last off is greater than last on so sensor has received its off!
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Recovery(): * End of sensor recovery check for Zone 8
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Recovery() finished
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Dead_Batteries() started
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Dead_Batteries(): * Start of sensor failure check for 2115...
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Dead_Batteries(): dead battery time is NOT enabled for this sensor!
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Dead_Batteries(): * End of sensor failure check for 2115
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Dead_Batteries() finished
    5/13/2018 6:42:50 PM : v2.0.139.0 - Check_Sensor_Times(): ** Finished checking sensor --> 2115

    Thank you!
    Bill
    Attached Files

  • #2
    I do not see a device change callback into the plugin from HS3
    HS3 will send these when the device changes value in HS3 but I do not see any for device ref 2115
    Cheers,
    Bob
    Web site | Help Desk | Feature Requests | Message Board

    Comment


    • #3
      Very very strange (I am a plugin developer as well). I tested other plugins (and debugged mine) and am seeing the change, what else can I try?

      Comment


      • #4
        Yes I would expect to be seeing it in the log as others are using it and no one else is reporting it

        Can I see the status/graphics tab in a screenshot for the device
        Also attach your BLRadar.xml file zipped too
        Cheers,
        Bob
        Web site | Help Desk | Feature Requests | Message Board

        Comment


        • #5
          Agreed, definitely odd. Requested files attached...
          Attached Files

          Comment


          • #6
            OK that makes no sense
            Delete the debug log and turn on debug logging again, then make 2115 turn on to a value of 1, then turn off debug logging
            Attach the new debug log zipped

            If I do not see it in the log then I am going to have to mimic this at home and see what is happening
            Are other devices triggering?
            Cheers,
            Bob
            Web site | Help Desk | Feature Requests | Message Board

            Comment


            • #7
              I just upgraded to 3.0.0.325 from 3.0.0.368, no change (same issue)
              Issue is effecting all sensors/zones not just this one.

              I just triggered the motion sensor twice (and watched as the device changed in the HS UI). The device change really quickly (on for a second or two, then back to off as I walk through the room) Last 'off' was at 10:11:32, so the ON would be around 10:11:30 or later. On the plus side Im glad I asked, I spent a few hours trying to figure this out thinking it was something in my config (albeit, still may be, but its not at least obvious)
              Attached Files

              Comment


              • #8
                Ok, something new. The latest build is showing this in the error log:

                May-14 10:21:26 AM Warning Dropping event callbacks due to full queue (Type: 1024) (500 entries), system may be too busy, plugins and HSTouch may not receive all device updates

                Which would explain why you aren't seeing the change. Now I just need to figure out what is broken on my system causing this. Guess I get to go play whack-a-plugin until the error goes away. Will update.

                Comment


                • #9
                  Yes that could explain it - my guess is HS3 is causing this. I am running HS3 .435 but I do not use HSTouch
                  Cheers,
                  Bob
                  Web site | Help Desk | Feature Requests | Message Board

                  Comment


                  • #10
                    I owe you a beer. I found one of my plugins was using high cpu, which apparently was causing events to queue up. Not sure why (off to go debug that), but when I stopped it then events started flowing and BlRadar immediately showed the correct echo/noecho on the zones.

                    Sorry for the spin, but greatly appreciate the time, as I don't think I saw any other symptoms but this (which is scary!)

                    Best
                    Bill

                    Comment


                    • #11
                      No problem - glad you got it sorted
                      Cheers,
                      Bob
                      Web site | Help Desk | Feature Requests | Message Board

                      Comment

                      Working...
                      X