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

[bravenel (Bruce)]

That’s what I’m calling a headless zombie. It’s happening to lots of people. I had 13 of them yesterday morning, and 8 of them came back. I don’t know what to suggest at this point, because ST cloud is obviously messed up and “degraded”. You can certainly try removing the broken rule, and putting it in again, and keeping your fingers crossed. I’m just waiting to see where they end up with this mess. I’m afraid of putting too much effort in right now.

[kalex1114 (Alex K)]

Haha. That’s what I figured. I’ll disable the rule and leave it as is

[ruricu (Chris Eaton)]

@bravenel

On iOS, putting in 1 for the number of buttons makes the button number field go away. But this feature would not work on Android prior to 2.10. It does work on 2.10. So I’m not sure about the remainder of your issues with it.

It appears that the Gui-related problems were purely my fault. (On android 2.10) Removing focus from the numButtons field by tapping another control within that group does NOT trigger a save. Pressing the Enter/Return key, which I am not accustomed to, makes the form behave predictably.

So with that brushed aside, on to the functional issue…
In the event handler’s getButton(dev, evt, i),
settings.find{it.key == “numButtons$dev”} is always returning null, even when I specify in the form that numButtons > 1

Maybe I’m just crazy, but this doesn’t look restricted to the single-button device functionality…

[keltymd (Matt)]

25 hours and counting with no update from ST. @slagle got anything for us to hang our hats on or to save us from our SOs?

[jovanm (Jovan)]

is there a way to make a rule fire only one time per day (turn on lights when lux < x)?

[bravenel (Bruce)]

@ruricu

Removing focus from the numButtons field by tapping another control within that group does NOT trigger a save. Pressing the Enter/Return key, which I am not accustomed to, makes the form behave predictably.

Yea, another Android glitchy thing. It didn’t use to work at all, so they partially fixed it.

@ruricu

In the event handler’s getButton(dev, evt, i), settings.find{it.key == “numButtons$dev”} is always returning null, even when I specify in the form that numButtons > 1

numButtons$dev is the variable set by choosing the number of buttons (that defaults to 4 if not selected). It’s not null when you specify the number of buttons, only when you don’t. This code works. By “when I specify”, do you mean in Rule Machine or in your device handler?

[sgnihttrams (ocd+adhd+alz+md+asd+fms+tldr+lol=me :))]

@jovanm

is there a way to make a rule fire only one time per day (turn on lights when lux < x)?

Yes. I just asked that in the thread for getting help with how to build rules, and got a great, quick response…

@sgnihttrams

I assume this has been talked about already in this thread, but…

I have lots of Rule Machine rules doing all kinds of things. So, I’m not completely new to it, but I know I’ve probably only scratched the surface of what’s possible.

Without going into much detail about specifics, I’ll just say this…I want to learn how to make something happen, but for it to only happen once within a particular period of time;

e.g Speak ‘good morning’ (I already know how to do that part) as soon as motion is detected in the morning between this time and that time, but only do it once per day.

Again, I assume even this specific thing has probably been talked about, but I can’t find it.
Anybody here know how this works?

@bamarayne

@sgnihttrams

Again, I assume even this specific thing has probably been talked about, but I can’t find it. Anybody here know how this works

Trigger #1 - motion active
Condition - between the times you want, private Boolean true
Action - speak your phrase, set private Boolean to false

Trigger #2 - at a certain time (right before rule #1 is going to fire)
Action - set private Boolean of Rule #1 to true

[bravenel (Bruce)]

Yes there is. You can use private Boolean to do that. It starts out true. So when your rule runs, turn it to false as an action. Then, you want it to be true again for the next day, so you’d have to figure out when to do that. That could be a simple time trigger, that sets it to true again.

[jovanm (Jovan)]

thank you very much!

[ruricu (Chris Eaton)]

@bravenel

numButtons$dev is the variable set by choosing the number of buttons (that defaults to 4 if not selected). It’s not null when you specify the number of buttons, only when you don’t. This code works. By “when I specify”, do you mean in Rule Machine or in your device handler?

With either of these trigger configurations, the latest rule.groovy from the repo, and my device handler not specifying a button number (call this Device Handler 1):
Configuration A
https://dl2.pushbulletusercontent.com/x9AuLRZQXpGHUk75fdzojUztAjUJB1vt/Screenshot_20160316-135203.png
Configuration B
https://dl2.pushbulletusercontent.com/E6QyI8XP7pnllfyXRLnu9271HfrZnwWm/Screenshot_20160316-135351.png

this exception is thrown when “Computer Left” is pushed:

java.lang.NullPointerException: Cannot get property ‘buttonNumber’ on null object @ line 1934

It can be seen that this happens because numButtons, as returned from settings.find{it.key == “numButtons$dev”}, is null, and is being defaulted back to 4

When my device handler specifies buttonNumber=1 (device handler 2):

Configuration A throws:
java.lang.NullPointerException: Cannot get property ‘value’ on null object @ line 1956

Configuration B passes… but this is completely circumventing any change made to support single button devices.

Maybe I misunderstood your intent, but I would expect configurations 1A and 2B to definitely pass… the others would be up to interpretation.

[slagle (Tim Slagle)]

@SBDOBRESCU

Should we kill these zombies and start over?

Until we sort out the current platform issues I can’t really say. But if it’s not working for you right now, a fix would be to remove it temporarily.

[slagle (Tim Slagle)]

@keltymd

25 hours and counting with no update from ST. @slagle got anything for us to hang our hats on or to save us from our SOs?

Still working on it, last i heard we knew what the problem was yesterday.

This is your source of truth: http://smartthings.statuspage.io

[bravenel (Bruce)]

OK, thanks. I’ll look at that code some more. I’ll get back to you.

[SBDOBRESCU (Bobby)]

Yup, thanks Tim, that’s what I did

[bravenel (Bruce)]

[quote=“ruricu, post:3588, topic:28730”]
this exception is thrown when “Computer Left” is pushed:

It’s very hard to attempt to debug this without seeing what you actually have. Either post for me by Private Message your device handler, so I can test with it and see what’s happening, or send me a PM and you could turn on debugging code for me to see what’s going on. The first is the more efficient option.

That exception being thrown for Conf. A suggests that numButtons$dev is null when it should be 1. So I really need to see the application state, the live logging, etc.

[Luvien (LJ)]

@bravenel I’m from QC, Canada. ST is still having a lot of problems from what I see. Wake up mode didn’t fire this morning, lights don’t open or don’t close after delay. This is getting frustrating.

I got 2 minimote to help so my wife can trigger actions manually instead. Bruce, thanks for your Button Controller+, it’s awesome!

LJ

[Squares (Rodrigo Cuadros)]

same here… nothing fired today…

[Kevin_Prefer (Kevin)]

Same here… routine and RM didn’t kick in for certain lights

[fstbusa (Travis)]

RI had a new one happen this morning, rules firing that weren’t supposed to. I’ve had rules that have not fired when they were supposed to but these fired when they were not supposed to. Had some lights that come on to wake up my wife. I have a switch set to disable the rule and that has been enabled the last few days because my wife hasn’t felt well. Didn’t catch it for 25 min after the lights came on… I’m sure she won’t be happy

[GatVlieg]

Based in Cow Town, AB. Rules, some of them, fired OK, up to end of day yesterday. So far none have fired this morning…