Delay per mode recently broken?

📐 Rule Machine®
1

I just upgraded my C-5 to 2.3.9.174 and a "delay per mode" action in a RM Legacy rule that I haven't touched for years started throwing:

java.lang.NumberFormatException: For input string: "null" on line 7041 (method appButtonHandler)

I tried deleting and recreating the action and the same error occurred. The result is that no delay is getting scheduled (so, in my rule below, the lights never turn off). It works if I replace it with a regular (not per-mode) delay.

1000001489
10000014891080×2400 283 KB

1000001488
10000014881080×2400 346 KB

2

@bravenel

3

Please redo this rule in Rule 5.1.

4

I started to, but realized I'd need to migrate at least 7 rules that touch the Rampup variable directly (and probably more indirectly). I can get something to work, even if it means ditching some functionality in my rules until I have time.

I mentioned this because I didn't expect RM Legacy to have regressions (even if it doesn't get new features).

5

I'm looking into this. RM Legacy has not been changed in a few years, so it's an odd situation.

1 Like
6

From what I can tell, this bug has been there for at least 3 years. Fix will be coming in Release 2.4.0....

1 Like
7

Awesome, thank you! I guess I was lucky that it didn't seem to break my rule until recently.

1 Like