Open IFTTT Webhook from chrome dont work / from android it works

Discussion in 'Join' started by wagi2, Feb 6, 2020.

  1. wagi2

    wagi2 New Member

    Joined:
    Feb 4, 2020
    Messages:
    13
    Likes Received:
    0
    I have a IFTTT webhook "kamera_aus" with works since an long time (calling from Tasker and homeatic). Today I tried zu add an action to teh Chrome zu trigger the webhook.

    Calling the webhook from Join in Android works:

    ifttt android.png

    4 ifttt run from android.PNG

    When I try to send the Webhook from Join Chrome Extension, it dont work (not show up as activity in IFTTT):

    1.PNG

    Sending from Chrome dont work:

    ifttt_chrome.PNG

    Are there any Logs or debuging information? Why does the sending from Chrome not work? Trieding a an Chrome IFTTT action who sends "kamera_aus" (without quotes) dont work, too.
     
  2. wagi2

    wagi2 New Member

    Joined:
    Feb 4, 2020
    Messages:
    13
    Likes Received:
    0
    Admin?
     
  3. wagi2

    wagi2 New Member

    Joined:
    Feb 4, 2020
    Messages:
    13
    Likes Received:
    0
    Any Help?
     
  4. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    8,973
    Likes Received:
    759
    Hi. Sorry for the late reply. Do you see any logs on IFTTT showing the command that was sent?
     
  5. wagi2

    wagi2 New Member

    Joined:
    Feb 4, 2020
    Messages:
    13
    Likes Received:
    0
    No, but I dont know if there are more logs then the acivity view in ifttt. I have created a simple "test" Webhook that sends a email. This webhook can triggered from the Join app but not from the chrome extension.

    100.PNG
     
  6. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    8,973
    Likes Received:
    759
    Hmm, does it work if you create a Join action in Chrome and use IFTTT as your device?
     
  7. wagi2

    wagi2 New Member

    Joined:
    Feb 4, 2020
    Messages:
    13
    Likes Received:
    0
  8. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    8,973
    Likes Received:
    759
    Hmm, I just tried it and it worked for me...
    Maybe try to refresh your devices in Chrome to make sure that you have the right IFTTT device?
     
  9. wagi2

    wagi2 New Member

    Joined:
    Feb 4, 2020
    Messages:
    13
    Likes Received:
    0
    I have enabled devmode in chrome Extension and get this error trying to send to IFTTT
    Access to fetch at 'https://maker.ifttt.com/trigger/<SOME HASH>==/with/key/<KEY WAS HERE>value1=kvpVT%2F%2FmqMeGsJ6dkkT6Ag%3D%3D' from origin 'chrome-extension://flejfacjooompmliegamfbpjjdlhokhj' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

    900.PNG
     
  10. wagi2

    wagi2 New Member

    Joined:
    Feb 4, 2020
    Messages:
    13
    Likes Received:
    0
    And a second thing: If I look at deviceIdsAndDirectDevices.js
    var url = `https://maker.ifttt.com/trigger/${autoAppsCommand.command} [....]

    My command is transfered ENCRYPTED and IFTTT will never understand this stuff!! (i have encryption enabled) therefore the command is nw5523CzUtvM1E5GDcfjYw== and there is a value1 because if encryption is enabled there seems to by a value pair transfered. (xxxxx==yyyyyy)

    This can never be function, if encryption is enabled, because IFTTT cant decrypt this stuff.

    I bet:
    1. you get a CORS error, too, but this affects only the response from ITFFF therefore the command is triggered at your chrome
    2. If you enable encryption, IFTTT dont work for you because the IFTTT Triggerword is transfered encrypted and IFTTT canT handle this.
    Now it's your turn...



     
  11. wagi2

    wagi2 New Member

    Joined:
    Feb 4, 2020
    Messages:
    13
    Likes Received:
    0
    I tried it.
    1. Disabling encryption, restart chrome
    2. send command to ifttt
    a) CORS error occurs; Triiher "test" is send!
    1200.PNG
    b) test is triggered on IFTTT
    1300.PNG

    ==> If encryption enabled, triggering IFTTT from chrome wont work! Why isn't this tested before publishing a tool?
     
  12. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    8,973
    Likes Received:
    759
    Ah yes, that's the issue :)
    About not testing, sorry about that. It's just that these tools have so many possible use cases that sometimes some use cases are not tested.
     
    wagi2 likes this.
  13. wagi2

    wagi2 New Member

    Joined:
    Feb 4, 2020
    Messages:
    13
    Likes Received:
    0
    I h have seen you updated the chrome extension
    Version 1.8.19 18. Februar 2020

    but the IFTTT encryption bug is still there
     
: IFTTT

Share This Page