Announcement

Collapse
No announcement yet.

Detecting string changes

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

  • Detecting string changes

    Spud,

    We're having a discussion here about the ability of the json setdeviceproperty to change a string's value. Rich and the documentation say it can be done, but it doesn't work. Even if it can be made to work, Rich says it won't generate an HS event. If it doesn't would easytrigger still detect the change? How? Do you continuously check the value to see if it has changed?

    It would be great if you could come and weigh in on this discussion.

  • #2
    As Rich said in this thread, the EasyTrigger plugin registers with HS for string changes on devices, so it only gets called when a change actually happens (i.e. no continuous check of the string) and it fires the "A device's string is..." triggers accordingly.

    Comment


    • #3
      Great. Thanks.

      Comment


      • #4
        Hi Spud,

        Circling back on this one. I'm using the JSON string update mentioned above and also changing the update to true as well based on this added functionality:

        Originally posted by rjh View Post
        There was some protection on the properties, I have put in a fix in build 304 which is posted here:

        http://forums.homeseer.com/showthread.php?t=181241

        To set them and trigger events, do this:

        Code:
        http://IP/JSON?request=setdeviceproperty&ref=####&property=NewDevString&value=STRING_VALUE
        http://IP/JSON?request=setdeviceproperty&ref=####&property=ChangedValueORString&value=TRUE

        The virtual device I'm testing receives the JSON string update and the timestamp update, but EasyTrigger will not fire on the String Changes Trigger. I manually updated the device string via a script and the EasyTrigger fired correctly. Any thoughts as to why it is not firing on these two JSON snippets above?

        Thanks!

        Comment


        • #5
          Originally posted by tamu View Post
          Hi Spud,

          Circling back on this one. I'm using the JSON string update mentioned above and also changing the update to true as well based on this added functionality:




          The virtual device I'm testing receives the JSON string update and the timestamp update, but EasyTrigger will not fire on the String Changes Trigger. I manually updated the device string via a script and the EasyTrigger fired correctly. Any thoughts as to why it is not firing on these two JSON snippets above?

          Thanks!
          you're right, I just tested it and got the same results. I posted in the original thread.

          Comment

          Working...
          X