New RM bug in 2.1.7.123

[jwetzel1492]

I just upgraded to 2.1.7.123 and now one of my Rule Machine rules is throwing a java.lang.NumberFormatException.

Here's what the rule looks like:

And if I trigger it with the "Run Actions" button in Rule Manager, here are the logs I get:

CC @bravenel

[halfrican.ak]

Getting the same errors on at least one of my rules

[bertabcd1234]

This is unlikely to solve the problem, but you're missing an END-IF and END-REP (in that order as the last two actions in your rule) and causing Rule Machine to be polite and imply them for you. Still, adding them can't hurt.

Also, I know you didn't ask this, but is there a specific need this rule is trying to address? This isn't causing your problem, but looping every minute to see if your motion sensor is inactive is a pretty inefficient way to turn off a light. A "wait for inactive" would be better here, I think.

[bjcowles]

Just realized my coffee hadn't turned off. Ran the rule again, and seeing a similar error.

[bobbles]

I'm getting it too.

[bravenel]

Thanks, will find this pronto!

[bravenel]

Found and fixed. Hot fix coming in a bit...

[bravenel]

Hot fix release is out for this bug.

[jwetzel1492]

Looks like @bravenel has a hotfix for us, which is awesome! I'm going to try your suggestion of waiting for inactive too. I'm still learning all the different ways things can be accomplished in RM.

(Overview of what I'm attempting: I basically want something like Motion Lighting, but it can be triggered by several different things. However, the thing that makes it turn off is still the motion sensor.)

[jwetzel1492]

@bravenel Looks like the hotfix worked on my rule. Thank you sir!

[bravenel]

@Carl

the error is still there but on different line this time!?

Please see the PM I just sent you.

[AdamV]

Looks like this error is still in 2.1.7.24

[bravenel]

Yep, fix coming....