Announcement

Collapse
No announcement yet.

Limits to number of instructions in an Event?

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

    Limits to number of instructions in an Event?

    I'm wondering if there is a practical limit to the number of actions I can include within an event?
    I have a "bed time" event where it's supposed to action on about 20-25 things (i.e. turn lights off, set flags etc) and it seems to have been working fine for years, but lately, it seems that the items towards the bottom of the event are not getting executed. This includings an email-to-self test as the last step.

    I tried inserting a few WAIT 2sec commands, in case it was a problem with too many commands in a row. But that did nothing.

    Does anyone have any insight into this?
    Comments and thoughts always appreciated.
    Thanks
    -steve


    Date/time=2/17/2023 12:24:58 PM EST
    Version=HomeSeer HS4 ZEE S2 (Upg from HS3ZS2) Edition 4.2.16.0 (Linux)
    MONO Version=Mono JIT compiler version 5.16.0.179 (tarball Thu Oct 4 13:39:39 UTC 2018)

    License=Registered
    Confguration File=/usr/local/HomeSeer/Data/HomeSeerData.json
    Uptime=1 Day 10 Hours 18 Minutes 52 Seconds
    Lan IP=192.168.15.10 (HomeTrollerZeeS2V5)
    Device Count=372
    Event Count=249
    Plugins Enabled=EasyTrigger:,Z-Wave:,AK Weather:
    Modules/Threads=81 Modules, 54 Threads
    Available Threads=399
    HomeSeer Memory Used=132 Mbytes
    Plugins Installed=AK Weather 4.0.4.38,EasyTrigger 3.0.0.76,Z-Wave 3.0.10.0
    Disk Size=28.97GB​

    #2
    I am sure there is some practical limit but I doubt that limit would be 20 or 25 actions.

    You could try breaking the event into multiple events and see what happens.

    Comment


      #3
      I know it doesn't directly answer your question about how many in an event, but I ran into the same issue. As mentioned above, I broke into different events. My groups are broken up by a Group for Rooms where there is an Off and On event for Every Room in the house. I then have Events grouped by Floor of the house. The screen shot below is the first floor of my house. I have a separate master event for the second floor and Basement. The basement, first and second floors are within the House master event. When we go to bed we simply tell alexa goodnight which triggers the House master event and shuts everything off that needs to be off. I have 139 zwave nodes of which about 40 are called through this process and it works like a champ with no issues whatsoever. I know many folks use the Groups somewhat differently than me, but this has worked for me for years and meets the needs of my household.

      Click image for larger version

Name:	image.png
Views:	217
Size:	144.5 KB
ID:	1593518​

      Comment


        #4
        I wonder if there's a problem with one (or more) of the actions and that's what's causing the bigger problem.

        For me, I have several "Run another event..." actions as a part of our "good night" routine and those have been working fine for several years. I also find it makes maintenance a bit easier in that I can make a change in a room and only have to change the On and/or Off events for that room.
        "if I have seen further [than others], it is by standing on the shoulders of giants." --Sir Isaac Newton (1675)

        Comment


          #5
          Originally posted by drhtmal View Post
          I am sure there is some practical limit but I doubt that limit would be 20 or 25 actions.

          You could try breaking the event into multiple events and see what happens.
          Definitely - I will try that, thanks.

          Comment


            #6
            Originally posted by stubble36 View Post
            I know it doesn't directly answer your question about how many in an event, but I ran into the same issue. As mentioned above, I broke into different events. My groups are broken up by a Group for Rooms where there is an Off and On event for Every Room in the house. I then have Events grouped by Floor of the house. The screen shot below is the first floor of my house. I have a separate master event for the second floor and Basement. The basement, first and second floors are within the House master event. When we go to bed we simply tell alexa goodnight which triggers the House master event and shuts everything off that needs to be off. I have 139 zwave nodes of which about 40 are called through this process and it works like a champ with no issues whatsoever. I know many folks use the Groups somewhat differently than me, but this has worked for me for years and meets the needs of my household.

            Click image for larger version

