Trigger *increased* still broken?

šŸ“ Rule MachineĀ®
1

@bravenel, is the increased trigger fixed for all cases? I had a simple rule that broke when this issue arose a while back, and I worked around by changing the trigger to changed, saving prior value, then having an IF ā€¦ THEN test of the new value with the prior, saved, value around the single action that turned on an auto-off virtual switch.

When the recent update reported that this was fixed, I went back to the original rule, and itā€™s broken (in a different way). Previously, it didnā€™t trigger, now it is triggering, but with an NPE error.

C-8 on 2.3.7.139.

Here is a screenshot of the Rule and logs (all logging turned on).

IMG_0201
IMG_02011668Ɨ2224 281 KB

IMG_0200
IMG_02001668Ɨ2224 604 KB

EDIT: Updated to 2.3.7.140, same NPE results. Here are the logs after update to 2.3.7.140:

IMG_0202
IMG_02021668Ɨ692 212 KB

2

Well, that's not good. I'll look into it.

I was able to reproduce this, and I think I have a fix for the next hot fix release.

8 Likes
4

What is the actual device for the trigger? Is that a Custom Attribute?

Itā€™s an entity that monitors the poop level in a Litter Robot 3, brought over from Home Assistant by HADB:

IMG_0203
IMG_02031668Ɨ2224 232 KB

Previously, it was a Custom Attribute in the user-contributed Litter Robot integration on Hubitat, but Litter Robot changed their API, which broke the Hubitat integration.

5

Updated to 2.3.7.141, tested again, can now report that this issue has been fixed. Thanks.

2 Likes
6

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