Would it be possible to have an enhancement which allows us to change the type of rule we created?
Example: I create a rule but after i put all of the logig in and run it for a while I determine I need to add a trigger. Right now I need to create the entire rule again as a trigger. It would be awesome if you decided it was a triggered rule it would just give you the addition trigger field to define that.
Anything is possible with software, but this would entail a great deal of effort -- effort that would be better spent on other things. Meanwhile, how much effort really is it to create a new rule? There's an imbalance between the effort this change would take to the benefit that would accrue from it.
I understand from a company perspective that makes sense, but the user experience can be frustrating as your learning to use Rule machine and what really works for you. I am not saying this has to be developed now, but it may be something you want to change with RM.
From a user perspective if 95% of your rule works and you have to rewrite the rule because you selected the wrong rule type, means that you have to rewrite 100% of your rule for a 5% error.
Many of my rules use 90% of my contact sensors so when I rewrite my rules I have to check each contact sensor. It is a pain when I have to update multiple rules because I now need to trigger it.
I guess I can just create another rule as a trigger and then pause/resume/ the rules that need triggers. Just seems like it's making things more complicated than they need to be. It still would be nice to have the enhancement added to another release.
One other suggestion I'd like to make is to offer work arounds to people when they ask for an enhancement. Unless it's a crazy bug, I assume most people are willing to wait especially if a work around is given. Just a friendly suggestion, I am not trying to offend.
Thanks for considering the enhancement for a future release.
Unfortunately, there isn't a simple work-around for a triggered rule. I suppose you can conjure one up by disabling the rule until your trigger goes off, but I wouldn't consider that simple, nor would I recommend it as a work-around.
I understand your frustration with having to rework your rules. We are looking at a method to clone a rule, but I'm afraid even that wouldn't solve your issue with wanting to change a rule from a rule to a triggered rule, since cloning would just make another rule.
There are lots of customers, so we have to weigh all of their interests in making our priorities. I'd be indifferent to what we worked on if we weren't trying to move the ball down the field for all of our customers, So when you say "company perspective", you are really indirectly saying "overall customers' perspective".
Having said all of that, I will look to see if there is some easy way to accomplish what you seek.
It turns out that this is actually very easy to do. So I'm going to put it in.
There is one significant caveat: There are actions available in a rule that make no sense in a triggered rule. Anything that depends on rule truth changing are examples. For instance, Delay Off Pending Cancellation will only work in a rule, not in a triggered rule. These sorts of errors will not be detected at the time the rule is converted to a triggered rule. It will appear as though they are valid actions, but they won't work. Rule truth is never examined in a triggered rule, the rule is simply evaluated when the trigger fires.
Yes please!
Download the Hubitat app
