Okay, got the email that IFTTT support is going away. I have some Particle Photons that I trigger using IFTTT schedule recipes. Basically a simple “turn this on at this time” and “turn this off at this time” kind of stuff. I’m guessing that’s no longer going to work? Basically I got into this ecosystem using NCD.io devel boards and their firmware. I extended that stuff so that I use Particle Cloud for some local communication between Photons, but nothing using IFTTT, just straight Particle Cloud.
So assuming I need to do something different from IFTTT, can someone point me to something with similar recipe funcationality and docs for making it work with Particle?
There are a few approaches you can use. First, you can continue to use IFTTT but with webhooks instead of a standard integration. Here’s the IFTTT Migration Documentation where you can learn how to update your applets to the webhook integration.
Thanks. I had already looked at the docs, but it seemed mostly geared toward communication the other direction. I can look closer, I suppose, but was hoping for something a little more tightly geared toward what I’m doing.
As for coding directly, yes, I could. But keeping track of time accurately is a kind of annoying on devices like that, or at least that’s been my experience. I also use IFTTT button widgets to override the timers and control things manually on occasion. It’s actually always worked fairly well for me, so it’s a bit of a bummer to have to go changing things. Yes, I’ve seen IFTTT lags by a minute or two sometimes, but that’s been the extent of it.
Oh man, I just realized the other problem with this: loss of name indirection.
With the previous setup, if a Photon went bad, I simply had to flash a new one, remove the old one from my Devices, and name the new one the same as the old one. No need to update the IFTTT recipes. Now I’ll have to go update every recipe that talks to that device.
I am appreciative of the documentation. That error just broke my brain into thinking I needed two different things in that line, not just arg: argument, though in retrospect it should have been obvious. But at least I found an error for you that should help clear things up a little for the next person.
Any chance we can get a way to make these calls by device name instead of by DeviceID? If we could get that back then everything still works as it did, even if it’s a tad more convoluted to setup. And that indirection was super-useful.
Hi, not sure if to start another thread or comment here, apologies if incorrect. I’m in same position, I used ifttt to call a particle function, called ‘lamp’ with the input ‘toggle’. Worked great from old integration. Now the move to webhook.
I’ve copied above, I get an event fired in ifttt with all signs it worked with the device and bearer field/token, no function on photon is called though
I’ve got {“arg”:“toggle”} in the applet Body field
Thanks, that worked, however another issue. I’ve gone through the thread of this post and here… IFTTT | Getting Started | Particle on how to Call a function, but not too sure why I’m getting this error (see attached photo)
Na, still failing. So to be clear, the action I want to send to my 4-channel relay Particle board is “3on” which I have at the end of the url field i.e. https://api.particle.io/v1/devices/<redacted>/3on
and also have it in the Body field as seen in previous screenshot. I have also tried the {“arg”:“”} which also failed a 404 error.
