The data is completely optional, and you can also pass value1, value2, and value3 as query parameters or form variables. This content will be passed on to the Action in your Recipe.
I dream of the day Vera finally links natively with IFTTT, as do many others I’m sure. The joke used to be that Google kept its beta programs languishing forever… now, they are getting some competition in that department.
ElCid I am seeing that it is possible to perform this integration with ifttt. Only now I ask you this question, if I want that when my phone’s wifi is detected by my local network, my vera will go to Home mode. How can I perform this action with this application?
No need for IFTTT, you can use the app WOLplusping as a scene trigger to set the home mode. You would need to set up a IP reservation on your router to assign a static IP to the phone.
you could use automate on your phone to send a local http request to vera when phone connects to wifi. This request would start the the home mode addon ie. http://***.***.**.***:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=24.
No need to have static ip. When i leave home my phone sends cloud message to local android running automate, then the local automate sends local request to turn on away mode. When i return home and my phone connects to local network it sends request to turn on home mode.
Hello EICid, I try to setup this webhook between automate and ifttt but I am not succeed.
Can you please give me your flows and a more details steps how to set this up.
Thanks.
After some struggles I succeed to send a webhook message via ifttt to automate. I have used the site example webform request in the ifttt webhook.
However I don’t understand what this “catch failure” part does in this totaal flow example. But it works.
The next step will be to send a http request to my vera system, can you give an example how to proceed with this challenge. Thanks.
The payload would be “vera_on 23 1”
this will turn device 23 to on
or
“vera_dim 23 75|vera_on 24 0”
this will turn device 24 off and set dimming level of device 23 to 75%
You could add a fork to make the cloud message recieve respond to multiple requests, as without fork, cloud block will not be waiting till all http requests are made. As example image below
I succeeded to get the flow working now. I also added the fork as in the example.
First it was also working with the static http message in automate. But with the last remark I understand now that the flow is dynamically, depending of the webhook payload. So the flow can stay the same.
I want to use this now to send the status of 3 sensors in ifttt to a vera virtual sensor. So I have to create 6 webhooks, one for switch on and one for switch off, in ifttt to transfer this status. Or is there an easier way to do this? Thanks for your support.
Yes you would probably have to create 6. Unless the ifttt sensors can trigger on toggle and report state, then you may get away with 3. In developer section of ifttt, there is the ability to make more complicated applets https://platform.ifttt.com .
I know this is an old topic, and from what I can tell Vera IFTTT is still in Beta, or completely dead. Either way, I was following the steps above and created a trigger within my Vera and IFTTT and then finally got to the part about creating a Webhook. I ultimately created my Webhook as an IF and then my THAT to be what I want to control outside of my Vera hub. This works perfectly and I didn’t need steps 1-4. I can use the LUA wget to run the webhook trigger. However I got to thinking if this was a security issue or not. Or am I over thinking this and I really only needed steps 5-10 to get everything running right?