I’ve been using IFTTT to “integrate” Sense devices into my Hubitat home automation hub. Basically, what I can do, is create a virtual switch, like for the washer, and when Sense sees the washer turn on, I turn on the virtual switch. When Sence sees the washer turn off, it turns off the virtual switch. If the virtual switch has been off for 10 minutes, I send a notification to mine and my wife’s phones saying the washer has finished. I do the same with the dryer and dishwasher. I’ve got another one that turns off the air purifier if the TV turns on (both of these devices are connected to an HS300). I have a few more but I think you get the idea of what I’m using this integration for.
However, I noticed that starting probably about 2 or 3 weeks ago (maybe longer ago, but this is when I noticed) that the Air Purifier was not turning off when I turned the TV on. It was normally taking about 20 seconds to run (from the time that Sense saw the TV come on to the time that the purifier turned off) which I was completely fine with. I’m not expecting real time. So I started trying to figure out what was going on. I eventually figured out that all my rules in IFTTT for Sense say “This Applet usually runs within an hour” and formally I believe it said within a minute.
Here are a couple of screenshots from the activity log. This morning I turned the TV on at 7:15am but the rule didn’t trigger until 7:27am. So a delay of 12 minutes.
Here, the TV turned on at 8:02pm but the rule didn’t trigger until 8:27pm. So a delay of 25 minutes.
According to this IFTTT knowledge base article, “The frequency in which Applets run is largely dependent on the service(s) you’re using. If an Applet isn’t running as quickly as you expect it, we encourage you to check with the service owner. Most service owners have tools available to them to help them figure out if their IFTTT integration can run a bit faster.”