Announcement

Collapse
No announcement yet.

Problem with two digit motion trigger rules

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

    Problem with two digit motion trigger rules

    Hello, Ultra. I think I may have uncovered a bug in the plugin last night...

    I've been successfully using several events with trigger "Sighthound Video Motion Trigger" for a while now with no problems. But last night I added two new Sighthound motion trigger events, using two digit rules for the first time, and right away I noticed something not right because the wrong events started triggering unexpectedly.

    After some testing, I've discovered that it appears the plugin is truncating the second digit. So, for example, if I send "curl --request GET http://ipaddress/UltraSighthoundVideo3?rule=12" from Sighthound, HS3 actually runs events that have a trigger of "Motion Trigger rule number 1" (instead of "Motion Trigger rule number 12"). If I send "curl --request GET http://ipaddress/UltraSighthoundVideo3?rule=23" from Sighthound, events with "Motion Trigger rule number 2" trigger run.

    Could you please test this on your end?

    #2
    Hello teladog01,

    I have not been able to look into this yet. This is on my todo list for this week. Sorry for the delay.
    Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

    Comment


      #3
      Originally posted by teladog01 View Post
      Hello, Ultra. I think I may have uncovered a bug in the plugin last night...

      I've been successfully using several events with trigger "Sighthound Video Motion Trigger" for a while now with no problems. But last night I added two new Sighthound motion trigger events, using two digit rules for the first time, and right away I noticed something not right because the wrong events started triggering unexpectedly.

      After some testing, I've discovered that it appears the plugin is truncating the second digit. So, for example, if I send "curl --request GET http://ipaddress/UltraSighthoundVideo3?rule=12" from Sighthound, HS3 actually runs events that have a trigger of "Motion Trigger rule number 1" (instead of "Motion Trigger rule number 12"). If I send "curl --request GET http://ipaddress/UltraSighthoundVideo3?rule=23" from Sighthound, events with "Motion Trigger rule number 2" trigger run.

      Could you please test this on your end?
      The issue you reported is a confirmed bug. I will post an update that will fix the issue within the hour.

      Regards,
      Ultrajones
      Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

      Comment


        #4
        Originally posted by Ultrajones View Post
        The issue you reported is a confirmed bug. I will post an update that will fix the issue within the hour.

        Regards,
        Ultrajones
        The update appears to have fixed it for me. Thanks, Ultrajones

        Comment

        Working...
        X