[2.2.4.153] Simple Automation Rules null pointer

🛎️ Get Help
1

I'm seeing a null pointer with Simple Automation Rules 1.1. I've recently re-created my rules for 1.1, so I don't know if this is new to 2.2.4.153 or not.

[error] java.lang.NullPointerException: Cannot invoke method multiply() on null object on line 777 (beforeSunriseHandler)

Screen Shot 2020-12-02 at 08.53.00
Screen Shot 2020-12-02 at 08.53.001826×337 16 KB

2

Do you get this when it should fire? Or when creating/editing the rule?

I made a duplicate of your rule with no errors. But obviously it won't fire next until sunset+10.

1 Like
3

The error was logged at sunrise (not sunrise -15). According to the device event log, the device turned off at sunrise -15.

4

Cool. I'll keep my eyes open on my rule! Not that it helps you either way, but it will be another data point in any case.

5

I need to see those logs. Can you post a screenshot.

6

As above.

Screen Shot 2020-12-02 at 09.55.57
Screen Shot 2020-12-02 at 09.55.572051×41 17.1 KB

7

Please show the Settings portion of the App Status page (gear icon). You could only get that error if the rule ran without a sunrise offset having been set, but you have a sunrise offset defined.

8

Screen Shot 2020-12-02 at 11.23.37
Screen Shot 2020-12-02 at 11.23.372122×1011 120 KB

9

Ah, I see the problem. Will look into fixing that. Thanks.

1 Like
10

Thank you Bruce.

11

Never mind. Able to reproduce.

Found and fixed for next release.

1 Like
12

Fro the record, I got the same error this morning (hub=2.2.4.155). I updated that dev hub to 156 so we'll see what it does tomorrow.

app:792020-12-03 07:15:00.430 am errorjava.lang.NullPointerException: Cannot invoke method multiply() on null object on line 778 (beforeSunriseHandler)

13

This bug was fixed. Assuming you're talking about a Before Sunrise offset on the second action (anti-action).

14

Yup. Ok, We'll see tomorrow morning then! Definitely wasn't fixed in 155.

15

Yeah, fix was merged yesterday, so it made it into 156, not 155.

2 Likes
16

Thanks Bruce!

17

Actually, part of the problem was that Simple Automation Rule had its guts redone, but got virtually no testing during beta. We failed to push enough people to start using it. So there were corners here and there never used, including this one. I think we got them all now, but.... it's software!

3 Likes
18

I’m in a public safety electrical shutdown area, so I won’t be able to test until the day after tomorrow.

19

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.