Announcement

**drhtmal** · February 17, 2023, 12:31 PM

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.

**stubble36** · February 17, 2023, 01:40 PM

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.

**kenm** · February 17, 2023, 02:03 PM

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.

**Otto-mation** · February 17, 2023, 03:32 PM

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.

**Otto-mation** · February 17, 2023, 03:35 PM

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.

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!

**Otto-mation** · February 17, 2023, 03:36 PM

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!

**Otto-mation** · February 17, 2023, 04:10 PM

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.

**randy** · February 17, 2023, 04:13 PM

I’ve never run into a problem. The largest Event I recall making had about 25 Actions.

**Kevb** · February 17, 2023, 08:34 PM

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?

**kenm** · February 18, 2023, 12:57 PM

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.

**macromark** · February 23, 2023, 03:57 PM

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.

**Otto-mation** · March 17, 2023, 01:07 PM

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

**Otto-mation** · March 17, 2023, 01:13 PM

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.

Announcement

Limits to number of instructions in an Event?

Limits to number of instructions in an Event?

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment