Rule suddenly failed

No idea what's happening here but it's the second time it's happened so I thought I'd post a question. I have a rule that keeps my temp above 54 degrees in my shed. Generally it's been working well. Pretty sure my screenshot will work below, if not I'll add it separately.

This morning I looked and the temp in the shed was 69 degrees and the heater was on. Looking at the log it seems the rule didn't trigger the heater to turn off. I've pasted a longer section of the log below, but you can tell where it turns on and where it goes false,

Thoughts?

Can you post your temp sensor's log, it looks like either the sensor wasn't sending events, or the rule wasn't seeing the events. You can also look for temperature events on the sensor device page.

I can but I have to pull the power on my hub. It's locked up again. If you want I can post it, but it's actually on the screen shot of the log details. The first (bottom) one highlighted is the temp sensor reading of 53.9 which triggers the rule. About 13 lines down from the top of the highlighted section there's the temperature sensor reading of 55.1 and the rule triggers to False. The problem is that there is no command to set the switch to off.

ahh, missed that. now I am out of ideas. I would expect to see Heater switch is off as well. You'll need someone more knowledgeable than me...

yeah, bummer. Since I have the log, here's a shot of it working fine.

And the one that didn't work...

It started going back down because I saw it and turned off the heater via the dashboard.

Just chiming in to say I have noticed a few times where rules fail to run/trigger for unknown reasons in the last few weeks. Itā€™s very rare for me and I havenā€™t been able to force-reproduce the behavior. Similar symptoms to what you describe.

Thanks for the reply. Still, that's a pretty catastrophic fail if it were a different device. Other than costing me money it's doable, but should we be using time based triggers instead? At least it would get re-evaluated.

Iā€™ve seen this too. Rules not running. Iā€™m just not sure if itā€™s do to how I built my rules based off triggers. More time will tell...

Yeah, I think a time based trigger would at least recheck the condition again. In my case it will never turn off unless I put something in that makes it do that.

Wondering if there's a platform that doesn't have this problem.

Looking at this a bit more, I'm wondering if my Fibaro Wall Plug is the issue. I Think my other devices are working (More or less) but this one seems tricky. I'm using the Fibaro Wall Plug driver from Hubitat but wondering if I should be using a generic driver instead.

Thoughts? If I go generic will the USB plug still work?

OK, more troubleshooting, and the Fibaro Wall Plug definitely doesn't work correctly anymore (at least consistently).

Any thoughts on swapping it to a generic driver? Tried outlet and it didn't work well either. Other options? Kinda bummed to spend 60 dollars for a supported device that's not working, but I'd rather have something that works.