Announcement

Collapse
No announcement yet.

Test - What is wrong with this Event?

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

  • Test - What is wrong with this Event?

    I helped another member with a problem last night. His system was brought to a screeching halt every time he turned some lights lights on with a HomeSeer central scene. I have seen different people encounter this problem on a number of occasions. I have created the same problem by modifying an Event in my system. Who can spot the problem? For extra credit, what is going on in this Event

    Click image for larger version

Name:	Capture.PNG
Views:	16
Size:	73.6 KB
ID:	1274932
    Randy Prade
    Aurora, CO
    Prades.net

    PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

  • #2
    Loop. Actions set a device which has a set trigger. HS engine not smart enough to realize and all goes poorly.

    Comment


    • #3
      How do you fix or avoid it?
      Randy Prade
      Aurora, CO
      Prades.net

      PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

      Comment


      • #4
        Originally posted by rprade View Post
        How do you fix or avoid it?
        For this one I would change the event form set to to changed to....

        Comment


        • #5

          Originally posted by bsobel View Post

          For this one I would change the event form set to to changed to....
          Thanks for playing

          Hopefully this will help others.

          The loop was caused by "setting" a device in the Actions and a Trigger being based upon the device being "set". I also added Cannot Re-Run For: 5 Seconds.

          Click image for larger version

Name:	Capture.PNG
Views:	14
Size:	88.7 KB
ID:	1274975
          Randy Prade
          Aurora, CO
          Prades.net

          PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

          Comment


          • #6
            That is really good info. I almost always use "changes and becomes" in my events since I'm usually wanting a device that was value 'X' but has changed to value 'Y'.
            HS3Pro Running on a Raspberry Pi3
            64 Z-Wave Nodes, 168 Events, 280 Devices
            UPB modules via OMNI plugin/panel
            Plugins: Z-Wave, BLRF, OMNI, HSTouch, weatherXML, EasyTrigger
            HSTouch Clients: 3 Android, 1 Joggler

            Comment


            • #7
              Since Jon000 has done all the work to decode events maybe we can make a list of common mistakes he can try to highlight if found?

              Comment


              • #8
                Now can anyone tell me why in the world would one set the value of a device in an Event that uses it as a Trigger?
                Randy Prade
                Aurora, CO
                Prades.net

                PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

                Comment


                • #9
                  Originally posted by rprade View Post
                  Now can anyone tell me why in the world would one set the value of a device in an Event that uses it as a Trigger?
                  One scenario that comes to mind: editing an existing event (especially one that has been around for a while) and failing to analyze the effects of the change adequately.
                  Mike____________________________________________________________ __________________
                  HS3 Pro Edition 3.0.0.548

                  HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF, Rain8Net+ | RFXCOM | QSE100D | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3

                  Comment


                  • #10
                    Originally posted by rprade View Post
                    Now can anyone tell me why in the world would one set the value of a device in an Event that uses it as a Trigger?
                    I set the value of devices that triggered the event often. Let say a virtual device is set to 1 (ON) and that is a trigger for an event to run. In the event that got triggered, as a housekeeping chore I will set the value of that device that triggered the event to 0 (OFF).

                    I think maybe your question might be 'why would anyone set the value of a device in an event, to the value that satisfies the trigger of that same event?'

                    Comment


                    • #11
                      Originally posted by logbuilder View Post

                      I set the value of devices that triggered the event often. Let say a virtual device is set to 1 (ON) and that is a trigger for an event to run. In the event that got triggered, as a housekeeping chore I will set the value of that device that triggered the event to 0 (OFF).

                      I think maybe your question might be 'why would anyone set the value of a device in an event, to the value that satisfies the trigger of that same event?'
                      Well, I didn't ask it that way on purpose, because the question would provide a clue to the answer.

                      The Event is designed to run by the value of the Low Light Device, but it also can be run by a remote Central Scene, HS switch Central Scene, Voice Command or HSTouch (as a manual override). The Manual Override device needs to stay in sync. We will double tap the hall light switch in the early morning to turn the lights on when Low Light is not a factor and they will stay on until 1) it becomes late enough in the morning for the Low Light device to turn off or 2) we manually turn them off. We use the manual override device to inhibit the lights from turning off immediately because the light becomes sufficient.

                      Click image for larger version

Name:	Capture1.PNG
Views:	13
Size:	56.6 KB
ID:	1275036


                      Also in both Events as shown in the corrected Event in post #5 above have the Cannot Re-Run For set to keep the event from retriggering if the value of the device is changed. For what it is worth, setting this value would also stop the runaway situation in the original Event triggering on the device being "set".

                      Click image for larger version  Name:	Capture2.PNG Views:	1 Size:	18.0 KB ID:	1275033
                      Randy Prade
                      Aurora, CO
                      Prades.net

                      PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

                      Comment


                      • #12
                        Sorry, I thought you were suggesting that nobody should ever set the trigger device. I missed the inflections in your text.

                        Comment


                        • #13
                          Originally posted by rprade View Post
                          Now can anyone tell me why in the world would one set the value of a device in an Event that uses it as a Trigger?
                          My guess?

                          1) Because the user isn't a programmer or "scripter" and is climbing the ridiculously steep learning curve of a software package that has very poor to non-existent documentation.

                          2) O'Reilly hasn't yet written "Homeseer the missing manual. The book that should have been in the box."
                          HomeSeer Version: HS3 Pro Edition 3.0.0.500
                          Operating System: Microsoft Windows 10 Pro - Work Station

                          Enabled Plug-Ins:
                          2.1.0.119: AmbientWeather | 3.0.21.0: BLLock | 2.0.24.0: BLUPS | 1.3.6.0: Device History | 3.0.0.56: EasyTrigger | 3.1.0.7: MeiHarmonyHub | 3.0.6681.34300: UltraCID3 | 3.0.6644.26753: UltraLog3 | 3.0.6554.33094: UltraMon3 | 3.0.0.91: weatherXML | 3.0.1.245: Z-Wave | 3.0.51: HS Touch Designer | 3.0.0.40 Z-Seer+

                          Comment


                          • #14
                            Originally posted by ewkearns View Post

                            My guess?

                            1) Because the user isn't a programmer or "scripter" and is climbing the ridiculously steep learning curve of a software package that has very poor to non-existent documentation.
                            Or, ironically, it might be that they are a very experienced programmer with a well informed understanding of the power of conditionals and how to finesse them.

                            Comment

                            Working...
                            X