Simple automation rule generates NullPointerException errors

🛎️ Get Help Apps
1

I run a set of rules that I've haven't touched in several years. My hub has been running 2.2.6.137 for a long time. Starting about a week ago, one of my simple automation rules failed, generating NullPointException errors. I did some searching and saw that others had reported this within the last few years and there were comments that a bug was found and had been fixed. So it occurred to me that I really should update the hub, maybe it would fix the problem. Today I updated to 2.3.8.118, which was seamless... all my existing rules seemed to work fine. However, I still get this NPE error.

The error occurs when the code tries to turn off a Zigbee power outlet a few minutes after sunset. I can turn the outlet on/off manually without a problem so I don't think this is a Zigbee issue etc.

Attached are screen shots of the log file and the rule itself. Any help greatly appreciated.

log_error
log_error1459×43 11.3 KB

simple_rule
simple_rule1497×684 48.1 KB

2

In case there’s something corrupted about the rule, have you tried recreating it from scratch? That would be pretty simple to try.

3

I didn't try that because this is a cookie cutter rule. You just click the boxes in the template and fill in the delay values you want. I could try it of course, but this code has been working fine for years.

4

Anything can get corrupted on a power loss to the hub.

1 Like
5

OK I will try to recreate the rule. But my hub is on a UPS, never loses power.