
Run a POST webhook?

I currently use IFTTT to activate scripts, scenes etc. in https://home-assistant.io via webhooks (activated via Google Home and Alexa), and I'm wondering if it would be possible to create some buttons (recipes) in NEEO to do the same?
The image attached shows an example of a typical webhook I use in IFTTT.
Would this be possible with NEEO? If so how? (Or alternatively just activate an existing IFTTT recipe from the NEEO)
-
Would be pretty easy to do - just look at the SDK examples - especially the ones creating a custom button. You'll see a button callback that can execute any code you want (which includes sending off IFTTT triggers). The other option is to use one of the bigger packages like openHAB or Homey which both have full integration with IFTTT and can work with NEEO through the plugins that Niels de Klerk (homey) or I (openHAB) have created.
-
With my API guide you should be able to do all the basic stuff like start a recipe, press a button etc etc...
https://planet.neeo.com/t/x1trmk/api-examples-to-get-started
Have fun!
-
Thanks.
Am I right in thinking I'd have to create a driver with the code on (for example) a Raspberry Pi, and then keep it running on the Raspberry Pi in order to import it and keep running it on the NEEO?
And the code would be something like this, is that correct?
PUT https://MYURL.duckdns.org/api/services/scene/turn_on?api_password=MYPASSWORD content: {"entity_id":"scene.bedtime"}
-
Yeah, I'm still wanting to know how to do this.
I guess if IFTTT integration was implemented as was stated in the original Kickstarter then things like this would be 'easy'.
But at the moment I still don't understand how to do it. I don't know how to write a driver to do it (or particularly want to know how to write a driver).I'm just wanting to send instructions from the NEEO to Home Assistant (home automation) to start scenes, run scripts etc. and just keep going round in circles 🤔
-
@all tahnks for your hints. I am totaly with you but for me that are workarounds. This webhook thing is a standard for a smart device for me.
And this SDK "workaround" works if you have 1-2 buttons you want to use. But if you have to touch code for every button and deploy the stuff and keep it running this it no way to handle it sorry. And at the end I have a smarthome to simplify things, inspecial neeo which combines many standards, and not to run a neeo, a Pi a cloud application and so on.