@bravenel
Just spending the day converting every thing over to Rule and notice an oversight for us Metric people.
I can’t set temperatures with decimal places; when using C(elcius) a full degree is almost 2 F so there are a lot of times I need a .5.
Tackling the arrival/departure presence sensors and mode changes last as this looks the most messy.
I will look into this. I wondered about C vs F.
1 Like
triggers would be helpful in a sense that they could be used when a condition is already true, but you want the action to take place when the trigger happens. (you want X to happen if Y switch is on, but not when y switch changes states, just that it is on, but X can’t happen if Y switch is off) hopefully that is not clear as mud lol.
I understand what you’re saying, but that’s not quite the same thing as the triggers that are for manual execution.
What you’re really looking for is a “while” condition, not a trigger. And those are really really hard to do in mesh architecture because you can’t guarantee the sequence in which events take place.
Smartthings offers two while conditionals: mode and SHM arm state. Those are evaluated at the account level. Everything else is by event subscription, so very hard to fit into a while.
Which is to say you may have a use case where you’re pretty sure it will work at your house, but writing code that would make it work for everybody just doesn’t really match the reporting tools available.
New release today (yet again 
) Version 1.2.0
Release notes:
- Now you can set colors as an action; only a small selection of colors available
To update: copy code for Rule from Github https://github.com/bravenel/SmartThings/blob/master/Rule
Paste it into Rule in IDE, overwriting previous version, and Save. Do not publish!
1 Like
in thinking about it, it’s more of an IF than WHILE, but similar
Not sure if you did anything to address this but I had the SmartThings app crash again today while building a rule. This time I was able to open the rule and continue building it. I was never able to to this before.
FYI - I am running BlueStacks on my Mac Air so the SmartThings app has a tendency to crash a lot.
@jnschemm - mine crashed every few minute but I finally got all the rules in, wheeew!
@bravenel I know this is probably out of the scope of this project but I’ll toss it out there anyway. 
All my ST routines (Good…, I’m Back…) are gone now and handled in RM, I’ll wait to see how well I did 
The ST widget on my Android phone is now empty so can’t hit a quick “I’m Back” if the cloud is slow and I’m standing at the front door like dufus staring at an inanimate object.
Is there a method to link ST’s app with the RM routines so that ST can then populate the widget?
You would need a user definable flag to designate which rules were to be linked to ST as well if this is possible
There’s nothing preventing you from keeping the ‘I’m Back!’ routine but removing all automatic triggers. That way, your widget will still be populated, but do nothing unless you tap it.
That’s what I was worried about was double triggering of the same routine; hence I delete the ST routines after creating the RM ones.
@bravenel Can you access each rule somewhere (IDE?) to delete them? I have a rule that was incomplete when ST app went POOP! again. Now, no matter what I do, RM says Unauthorized Access when I try to edit that incomplete rule. 
Yes in IDE. Under location/Smartapp click edit up top.
3 Likes
Awesome, thanks!
Took me a minute to find the “EDIT up top”. Silly place buy the logo and graphics, most of they edit, update and delete buttons are at the bottom left.
wow, quick response, that is awesome. I’ll play with it some more.
I have one instance of a SmartApp (not Rule Machine), that has been missing or not getting mode change events for Night to Day
Independent of the Rule Machine (which looks awesome but I have to try) – I have found that Day - Night transitions have been flaky for months. The Sunrise/Sunset app has never been very reliable for me.
At one point earlier this year I complained to ST Support and someone there theorized it might be because so many commands (in my timezone) were executing in the cloud at once. The suggested solution was to program an offset so that the command would execute at a different time (e.g., 5 minutes before sunset). I tried that, but still found it didn’t work reliably.
Since installing the ‘Routine Director’ SmartApp to manage my day/night scenarios, I haven’t noticed any failures. For whatever that’s worth.
Minor update this morning: Version 1.2.1.
Release Notes:
- allows decimal input for temperatures, for those with degrees Celsius to use temps like 17.2
- supports Fan settings for thermostats, as requested by @kraig109.
To update: copy code for Rule from Github https://github.com/bravenel/SmartThings/blob/master/Rule
Paste it into Rule in IDE, overwriting previous version, and Save. Do not publish!
2 Likes
I think it was removal of certain time, but now getting errors when I attempt to edit one of my rules. Getting the following in logs:
9c68594a-1b56-4e59-916c-31ad3b147751 07:33:53 PST: error java.lang.NullPointerException: Cannot invoke method size() on null object @ line 827
Go into the IDE and delete that rule. Then put it in again.
Awesome, once my computer is done installing updates I will give this a shot.
