I am able to see/control/update a Digital Pin on my NodeMCU from a web browser. But when I try to make the same request from IFTTT makers channer I get an error “Action skipped” or “Maker Action error”. It´s not like it´s just with blynk server. I get the same error when I make a request to go to google.com. Can anyone explain why is this happening. Anyway I can put the URL
I don’t know if this helps you at all in terms of setting up your recipe in IFTTT, but this an example of my setup for Blynk/IFTTT. I share this because getting the syntax right took me some trial and error:
I tried last whole week to get work Blynk with IFTTT but no luck. I tried both put and get methods with browser,postman and maker channel.I always get invalid token message,how can i solve this?
I tried IFTTT with the domain name and IFTTT compalins that it got 400 as response and after using the IP it works. Though with postman I can use domain name as well.
This is because Blynk uses a number of different cloud servers around the world, to get good response times.
Your project and it’s associated Auth code are only stored on one of those servers, and this will be the one that’s nearest to you when you create the project (I think it’s actually a bit more complex than that, but go with this as the explanation for now).
When you use postman on your local PC, and specify blynk-cloud.com it hits the correct Blynk cloud server, so it works.
Assume that the ITTTT servers are on the other side of the world from you, and when they send a command to blynk-cloud.com they hit a different server to the one that your postman command hits. The blynk-cloud.com server that the IFTTT server hits doesn’t have your project on it, so you get an error.
The solution is for you to open a command window on your PC and type ping blynk-cloud.com
The IP address that’s returned is the IP of the Blynk server where your project lives. I you put this IP in your IFTTT recipe, rather than using blynk-cloud.com then IFTTT will be able to hit the correct Blynk server and will work correctly (assuming that the rest of your IFTTT recipe is correct of course).