Announcement

Collapse
No announcement yet.

Whats wrong with this event?

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

    Whats wrong with this event?

    I made 2 conditional event with the following rules:

    Event 1:

    Trigger: Ligth(1) on or ligth (2)on

    Action: Turn pump on

    Event 2:

    Trigger: Ligth(1) off and Ligth (2)off

    Action: Turn pump off


    the problem that aim having is that when I check the log, these event keep on triggering. The ligth above mentioned are triggered by motion sensors. My question is:

    How do i tell it to fire once when the ligth is on ??

    How do I tell it to fire once when the ligth is off ??



    Can somebody shed some ligth?
    Last edited by Rotech; June 30, 2008, 09:14 PM.
    Hector
    ____________________________________
    Win.2003 OS, HS3
    BLDSC,BLstat,BLRadar,BLRamdom,BLOccupied
    BLups,BLrain8,HSTouch,Ultrajones Weatherbug,
    MyTrigger,ACRF2,W800,Zwave
    AP800,Honeywell Stat

    #2
    well what im thinking is this.... if your using a motion sensor... you will always have the logs full of on's....

    is everything working correctly but you just dont want so much in the log?

    if that is the case then you can do 2 things..

    1. on the device setup check off Do not log commands from this device
    2. within your event then throw a hs.writelog to get the logged data.... but only do that for the on and off of the actual pump....


    im just double checking with you that your main concern is mainly so much in the log..... I actually checked that box off on alot of my devices.... just dont want so much crap in my logs.....
    HW - i5 4570T @2.9ghz runs @11w | 8gb ram | 128gb ssd OS - Win10 x64

    HS - HS3 Pro Edition 3.0.0.435

    Plugins - BLRF 2.0.94.0 | Concord 4 3.1.13.10 | HSBuddy 3.9.605.5 | HSTouch Server 3.0.0.68 | RFXCOM 30.0.0.36 | X10 3.0.0.36 | Z-Wave 3.0.1.190

    Hardware - EdgePort/4 DB9 Serial | RFXCOM 433MHz USB Transceiver | Superbus 2000 for Concord 4 | TI103 X-10 Interface | WGL Designs W800 RF | Z-Net Z-Wave Interface

    Comment


      #3
      This is where DooMotion really shines - handling multiple ONs from motion sensors.

      Without DooMotion, I think you have a couple of options (off the top of my head). To your ON event, you could add "and has been OFF for x minutes" and for your OFF event, add "and has been ON for x minutes"

      or

      Create a virtual device and add that to your ON/OFF events - if this virtual device is ON and your ON event fires, turn on the pump. Same for the OFF event, except check to see if the virtual device is OFF. You then control the ON/OFF of the virtual device as needed.

      Hope this helps...
      HS4Pro on a Raspberry Pi4
      54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
      Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

      HSTouch Clients: 1 Android

      Comment


        #4
        This should work exactly the way you want it to:

        Event 1:

        Trigger: Light(1) CHANGED to ON and light(2) OFF (Group 1)

        or

        Trigger: Light(1) OFF and light(2) CHANGED to ON (Group 2)

        Action: Turn pump on

        Event 2 :

        Trigger: Light(1) CHANGED to OFF and Light (2) OFF (Group 1)

        or

        Trigger: Light(1) OFF and Light (2) CHANGED to OFF (Group 2)

        Action: Turn pump off
        Last edited by fran_joel; July 1, 2008, 06:02 AM.

        Comment


          #5
          Fran-joel

          what is the diference having the event made this way?

          Originally posted by fran_joel View Post
          This should work exactly the way you want it to:

          Event 1:

          Trigger: Light(1) CHANGED to ON and light(2) OFF (Group 1)

          or

          Trigger: Light(1) OFF and light(2) CHANGED to ON (Group 2)

          Action: Turn pump on

          Event 2 :

          Trigger: Light(1) CHANGED to OFF and Light (2) OFF (Group 1)

          or

          Trigger: Light(1) OFF and Light (2) CHANGED to OFF (Group 2)

          Action: Turn pump off
          Hector
          ____________________________________
          Win.2003 OS, HS3
          BLDSC,BLstat,BLRadar,BLRamdom,BLOccupied
          BLups,BLrain8,HSTouch,Ultrajones Weatherbug,
          MyTrigger,ACRF2,W800,Zwave
          AP800,Honeywell Stat

          Comment


            #6
            Originally posted by Rotech View Post
            Fran-joel

            what is the diference having the event made this way?
            Maybe due to the value being Changed vs turned on..

            so if the item is on, your event will run, every time a motion kicks on your event will run..

            by setting when the device is Changed to on - then when it is on... the event will not re fire up due to the device is already on...

            I believe this is how I use the motion in my garage for the lights......
            HW - i5 4570T @2.9ghz runs @11w | 8gb ram | 128gb ssd OS - Win10 x64

            HS - HS3 Pro Edition 3.0.0.435

            Plugins - BLRF 2.0.94.0 | Concord 4 3.1.13.10 | HSBuddy 3.9.605.5 | HSTouch Server 3.0.0.68 | RFXCOM 30.0.0.36 | X10 3.0.0.36 | Z-Wave 3.0.1.190

            Hardware - EdgePort/4 DB9 Serial | RFXCOM 433MHz USB Transceiver | Superbus 2000 for Concord 4 | TI103 X-10 Interface | WGL Designs W800 RF | Z-Net Z-Wave Interface

            Comment


              #7
              Originally posted by Rotech View Post
              Fran-joel

              what is the diference having the event made this way?
              Because this way, it works...


              Seriously, the main difference is having CHANGED to ON as the trigger and not is ON or is OFF.

              A device only changes to ON once, but is ON continuously after that... In terms of defining a trigger, it makes a huge difference.

              If you select is ON or is OFF as a trigger, it will trigger repeatedly because the trigger condition is always true as long as your device remains ON or OFF.

              If you select CHANGED to ON or CHANGED to OFF as a trigger, it will trigger only once when the device changes state, which is what you want here.
              Last edited by fran_joel; July 1, 2008, 08:31 AM.

              Comment


                #8
                Thank you for the explanation, now it does make sense!!
                Hector
                ____________________________________
                Win.2003 OS, HS3
                BLDSC,BLstat,BLRadar,BLRamdom,BLOccupied
                BLups,BLrain8,HSTouch,Ultrajones Weatherbug,
                MyTrigger,ACRF2,W800,Zwave
                AP800,Honeywell Stat

                Comment


                  #9
                  The other way you could do it is add another condition to event 1 that the pump is OFF and to event 2 that the pump is ON. That way it with only trigger once to get the pump into the state you want.
                  Dick
                  HS PRO 2.5.0.81, WinXP, IE8, Shuttle XS35V3, 2.13GHz, 4GB, 40GB SSD drive, AC-RF2, ADIOcelot, Message Server, TI103, SNEVL CID, pjcOutlook, MCSTemperature, Powertrigger, BLBackup, BLFloorplan, BLIcon, BLOccupied, BLRadar, BLRfid, BLLogMonitor, ACPUPSD, UltraECM, WeatherXML & Stipus' script connector. 500+ devices, 260+ events, 1-wire weather station + temp/humidity sensors & Oregon Scientific temp & humidity sensors & 2 Brultech ECM-1240s

                  Comment

                  Working...
                  X