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

[bravenel (Bruce)]

Today has been an interesting day for me with Rule Machine!

There was a bug shown yesterday about sub-rule definition, a missing right paren, that I got to today. That bug was in the core recursive code that builds the rule.

There was a bug shown today about sub-rule evaluation, an evaluation error. This bug was in the core recursive code that evaluates the rule.

And, of course, that’s the hardest code to work with, hard to think through. The second bug was simple once I found it, but that took considerable mental and debugging effort.

Wow! This shows two things:

1. Even seemingly solid code can have unrevealed or unnoticed bugs.
2. People are pushing RM further as they uncover the power of a logical expression in this context.

I wish we had a cool way for people to show off their rules, their automations that they come up with, for other people to see and copy / modify. To that end, I just started a topic where you can show off your automations using Rule Machine. Show us your cool ideas!!

Show your Rule Machine automations

There have been some very cool automations created by people using Rule Machine. Rather than people search 1750 posts in the original Rule Machine topic to find these gems, you should show your Rules and Triggers here. Upload a screen shot of your rule main page, and explain what it does. I’ve seen very cool automations, be they simple or complex!! This will help people see what they can do with Rule Machine, how they can solve their automation needs. To kick this topic off, here is a simple automation similar to one everyone uses, motion on/off lights. This rule turns on a garage light when motion is detected or vibration (acceleration) of the garage door is detected, and then turns the light off after 2 minutes of no motion/vibration. [image]