Name:	image.png
Views:	217
Size:	144.5 KB
ID:	1593518​
            Outstanding breakdown! I love the multi-level modularity and I'm kicking myself why I haven't done this because once poked in the eye with it, it just seems so obvious and practical!
            I do the same thing with Google - but on a mass-event basis (which is actually fairly onerous to udpate)
            I'm off to break them down and debug as need from there.
            Thanks for taking the time to share this!
            Cheers!

            Comment


              #7
              Originally posted by kenm View Post
              I wonder if there's a problem with one (or more) of the actions and that's what's causing the bigger problem.

              For me, I have several "Run another event..." actions as a part of our "good night" routine and those have been working fine for several years. I also find it makes maintenance a bit easier in that I can make a change in a room and only have to change the On and/or Off events for that room.
              Thanks, I love this modularity model and I'm going to implement it right this minute. Since I already have my devices by rooms, it should be pretty straightforward.
              Wooohoo!

              Comment


                #8
                Originally posted by kenm View Post
                I wonder if there's a problem with one (or more) of the actions and that's what's causing the bigger problem.

                For me, I have several "Run another event..." actions as a part of our "good night" routine and those have been working fine for several years. I also find it makes maintenance a bit easier in that I can make a change in a room and only have to change the On and/or Off events for that room.
                Thanks, I am in the process of modularizing them like this and I will then be in a better position to debug them as you suggest.

                Comment


                  #9
                  I’ve never run into a problem. The largest Event I recall making had about 25 Actions.
                  HS4 Pro, 4.2.18.3 Windows 10 pro, Supermicro LP Xeon

                  Comment


                    #10
                    Originally posted by drhtmal View Post
                    I am sure there is some practical limit but I doubt that limit would be 20 or 25 actions.

                    You could try breaking the event into multiple events and see what happens.
                    Or try disabling certain steps of the existing event to see if it's either the number of actions, or if their is a problem with one or more of the events called. What does the log show?

                    Comment


                      #11
                      Originally posted by Otto-mation View Post

                      Thanks, I am in the process of modularizing them like this and I will then be in a better position to debug them as you suggest.
                      One other thing you might find useful and that is I use LOCATION2 for devices as "Technology" instead of "Floor". I know what floor my kitchen is on, but it's nice to quickly see what technology is being used in a given room. When troubleshooting an event, I can quickly determine if it's event logic, something technology related (i.e Z-Wave, Zigbee, etc), or a problem with a specific device or group of devices.

                      Others have said they use functional groups like lights, motions sensors, etc. and that could be useful as well. It would be nice if "Categories" were better integrated into events.
                      "if I have seen further [than others], it is by standing on the shoulders of giants." --Sir Isaac Newton (1675)

                      Comment


                        #12
                        Otto-mation We don't have a limit to the number of actions in an event. Were there any errors in the log when your event executed? That would be the first place I would look.
                        💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products​

                        Comment


                          #13
                          Originally posted by kenm View Post

                          One other thing you might find useful and that is I use LOCATION2 for devices as "Technology" instead of "Floor". I know what floor my kitchen is on, but it's nice to quickly see what technology is being used in a given room. When troubleshooting an event, I can quickly determine if it's event logic, something technology related (i.e Z-Wave, Zigbee, etc), or a problem with a specific device or group of devices.

                          Others have said they use functional groups like lights, motions sensors, etc. and that could be useful as well. It would be nice if "Categories" were better integrated into events.
                          Very useful tip and it just went into my Debugging notes. Thanks for sharing.
                          I agree, the introduction of Categories was a good start. I also hope to see more integration in there

                          Comment


                            #14
                            Originally posted by macromark View Post
                            Otto-mation We don't have a limit to the number of actions in an event. Were there any errors in the log when your event executed? That would be the first place I would look.
                            Thanks for responding. Very good to know.
                            I wasn't able to determine root cause, even from the log.
                            But as part of a debugging tip from another user, I broke down my bedtime routine into room-specific events, to help localize it.
                            And at the end of each Room event, I include a WriteLog Command to indicate that particular event completed to the end.

                            And of course, once I did all of this, the problem no longer occurred.

                            Comment

                            Working...
                            X