Announcement

Collapse
No announcement yet.

Not updating 'same value' via webhook from homeseer to node-red

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

    Not updating 'same value' via webhook from homeseer to node-red

    Hi.
    I might be missing something - but it does seem like homeseer doesn't update a device, that has it's value set to the same value again.
    For instance, pressing the same button on a remote, twice - doesn't send messages to node-red.

    This can be tested by pressing the ON-button on a bulb in hs-web - if the bulb is already on, messages isn't sent to node-red (the timestamp in hs-web is updated, nothing more)

    Im a missing something?

    #2
    I found a similar post where the issue was discussed.
    It IS an issue - my in-wall remote only has a 'pressed' status - which is then translatet to a TOGGLE through node-red and on to conbee.

    This will never work, if homeseer doesn't update the 'pressed' status when the button is pressed.

    Comment


      #3
      This is an issue with both the webhook and the ASCII interface. I first noticed it with central scene controllers like the Zooz Zen32. A workaround is to create an event that "resets" the central scene feature back to 0 (zero) after a second or two. In other words, If the central scene device is set to a value greater than 0, run an immediate script command to set the value back to 0. Using EasyTrigger, you can also copy the value to a virtual device before resetting it, if you want to preserve the "last press".

      Ken
      "if I have seen further [than others], it is by standing on the shoulders of giants." --Sir Isaac Newton (1675)

      Comment


        #4
        That could create problems for the hold/release features - and it's just plain wrong to have such hacks
        But thank you for the workaround.

        The idea was to completely drop the event-handling in homeseer and change it to node-red - which would also be impossible with the workaround.

        Comment


          #5
          If you uncheck the Device's Last Change Time Updates on Status Change Only then the HomeSeer Device Node should trigger your flow. You would now want to poll the device, such as an old z-wave light switch as this would trigger the flow at every polling interval. I tested with an old z-wave switch and the node intiated the flow on every polling event as well as wen I used HomeSeer to send an Off command when the switch was already off.

          I am referring to the setting highlighted below.
          Click image for larger version

Name:	HS1.png
Views:	136
Size:	38.7 KB
ID:	1498905

          Karl S
          HS4Pro on Windows 10
          1070 Devices
          56 Z-Wave Nodes
          104 Events
          HSTouch Clients: 3 Android, 1 iOS
          Google Home: 3 Mini units, 1 Pair Audios, 2 Displays

          Comment


            #6
            Thank you ksum!
            It's working - you are the best!

            Comment


              #7
              Originally posted by lurendrejer View Post
              Thank you ksum!
              It's working
              Glad this gets you what you need. Now let's get some interesting Node red flows going!

              Originally posted by lurendrejer View Post
              ... you are the best!
              I wouldn't go that far... Might get all full of myself or something... 😉
              Karl S
              HS4Pro on Windows 10
              1070 Devices
              56 Z-Wave Nodes
              104 Events
              HSTouch Clients: 3 Android, 1 iOS
              Google Home: 3 Mini units, 1 Pair Audios, 2 Displays

              Comment

              Working...
              X