Rule machine - as per the app developer, this app is no longer available for new installs, distribution, or support

[bravenel (Bruce)]

There is a new release of RM. See this post:

Rule Machine Version 1.7 Released

Version 1.7.4 released This update rearranges the UI a bit. There is a new first page, where you decide what you want to setup. There are three choices: Define a Trigger Define a Rule Define just Actions Your existing Rules will show up as one of these, depending on what you created. I want users to distinguish between a Trigger (even one with Conditions and a Rule) and a Rule, which has no Triggers at all. These are fundamentally different. Hopefully, this will help maintain that distinction as you think through your automations. If you have an existing Rule that you want to change into a Trigger or just actions, my suggestion would be to remove it and start over. Rule github: https://github.com/bravenel/Rule-Trigger/blob/master/smartapps/bravenel/rule.src/rule.groovy. Save and …

[EldRitch]

Got it - I know it was in there somewhere.

[toliver182]

@bravenel

Hi Bruce

Any chance of adding the musicPlayer capability?

I’ve added it locally but would love to see it in the main branch

[bravenel (Bruce)]

Send me a pull, so I can see what you’re doing.

[toliver182]

Will do, it’s not in GitHub yet.

I essentially just clones water sensor and changed it to use currentStatus.

I’m not sure that status is defined yet as musicPlayer seems to have been created for sonos , so I set it to use “playing” “paused” and “stopped”

I’ll ping you when it’s in git

[daven]

Maybe a bug here, not sure but I’m running out of hair
I deleted all my Dim Follow Me Apps and used RM instead. 3 of my virtual dimmers and their associates are acting nice. My Rec Room however will not pick up the OFF trigger. The logs show the virtual dimmer getting the trigger but the children in the rule never get a whisper in the logs when OFF is triggered - only ON; I have to turn them off manually every time I test.
I have deleted and recreated the rules and am running up to date code.

Using Virtual switch turn on/off

70fdf6f0-8796-4790-9c80-7d0d41554769 6:32:30 PM: info Rec Room VDimmer Off Triggered
70fdf6f0-8796-4790-9c80-7d0d41554769 6:32:30 PM: info Rec Room VDimmer Off: Rec Room VDimmer switch off
dcb07fa3-cc75-4bac-a3f5-1fff29760f80 6:32:29 PM: debug updating TS
dcb07fa3-cc75-4bac-a3f5-1fff29760f80 6:32:29 PM: debug event from: Rec Room VDimmer, value: off, source: DEVICE, description:
7ab61593-4ae8-4b9f-8a9d-5b1a72305354 6:32:29 PM: debug updating TS
7ab61593-4ae8-4b9f-8a9d-5b1a72305354 6:32:29 PM: debug event from: Rec Room VDimmer, value: off, source: DEVICE, description:
4d38acb7-4583-4615-a3c2-8c7bdf298253 6:32:29 PM: info off
dcb07fa3-cc75-4bac-a3f5-1fff29760f80 6:32:19 PM: debug updating TS
dcb07fa3-cc75-4bac-a3f5-1fff29760f80 6:32:19 PM: debug event from: Rec Room VDimmer, value: on, source: DEVICE, description:
7ab61593-4ae8-4b9f-8a9d-5b1a72305354 6:32:19 PM: debug updating TS
7ab61593-4ae8-4b9f-8a9d-5b1a72305354 6:32:19 PM: debug event from: Rec Room VDimmer, value: on, source: DEVICE, description:
4d38acb7-4583-4615-a3c2-8c7bdf298253 6:32:18 PM: info on

[bravenel (Bruce)]

@daven

3 of my virtual dimmers and their associates are acting nice. My Rec Room however will not pick up the OFF trigger.

So what is different between those that work and those that don’t? Are the Rules similar? What about the devices? Makes no sense that it works in one case and not another.

[daven]

Rules were all the same. Took a while to figure out that the nice, simple working rules were on smart bulbs only. Manupulating them was easy as the virtual switch and bulbs stayed in sync. When dealing with real in wall switches you can’t use the same approach. The virtual switch and the children are not bound together like they were in the dedicated app or with smart bulbs. I had to add extra on’s and off’s to get SmartTiles to reflect the state of the VDimmer

[toliver182]

@bravenel

Hi Bruce.
I have submitted the pull request, hopefully a simple change and i haven’t overlooked anything.

