Announcement

Collapse
No announcement yet.

V1.0.0.21 posted, Event handling (Dings) completely rewritten

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

    V1.0.0.21 posted, Event handling (Dings) completely rewritten

    Somehow, the way events are reported is completely different as it was about a month ago. Still don't know whether this was my changes (or more likely) a change on the Ring Server.
    This version should now turn off motion state as soon as the Ring Server stops reporting it.
    However, these event messages now don't seem to carry the detection type, so for now, only motion, no more human/person detection. I did leave a test debug log statement in the code, in case it is available on someone's system and I would love to hear from that person.
    I also changed the authorization code slightly, so you will now spot the PI in the Authorized Devices list as "homeseer-ring".
    Post your issues w v.21 here

    #2
    ok here is a cleaned up system at my house with a new Ring Pro 2 front door bell with updated v.21. Attached verbose log will have the first person initiated motion event at 09:20:39 and then a second person motion event about 09:21:10. Motion event expired at 09:21:43

    I only see one initial ding event and see it expired in 60+ secs compared to 180 secs from before. I hope you see something that is helpful

    (Rilassare and Back Door units are temporarily offline)


    Attached Files

    Comment


      #3
      Originally posted by will40 View Post
      ok here is a cleaned up system at my house with a new Ring Pro 2 front door bell with updated v.21. Attached verbose log will have the first person initiated motion event at 09:20:39 and then a second person motion event about 09:21:10. Motion event expired at 09:21:43

      I only see one initial ding event and see it expired in 60+ secs compared to 180 secs from before. I hope you see something that is helpful

      (Rilassare and Back Door units are temporarily offline)

      Only see on event, guess Ring didn't report the second event, did the Ring App see 2?
      All else looks to do what it was designed to do ie. as long as the event is repeated, it stays active and as soon as the Ring Server stops repeating it, the state goes back to "no Motion" which appears to be a minute instead of 3.

      Comment


        #4
        sorry about that, I didn't even think to check the app but since I added another ring device to my house I bogged down the bell transformer so things worked a little clunky. I have since upp'd the transformer size and all is well.

        I ran the person motion test again and it does appear that the verbose log contains the second motion event but perhaps it cancels the first one if I am reading this right?

        First motion event 12:46:06.
        Second motion event 12:46:38

        I received both RING app notifications time stamped at 12:46PM. The first one reported as "Answered Motion (Person)", the second as "Person Detected"

        *Oh and it expired No Motion at 12:47:40

        See attached. I hope this helps
        Attached Files

        Comment

        Working...
        X