No announcement yet.

ifttt latency

  • Filter
  • Time
  • Show
Clear All
new posts

    ifttt latency

    Hello Folks
    I am just setting up my system, I had a few false starts. I am trying to get Link Shades ( to work with Homeseer. I have a virtual button in Homeseer (ON/OFF) and I want to use that to control the shades. To do this I am using IFTTT. The Applet is basic, "IF a device is turn OFF, Open the shades." When I check the applet, nothing happens, I tried checking the applet with the Virtual button ON and OFF.

    I get a message "This Applet usually runs within a few hours" ; that's not automation!
    I do have a MS.homeseer account set up as well, not sure how that fits into the equation.

    Any suggestion on what I am doing wrong.

    How does Homesser know to send a message to the IFTTT server when the virtual button is pressed?
    How can I test the two communication channels. One between Homeseer and IFTTT, then the second between IFTTT and Link Shade.


    IFTTT is known to be slow, but I thought the delay was minutes and not hours.

    Most of these WiFi devices use an ESP8366. For the DIYer the firmware is reflashed with something like Tasmota. This provides non-cloud control, Wemo/Hue emulation for voice control and HTTP or MQTT for integration with HS or other preferred system. Very little info on the web site so can’t provide much more guidance.


      Thanks, a bit too deep into the bits and bytes for me right now.

      I think IFTTT can work, I just have something set up wrong . I have proved to myself the issues is the connection / link between Homeseer and IFTTT. I proved this by generating another Applet on the IFTTT site. This test Applet is : "IF the TIME is 11:30, Open the shades." This works within a few seconds of 11:30.

      So does anyone have guidance about the connection between Homeseer and IFTTT. Now I am down to one question
      How does Homesser know to send a message to the IFTTT server when the virtual button is pressed? Does this have to be configured somewhere?


        You need to create a Trigger in IFTTT that is linked to your HomeSeer virtual device.
        IFTTT typically responds within a few seconds.


          I have a trigger in IFTTT that is linked to Homeseer.


            The IFTTT is pointing to the Homeseer servers as the problem, see photo 1. It's not a latency issues, it simply does not work. In the Homeseer log I see when the virtual button is pressed, either on the hub or remotely via MyHs

            I created another APPLET : " Get e-mail when Homeseer publishes a new event or trigger". It does not work either.

            Did anyone else experienced this problem.


              same problem here... HS connection to IFTTT is very slow or not working at all.


                I have given up on IFTTT. I have a Skybell doorbell and wanted to get notifications through HS. When it made it through it took several minutes. Completely useless for a doorbell. IFTTT is blaming Skybell and Skybell is blaming IFTTT. I ended up using an Arduino board that monitors the electrical signal and then notifies HomeSeer. I had similar issues with other IFTTT applets. I have a feeling that if a company like HS/Skybell/etc pay money to IFTTT then they prioritize messages but that's just a guess...


                  Yup - getting exactly the same here and IT IS 100% Homeseer servers/connection to IFTTT. How?

                  Every other IFTTT connection to many others 3rd party devices work within seconds, if not immediately. HS can take minutes or hours or fail
                  Setting up a HS event that triggers when a device is turned on/off BUT then fires a Webhooks command instead to IFTTT works instantly
                  Setting up an IFTTT Webhook to HomeSeer works instantly
                  Relying upon the IFTTT Homeseer integration without Webhooks takes forever, very rarely will it trigger instantly.

                  I deduce as there are no other integrations that take this long, and neither do HomeSeer/Webhooks take this long the one unique part the makes this slow is the HomeSeer/IFTTT configuration within HomeSeer servers, whereever they may be. It's probably been given a lower CPU priority and everyone's commands just get queued up.