https://github.com/bravenel/Rule-Trigger/pull/11

[sphen]

@bravenel

Limitation: a rule may only have at most one each of Days of week, Mode, or Time of day as conditions. If you need logic for two different Time of day periods, that would have to be done in two separate rules. A trigger can have at most one each of Certain Time or Mode change as a trigger event. If you need more time events, that would have to be done in separate triggers.

Hey bruce – great app! just learning myself and love using this app as a base for all my automations…

quest regarding the above as i see you mention it alot… how does this limitation react if you use some of the “More options” like “only during a certain time” or “only when mode is” with a condition that falls within the limitations? for example i could see using a time of day condition with a only when mode is etc etc – is that a no no?

thanks!

[bravenel (Bruce)]

@sphen

quest regarding the above as i see you mention it alot… how does this limitation react if you use some of the “More options” like “only during a certain time” or “only when mode is” with a condition that falls within the limitations? for example i could see using a time of day condition with a only when mode is etc etc – is that a no no?

Restrictions work differently. For the Rule to do anything, none of the restrictions can be in affect. So you can have mode restrictions, time restrictions, days-of-week restrictions, and disable switch all in the same Rule or Trigger. They are all checked whenever the Rule does anything, including something delayed.

[kjdayley (Kurtis)]

I’m running version 1.7.0/1.7.4a. Since this upgrade I am having a lot of UI errors on my iPhone and some seemingly associated failures of rules to execute properly. The main symptom of failures are lights that are automatically turned on (with motion in most cases) not turning off as expected. The UI error that I am getting is “Failed to save page: selectRule”.

[bravenel (Bruce)]

@kjdayley

The main symptom of failures are lights that are automatically turned on (with motion in most cases) not turning off as expected.

This was happening a lot yesterday, and is something related to the platform. That UI error is generally also a platform issue.

[Mr_Lucky (Bob)]

@bravenel, I have noticed that ever since custom commands were introduced, they appear in all rules when viewed within the IDE - even ones that don’t utilize the command. They appear under Application State > cstCmds. This appears to be normal. What doesn’t appear to be normal though is that newly added custom commands do not appear (in cstCmds) until each individual trigger/rule is gone into and hit Done.

What do you make of this, and is there any downside to ignoring it and doing nothing?

Edit: forgot to add that the new command itself works for its intended purpose.

[bravenel (Bruce)]

@Mr_Lucky

What do you make of this, and is there any downside to ignoring it and doing nothing?

Edit: forgot to add that the new command itself works for its intended purpose.

This is just an artifact of the way that custom commands are passed from the parent (Rule Machine) to the child app (Rule). It makes no difference, and as you observe, the commands work once selected.

[bravenel (Bruce)]

Version 1.7.5 Released

This new version addresses scheduling issues in SmartThings. See this post:

Rule Machine and ST Schedule Woes

Continuing the discussion from Scheduled Jobs Failing AGAIN: As many of you are aware, there are ongoing issues with scheduled events in SmartThings. While these are being worked on, some new issues have surfaced. One of these issues concerns the use of unschedule() by SmartApps. Beginning yesterday or the day before, users have also seen errors thrown that say “Undeclared Throwable Exception”. As far as I can tell, these are being thrown by unschedule(). For over a year, there has been discussion about how unschedule() is not reliable, and sometimes pays a high execution time penalty, so much so that some apps would be killed due to exceeding 20 seconds runtime. Pollster is one app that has had this problem. It became clear, that Rule Machine also was vulnerable to this failure. S…

Rule github: https://github.com/bravenel/Rule-Trigger/blob/master/smartapps/bravenel/rule.src/rule.groovy. Save and Publish for me.

[r4nd0m]

does this require to re-touch all configured rules when you update?

is there any option to configure getting the latest update automatically?

[bravenel (Bruce)]

@r4nd0m

does this require to re-touch all configured rules when you update?

No, you don’t have to do anything with your Rules. They always run the current version of Rule.

[dsbeck (Dave Schierenbeck)]

Do I have to do anything special to update the new version of RM in the IDE?

I assume I just copy the new code to replace the old code, save and publish for me?

Thanks,

Dave

[ahow628]

The original post has a section with instructions for forking Bruce’s github. Then you can just replace changes, save, and be good to go. No copy paste required.