Siri+iOS Shortcuts+Blynk

Hello there,

I just figured how to make Blynk work with Siri and tought about sharing the idea with this forum as I’ve seen there’s not much talk about it (so it’s either obvious or not that wanted, but oh well). It also allows you to create widgets for quick access as Blynk doesn’t have that feature on iOS.

If you have used IFTTT with Blynk, it’s pretty much the same thing. You’ll need to have the shortcuts app installed. In the Shortcuts app, create a new shortcut and name it however you like (you can change it anytime). Note that when using Siri to access the shortcuts you’ll need to use the name you chose. In the shortcut you created, select Add action->Web->Web requests->Get contents of URL. It should look like this:

You need to make a web request, so the next thing would be finding the adress, by running the command “ping” in Winndows console. This should return an adress. Copy that adress and paste it in the “URL” tab of the action you just added in your shortcut, followed by the auth token of the Blynk project you’re using it on, a /update/, the pin you’d like to use and its desired state. It should look simillar to this:

Also, in the Show More->Method tab “GET” should be selected.

Note that for digital pins D5 doesn’t correspond to the number written on the board, but with the GPIO pin number. So in mu case D5=GPIO5=D1(on nodemcu). You should now be able to run the command with Siri and also create a widget button by ticking “Show in widget” in the shortcut settings.

Try experimenting with it, there are a few things you can do without having to actually code.

Hope this will be helpfull to some of you. Any suggestions or ideas are kindly welcome


That’s very good.

If you’re using local Blynk server using SSL/TLS with a valid SSL/TLS certificate, and have DDNS service to access from Internet, and your DDNS address is, you can use this Web GET command


Then just call Siri to do the job.

If your SSL/TLS certificate is invalid, Siri will complain, saying something like

Hmm, something went wrong. Shorcuts says, "The certificate for this server is invalid. You might be connecting to a server that is pretending to be "" which could put your confidential information at risk"
1 Like

This works great!

I have a question though… If I do the

but with a virtual pin …/V1?value=1

It triggers my wemos the way I expect, except V1 now stays as 1, unless I do another get with


What I’ve done is build my shortcut to do two gets, first with a 1 then with a 0. To simulate a momentary pushbutton.

Is there a way I can use the wemos to change the virtual pin back to 0? Then I would only need one get in my shortcut…

Thanks in advance!

1 Like

I just finally managed to follow your instruction and I WORKS!
Thank you so much for this explaination!

1 Like

Fantastic, thnx for your very easy to follow instructions this worked perfectly first time! I have Blynk connected devices all around the hose that are very soon to become Siri enabled . . . :wink:


1 Like

I signed up for an account so I could favorite this. I didn’t realize this was possible and it works so well. THANK YOU!

1 Like

I have been using this method for a while now to control two esp8266 over my iPhone 11 with the newest iOS.

But now when I came back home After 3 weeks and tried to switch on the light, it did not work anymore and it has not since then.

The Shortcut is set up exactly how it was when it was working, my only idea is that the connection to the Blynk Server could have changed.

Maybe you are dealing with the same problem or have an idea?

@lil_satan I’m not sure if there’s any workaround. I’m using the same method to simulate a push button.

@Marco7 I’m not having this problem. Do the command work in the Blynk app?


First time writing. I started playing with the same idea of simulating a push button.

The first thing I did in the Arduino IDE was to set the the push button to run for three seconds. This functioned flawlessly with Blynk.

The second thing, which is the above mentioned question, related to shortcuts. I followed the instructions here using update/V21?value=1 but the virtual button stayed on (blocked?) after the url command. I solved this by adding a second action within the original shortcut and changed the end of the url to update/V21?value=0.

This allowed the virtual button to function as it was intended. So far so good.