Announcement

Collapse
No announcement yet.

HS-WD100+ 2-tap & 3-tap doesn't always fire

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

    HS-WD100+ 2-tap & 3-tap doesn't always fire

    I have a number of HS-WD100+ each on firmware 5.19 and have noticed that sometimes the controller does not get the 2 or 3 tap events.

    This same problem existed on 5.16 and 5.14 also.

    Was hoping others have seen this same problem and either know how to fix it or HS can take a look...

    #2
    Similar issue here, too....
    .

    Comment


      #3
      Has not happened to me. First question, are these devices connected to the root Zwave transceiver directly or is there a hop in between them and the root Zwave transceiver?


      Sent from my iPhone using Tapatalk

      Comment


        #4
        That was happening to me till I figured out I wasn't using the right test in an event. You can't use a test that detects a "Change" you must use the one that detects being "Set" even if the state wasn't changed.

        Since making that change it's not missed a beat.
        HomeSeer Version: HS3 Standard Edition 3.0.0.548
        Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
        Number of Devices: 484 | Number of Events: 776

        Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
        3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
        4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
        3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave

        Z-Net version: 1.0.23 for Inclusion Nodes
        SmartStick+: 6.04 (ZDK 6.81.3) on Server

        Comment


          #5
          TWO great points! Will check tonight. THANKS!
          .

          Comment


            #6
            I wasn't where I could easily view what setting I used so here it is.

            Use the setting "This device had its value set to...".

            HomeSeer Version: HS3 Standard Edition 3.0.0.548
            Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
            Number of Devices: 484 | Number of Events: 776

            Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
            3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
            4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
            3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave

            Z-Net version: 1.0.23 for Inclusion Nodes
            SmartStick+: 6.04 (ZDK 6.81.3) on Server

            Comment


              #7
              Originally posted by Timon View Post
              ...You can't use a test that detects a "Change" you must use the one that detects being "Set" even if the state wasn't changed.

              Since making that change it's not missed a beat.
              Thank you, thank you, thank you. I switched all my event to "set" vs "change" and they fire each and every time.

              Comment

              Working...
              X