I’m not using SmartThings to trigger IFTTT, I’m using Android Location and Android Device channels in IFTTT as the “if this” to set virtual switches in ST as the “then this”.
Maybe it would help if I explain my setup more in depth. I’m going to focus just on my presence, but I have a duplicate of everything below set up for my wife as well.
To add some redundancy to help work around the intermittent mobile presence issues that I have seen using my phone as a presence sensor in SmartThings, and to make it easier to delete and re-add my phone if it stops reporting (which has happened twice in the 4 months I’ve had my hub), I created a virtual presence sensor (named Chris) to use as a trigger for my various routines, pistons, and push notifications. I am using the CoRE piston below to set the status of this virtual presence sensor. Two reasons for this: first, I can use several different inputs to set the status of this virtual presence sensor instead of just relying on ST phone presence only, and second, when I have to delete and re-add my phone as a presence sensor, I just have to remove and re-add it one place instead of 5+.
So…here’s the piston:
Phone presence is self-explanatory.
For the Chris Presence IFTTT switch, I have two recipes in IFTTT that use Android Location channel to turn this switch on and off in ST, one for entering my home area, one for exiting.
For the Chris WiFi IFTTT switch, I have two recipes in IFTTT that use Android Device channel to turn this switch on and off in ST, one for when I connect to my home wifi network, and one for when I disconnect from my home wifi network.
The issue that I’m seeing is that the IFTTT recipes for Android Location and Android Device are not running correctly. When they do run, they turn the corresponding switches on and off almost immediately in SmartThings, so the connection between IFTTT and ST is fine. The problem is within IFTTT itself and the fact that the recipes don’t run or are severely delayed based on the IF portions of IFTTT’s own internal channels.