Enhancement Request: Rules grouping

Rule engine is so useful and number of rules is growing fast.

Browsing and maintaining these many rules would be easier if possible to group the rules, maybe presenting them in ‘tree view’, so I can expand/collapse a group of rules.

A possible grouping method could be group by SmartThings rooms/areas, another option is to let the users create their own groups and assign the rules to these groups respectively.

Thanks!

@Roy_Kfir, thanks for the feedback. @Justin_Newbury has suggested this related rule grouping concept by allowing users to set the rule’s color/icon so they are visually grouped in the rule list. So your feedback is important in helping us design the grouping feature. I’ve noted your feedback to this item in my list. Let’s see if anyone else wants to share their thoughts here too. :smiley:

4 Likes

Grouping sounds like a great idea to me. I would want the ability to collapse/expand rather than organize by color or icon. I want to reduce visual clutter and make it easier to find a rule quickly.

I could also see some sort of filtering capability. For example, I know my rule involves a particular device… show rules that involve this device.

One question I have (slightly off topic). Most of my rules are setup as automations in ST. Is there a good reason to convert my automations over to SharpTools rules? I haven’t actually looked into whether my automations run on my hub or not, but I figured I had the greatest chance of running them locally if I used automations.

1 Like

Thanks for the feedback, I am also wondering if a search bar at top would help filter based on the keywords in the rule name and description.

At this moment, keeping the simple automation in the ST may have the benefit of local execution as long as the device handler supports local execution. Automation like turning light on when motion detected without further conditions can be those to keep in ST at this point. (~200ms vs ~1sec difference in the rule execution performance)

1 Like

You made a comment in a Samsung dev con YouTube video I watched that you were looking into running Rule Engine rules locally in the hub, if I understood that correctly. Is that really a possibility? Can you do that in Hubitat? (I’m thinking about switching)

We implemented a proof of concept using the new SmartThings Rule API leading up to the Samsung Developer conference. SmartThings has indicated that they have plans to introduce local support for the Rule API, so it’s something we might revisit in the future once local support is added to the API. :grinning:

Hubitat offers their own rule feature called ‘Rule Machine’. It runs locally on the hub, but it’s not exposed as an API that we could build on.

1 Like

I’d love rule organization as well. Expand and collapse as well as room groupings would be my preference.

1 Like

Do you know if Hubitat has plans to open their API so rules could get executed locally? I just bought a Hubitat hub and still have most devices on SmartThings and was thinking about migrating to Hubitat only so things could run locally but the SmartThings plan to support local rule execution now has me reconsidering.

1 Like

Rules built with Hubitat’s own Rule Machine execute locally. I don’t know if they have any plans to open up an API for creating Rule Machine rules, but that is a neat suggestion!

Yes, but I like the sharptools rule engine better, seems to be more customizable as far as tiles go. Can I have a tile for a Hubitat rule? I guess it would just act as a virtual button to execute the rule and the rule would execute locally on my Hubitat, right?

Since I still have a SmartThings hub with devices, I’m using sharptools to aggregate all of my devices so I’m using sharptools for all rules.

2 Likes

A common approach is to create a Virtual Switch or Virtual Momentary device. Then you can control that device from your SharpTools dashboard or rules… and use it as a trigger in your Hubitat Rules.

Not sure I’m following this. You’re talking about a virtual button in my Hubitat to execute the rule, right? Is that a “device” that can be seen by sharptools?

Yes, you can create a virtual device in Hubitat and then authorize that in SharpTools.

So from SharpTools, you could flip the Virtual Switch on… then in Hubitat’s Rule Machine, you could build a rule that would react to the switch turning on.

You could either have the Hubitat rule turn the virtual switch back off or Hubitat’s Virtual Switch can be configured with an ‘Auto Off’ Setting which makes it act like a bit like a button (stateless):

@Roy_Kfir, @Aaron_Drysdale, and @Alex_Burrows, thanks for the feedback here. We just rolled out the search feature yesterday, which is our first step in better organizing rules. Please see the release notes below for more details, and hope you guys find the search feature helpful. :wink:

2 Likes