OK, I just wanted to close the loop on this one. As @PeteKnight suggested, I decided to keep testing to try to figure out what was going on… Just because I like to get to the bottom of things (even if there are alternative solutions)…
My conclusion is that IFTTT was having a glitch that day causing this strange behavior. I am saying this because, in addition to this issue, I wasn’t able to access the “New Applet” option from their webpage, the only way for me to do it was through the app… It was kind of odd, but it was also my first time doing it, so I just thought it was the only way…
Well, the good news is that I learned a lot and probably what I learned is useful for someone else, so here we go:
- There is a Blynk API documentation site where you can actually test the different methods (PUT, GET, POST, etc) and see the request sent to the Blynk server and the response received - Here it is: Blynk HTTP RESTful API. The requests can be sent either through apiary or through your local browser installing an extension. - I did different tests to set the PIN to what I wanted and they all worked flawlessly.
- The server IP is no longer required and the blynk-cloud.com server can be used directly on the request. Please see this post for more information. - I also tested this several times (IP and DNS name).
- The network port is also not required (at least for cloud servers) - I did my test with and without port and both worked (tested from IFTTT).
In summary, I think I will use GET for my purpose as I think it’s cleaner, but PUT works as well without any issue.
I hope someone finds this useful…
Best!