Was in touch with Josh and he suggested I post here. Discovered that my inexpensive wifi to IR blaster is compatible with SmartLife app which is also compatible with IFTTT and Alexa.
IFTTT can trigger the wifi to IR blaster to fire IR codes via SmartLife scenes (macros) with a simple webhook trigger. The SmartLife app natively controls the IR blaster via virtual remotes. Id rather not have to take out my phone each time. So I figured, if I could create a tile in SharpTools which triggers the IFTTT webhook, I could fire IR codes from the wifi to IR blaster without the need to first set up a virtual switch in Smartthings then link that switch to IFTTT (Smartthings is also compatible with IFTTT). In other words I want to tap a tile on my dashboard and bypass Smartthings, which would save setup time and send the IR code faster. I could control any IR based device this way directly from a SharpTools dashboard and the blaster. (TVs, AC, Fans, etc).
So…Josh suggested using the $.get (webhook URL) syntax with a hyperlink tile, which worked.
Problem is with IFTTT a glaring red error message appears after the tile is taped as a server response. Josh explained it’s due to an incompatibility between Sharptools servers and IFTTT. He said the Sharptools server could be modified to handle the request so it works without the error message if there’s enough of a demand. Perhaps even a dedicated IFTTT webhook tile option (since the service is so popular now) could be added or a simple option in the existing hyperlink tile to turn off the server response message, etc.
IFTTT webhooks would open up a world of possibiltes to control devices via Sharptools that aren’t directly compatible with smartthings.
I know this can be addressed by injecting CSS with fully kiosk. I don’t use fully kiosk and that’s more complicated than it needs to be. So a simple option or dedicated tile would be fantastic.
Would there be any community interest to expedite this feature?
Yes a proper webhook integration, official IFTTT integration, or just a simple option to turn off the response message from the server for the current hyperlink tile would do the trick- neat and clean!
IFTTT is like a Smartthings hub in the cloud, compliments and enhances everyone’s existing setup and devices.
The problem is modern browsers will block requests made across two different origins (domains) if the API that is being called doesn’t return a CORS header. In this case, IFTTT’s webhook API is not returning any CORS headers at all which is causing the issue.
What we are proposing is adding an option to the Hyperlink tile REST API syntax which would route the request through our servers to workaround the CORS issue. (Again, the requests currently go directly from your browser to IFTTT)