[Deprecated] Device Sequencer

Am I reading right that it's limited to 5 groups? I have 10 rules to turn stuff off when I go to Night mode and 13 to go to Away mode, 3 devices at a time spaced 1 second apart...when I lumped everything into 1 rule it would take 20-30 seconds for everything to actually turn off so had to split up. Wouldn't mind trying this but need more than 5 delay groups.

Edit... Might be able to combine groups if I mix different protocols in the same group...

I can easily add more groups but remember, you can have as many devices per group as you like and you can make as many child apps as needed too. With this in mind I haven't had a need for more than 3 groups...so I added 5 because I just knew someone would want more! lol. So the question is, How many groups should I make it?

Also, @wxmiked ... I got something in the works for you too. Stay tuned... :wink:

Let me see if I can condense to your current 5 before I formally ask for a change. The reason for doing this in the first place was that bulk commands being issued at the same time seemed to flood the mesh and introduce significant delays between a command being sent and the device responding. Sending 3 commands at a time has remedied the problem. But I can probably mix protocols within the same group...sending 3 z-wave, 3 zigbee, and 3 virtual device commands at the same time shouldn't cause any problems.

I'll get back to you on this....thanks for the app BTW :slight_smile:

1 Like

@bptworld, seems like you are trying to take over for @Cobra now that he is one of "them" :wink:
I expect to see a title change for you too..Developer.

Keep churning em out buddy.

PS
I scanned through the code. Never knew about the pauseExecution() option. It seems to be much better than the delay method I was using. Good stuff!

Thanks... I'm just really bored and coding gives me something to do! Most of the apps are not too complicated but they all fill a gap that I had in my system. And if someone else finds them useful, Bonus. :grin:

No replacing @Cobra, he was a huge help to me when I started coding for Hubitat. I still put a 'thank you' into every single app I put out!

1 Like

Will Do!

check this out... :grin:

@bptworld, First of all thanks for sharing all your great apps. I just installed Device Sequencer and was getting an error stating that the Child device could not be found. Noticed that line 57 "parent: "BPTWorld:Device Sequencer"" in the child app was commented out. I removed the comments and it is now working. Any reason that was commented out?

Ha, I must of been testing something. Thanks, it's fixed now.

Great thanks! I always like to confirm just in case.
“Don't ever take a fence down until you know the reason it was put up” GK Chesterton

1 Like

Hey, started working with this today in conjunction with the Send IP2IR app. I'm not seeing Group 1:

It's working if I only enter Groups 2 - 5, but I thought I'd let you know.

Also, guessing the 'null-' should be saying something else?

image image

Other than that, working as expected. Thanks!

1 Like

New version on GitHub...

Bug fixes

1 Like

@bptworld, I'm fairly new to Hubitat and have been checking out Device Sequencer, which works nicely for sequential power-up, and I want to use it via a virtual switch that can be invoked from Google Home. What would be the best way to effect the following:

  • When switch is turned on, devices power up in the order A - B - C
  • When switch is turned off, devices power down in the order C - B - A

The use case is for controlling a stereo system, where the On sequence should be source-preamp-amp, while the Off sequence should be amp-preamp-source. Will this require RE to deal with the on/off conditionals? Or is there another way to finesse it? Thanks!

Welcome to Hubitat!

So you need it run in reverse order?

New version:

2.0.4 - 11/14/20 - Added Reverse order on off option

1 Like

Damn Bryan - you’re a coding machine! It took less than 25 minutes from @john21’s request to your putting a new version on GitHub!!

2 Likes

lol, timing is everything. Besides, it was a very easy change. :wink:

2 Likes

Wow, it works!

One thing I notice.

  • I have 5 secs between Groups 1 and 2, and 1 sec between the devices in Group 2;
  • The startup sequence times perfectly;
  • However, while the order of the shutdown sequence is correct, the devices power off in rapid order.

For my use case, I'd like to build in a little buffer between power-off events. Can your code be tweaked to use the inter-device startup timing variables during the shutdown sequence?

Cheers!

Yup, looks like I missed this part. Give it another try.

New version:

2.0.5 - 11/14/20 - Adjustment

1 Like

Perfectamundo, bro!

Thanks very much!!

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.