Announcement

Collapse
No announcement yet.

One hour delay ...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • One hour delay ...

    On the newly configured IFTTT website, my Homeseer "Applets" now have a message displayed beside them - "This Applet can be delayed by up to an hour", and for the past 24 hours my notifications on Homeseer devices turning on/off are indeed delayed considerably, often around the one hour mark.

    I don't see this "delay" message on "Applets" which do not use the Homeseer Channel.

    Can anyone shed light on this for me pls?

  • #2
    Nothing specific, but I see the exact same issues. I am experimenting with the IFTTT plug in right now as a substitute. Never have been able to get timely updates with Homeseer for IFTTT.

    Comment


    • #3
      I see the same delay notice with other Applets such as Dash. I run a recurring trigger on IFTTT and log it on HS. It's actually getting better over the last few weeks. It's supposed to trigger right on the hour and it logs the delta between when it's supposed to trigger and when it actually does. When I first put it in place, it was typically triggered about 2-3 minutes after it was supposed to. I also run a similar log with HS as the trigger and it always triggers exactly when it is supposed to. Here's the recent log from the IFTTT trigger:

      Code:
      Nov-25 12:00:05 PM	 	IFTTT Heartbeat	5 seconds
      Nov-25 11:00:21 AM	 	IFTTT Heartbeat	21 seconds
      Nov-25 10:00:11 AM	 	IFTTT Heartbeat	11 seconds
      Nov-25 9:00:24 AM	 	IFTTT Heartbeat	24 seconds
      Nov-25 8:00:15 AM	 	IFTTT Heartbeat	15 seconds
      Nov-25 7:00:39 AM	 	IFTTT Heartbeat	39 seconds
      Nov-25 6:01:11 AM	 	IFTTT Heartbeat	71 seconds
      Nov-25 5:00:19 AM	 	IFTTT Heartbeat	19 seconds
      Nov-25 4:00:16 AM	 	IFTTT Heartbeat	16 seconds
      Nov-25 3:00:25 AM	 	IFTTT Heartbeat	25 seconds
      Nov-25 2:00:06 AM	 	IFTTT Heartbeat	6 seconds
      Nov-25 1:00:36 AM	 	IFTTT Heartbeat	36 seconds
      Nov-25 12:00:15 AM	 	IFTTT Heartbeat	15 seconds
      Nov-24 11:00:08 PM	 	IFTTT Heartbeat	8 seconds
      Nov-24 10:00:34 PM	 	IFTTT Heartbeat	34 seconds
      Nov-24 9:00:13 PM	 	IFTTT Heartbeat	13 seconds
      Nov-24 8:00:11 PM	 	IFTTT Heartbeat	11 seconds
      Nov-24 7:00:16 PM	 	IFTTT Heartbeat	16 seconds
      Nov-24 6:00:41 PM	 	IFTTT Heartbeat	41 seconds
      Nov-24 5:00:19 PM	 	IFTTT Heartbeat	19 seconds
      Nov-24 4:00:41 PM	 	IFTTT Heartbeat	41 seconds
      Nov-24 3:00:10 PM	 	IFTTT Heartbeat	10 seconds
      Nov-24 2:00:08 PM	 	IFTTT Heartbeat	8 seconds
      Nov-24 1:00:14 PM	 	IFTTT Heartbeat	14 seconds
      Nov-24 12:00:20 PM	 	IFTTT Heartbeat	20 seconds
      Nov-24 11:00:12 AM	 	IFTTT Heartbeat	12 seconds
      Nov-24 10:00:26 AM	 	IFTTT Heartbeat	26 seconds
      Nov-24 9:00:25 AM	 	IFTTT Heartbeat	25 seconds
      Nov-24 8:00:44 AM	 	IFTTT Heartbeat	44 seconds
      Nov-24 7:00:27 AM	 	IFTTT Heartbeat	27 seconds
      Nov-24 6:00:04 AM	 	IFTTT Heartbeat	4 seconds
      Nov-24 5:00:24 AM	 	IFTTT Heartbeat	24 seconds
      Nov-24 4:00:11 AM	 	IFTTT Heartbeat	11 seconds
      Nov-24 3:00:23 AM	 	IFTTT Heartbeat	23 seconds
      Nov-24 2:00:25 AM	 	IFTTT Heartbeat	25 seconds
      Nov-24 1:00:12 AM	 	IFTTT Heartbeat	12 seconds
      Nov-24 12:00:37 AM	 	IFTTT Heartbeat	37 seconds
      Nov-23 11:00:38 PM	 	IFTTT Heartbeat	38 seconds
      Nov-23 10:00:22 PM	 	IFTTT Heartbeat	22 seconds
      Nov-23 9:00:13 PM	 	IFTTT Heartbeat	13 seconds
      Nov-23 8:00:06 PM	 	IFTTT Heartbeat	6 seconds
      Nov-23 7:00:07 PM	 	IFTTT Heartbeat	7 seconds
      Nov-23 6:00:21 PM	 	IFTTT Heartbeat	21 seconds
      Nov-23 5:00:22 PM	 	IFTTT Heartbeat	22 seconds
      Nov-23 4:00:26 PM	 	IFTTT Heartbeat	26 seconds
      Nov-23 3:00:30 PM	 	IFTTT Heartbeat	30 seconds
      Nov-23 2:00:13 PM	 	IFTTT Heartbeat	13 seconds
      Nov-23 1:00:14 PM	 	IFTTT Heartbeat	14 seconds
      Nov-23 12:00:13 PM	 	IFTTT Heartbeat	13 seconds
      Nov-23 11:00:07 AM	 	IFTTT Heartbeat	7 seconds
      Nov-23 10:00:56 AM	 	IFTTT Heartbeat	56 seconds
      Nov-23 9:00:15 AM	 	IFTTT Heartbeat	15 seconds
      Nov-23 8:00:17 AM	 	IFTTT Heartbeat	17 seconds
      Nov-23 7:00:23 AM	 	IFTTT Heartbeat	23 seconds
      Nov-23 6:00:32 AM	 	IFTTT Heartbeat	32 seconds
      Nov-23 5:00:42 AM	 	IFTTT Heartbeat	42 seconds
      Nov-23 4:01:09 AM	 	IFTTT Heartbeat	69 seconds
      Nov-23 3:00:16 AM	 	IFTTT Heartbeat	16 seconds
      Nov-23 2:00:23 AM	 	IFTTT Heartbeat	23 seconds
      Nov-23 1:00:44 AM	 	IFTTT Heartbeat	44 seconds
      Nov-23 12:00:20 AM	 	IFTTT Heartbeat	20 seconds
      Nov-22 11:00:26 PM	 	IFTTT Heartbeat	26 seconds
      Nov-22 10:00:47 PM	 	IFTTT Heartbeat	47 seconds
      Nov-22 9:00:15 PM	 	IFTTT Heartbeat	15 seconds
      Nov-22 8:00:17 PM	 	IFTTT Heartbeat	17 seconds
      Nov-22 7:00:13 PM	 	IFTTT Heartbeat	13 seconds
      Nov-22 6:00:16 PM	 	IFTTT Heartbeat	16 seconds
      Nov-22 5:00:30 PM	 	IFTTT Heartbeat	30 seconds
      Nov-22 4:00:15 PM	 	IFTTT Heartbeat	15 seconds
      Nov-22 3:00:06 PM	 	IFTTT Heartbeat	6 seconds
      Nov-22 2:00:24 PM	 	IFTTT Heartbeat	24 seconds
      Nov-22 1:00:11 PM	 	IFTTT Heartbeat	11 seconds
      Nov-22 12:00:35 PM	 	IFTTT Heartbeat	35 seconds
      Nov-22 11:00:09 AM	 	IFTTT Heartbeat	9 seconds
      Nov-22 10:00:19 AM	 	IFTTT Heartbeat	19 seconds
      Nov-22 9:00:05 AM	 	IFTTT Heartbeat	5 seconds
      Nov-22 8:00:38 AM	 	IFTTT Heartbeat	38 seconds
      Nov-22 7:00:28 AM	 	IFTTT Heartbeat	28 seconds
      Nov-22 6:00:39 AM	 	IFTTT Heartbeat	39 seconds
      Nov-22 5:00:18 AM	 	IFTTT Heartbeat	18 seconds
      Nov-22 4:00:41 AM	 	IFTTT Heartbeat	41 seconds
      Nov-22 3:00:07 AM	 	IFTTT Heartbeat	7 seconds
      Nov-22 2:00:17 AM	 	IFTTT Heartbeat	17 seconds
      Nov-22 1:00:23 AM	 	IFTTT Heartbeat	23 seconds
      Nov-22 12:00:26 AM	 	IFTTT Heartbeat	26 seconds
      And from the HS trigger:

      Code:
      Nov-25 12:05:00 PM	 	Check 5:00	0 seconds
      Nov-25 11:05:00 AM	 	Check 5:00	0 seconds
      Nov-25 10:05:00 AM	 	Check 5:00	0 seconds
      Nov-25 9:05:00 AM	 	Check 5:00	0 seconds
      Nov-25 8:05:00 AM	 	Check 5:00	0 seconds
      Nov-25 7:05:00 AM	 	Check 5:00	0 seconds
      Nov-25 6:05:00 AM	 	Check 5:00	0 seconds
      Nov-25 5:05:00 AM	 	Check 5:00	0 seconds
      Nov-25 4:05:00 AM	 	Check 5:00	0 seconds
      Nov-25 3:05:00 AM	 	Check 5:00	0 seconds
      Nov-25 2:05:00 AM	 	Check 5:00	0 seconds
      Nov-25 1:05:00 AM	 	Check 5:00	0 seconds
      Nov-25 12:05:00 AM	 	Check 5:00	0 seconds
      Nov-24 11:05:00 PM	 	Check 5:00	0 seconds
      Nov-24 10:05:00 PM	 	Check 5:00	0 seconds
      Nov-24 9:05:00 PM	 	Check 5:00	0 seconds
      Nov-24 8:05:00 PM	 	Check 5:00	0 seconds
      Nov-24 7:05:00 PM	 	Check 5:00	0 seconds
      Nov-24 6:05:00 PM	 	Check 5:00	0 seconds
      Nov-24 5:05:00 PM	 	Check 5:00	0 seconds
      Nov-24 4:05:00 PM	 	Check 5:00	0 seconds
      Nov-24 3:05:00 PM	 	Check 5:00	0 seconds
      Nov-24 2:05:00 PM	 	Check 5:00	0 seconds
      Nov-24 1:05:00 PM	 	Check 5:00	0 seconds
      Nov-24 12:05:00 PM	 	Check 5:00	0 seconds
      Nov-24 11:05:00 AM	 	Check 5:00	0 seconds
      Nov-24 10:05:00 AM	 	Check 5:00	0 seconds
      Nov-24 9:05:00 AM	 	Check 5:00	0 seconds
      Nov-24 8:05:00 AM	 	Check 5:00	0 seconds
      Nov-24 7:05:00 AM	 	Check 5:00	0 seconds
      Nov-24 6:05:00 AM	 	Check 5:00	0 seconds
      Nov-24 5:05:00 AM	 	Check 5:00	0 seconds
      Nov-24 4:05:00 AM	 	Check 5:00	0 seconds
      Nov-24 3:05:00 AM	 	Check 5:00	0 seconds
      Nov-24 2:05:00 AM	 	Check 5:00	0 seconds
      Nov-24 1:05:00 AM	 	Check 5:00	0 seconds
      Nov-24 12:05:00 AM	 	Check 5:00	0 seconds
      Nov-23 11:05:00 PM	 	Check 5:00	0 seconds
      Nov-23 10:05:00 PM	 	Check 5:00	0 seconds
      Nov-23 9:05:00 PM	 	Check 5:00	0 seconds
      Nov-23 8:05:00 PM	 	Check 5:00	0 seconds
      Nov-23 7:05:00 PM	 	Check 5:00	0 seconds
      Nov-23 6:05:00 PM	 	Check 5:00	0 seconds
      Nov-23 5:05:00 PM	 	Check 5:00	0 seconds
      Nov-23 4:05:00 PM	 	Check 5:00	0 seconds
      Nov-23 3:05:00 PM	 	Check 5:00	0 seconds
      Nov-23 2:05:00 PM	 	Check 5:00	0 seconds
      Nov-23 1:05:00 PM	 	Check 5:00	0 seconds
      Nov-23 12:05:00 PM	 	Check 5:00	0 seconds
      Nov-23 11:05:00 AM	 	Check 5:00	0 seconds
      Nov-23 10:05:00 AM	 	Check 5:00	0 seconds
      Nov-23 9:05:00 AM	 	Check 5:00	0 seconds
      Nov-23 8:05:00 AM	 	Check 5:00	0 seconds
      Nov-23 7:05:00 AM	 	Check 5:00	0 seconds
      Nov-23 6:05:00 AM	 	Check 5:00	0 seconds
      Nov-23 5:05:00 AM	 	Check 5:00	0 seconds
      Nov-23 4:05:00 AM	 	Check 5:00	0 seconds
      Nov-23 3:05:00 AM	 	Check 5:00	0 seconds
      Nov-23 2:05:00 AM	 	Check 5:00	0 seconds
      Nov-23 1:05:00 AM	 	Check 5:00	0 seconds
      Nov-23 12:05:00 AM	 	Check 5:00	0 seconds
      Nov-22 11:05:00 PM	 	Check 5:00	0 seconds
      Nov-22 10:05:00 PM	 	Check 5:00	0 seconds
      Nov-22 9:05:00 PM	 	Check 5:00	0 seconds
      Nov-22 8:05:00 PM	 	Check 5:00	0 seconds
      Nov-22 7:05:00 PM	 	Check 5:00	0 seconds
      Nov-22 6:05:00 PM	 	Check 5:00	0 seconds
      Nov-22 5:05:00 PM	 	Check 5:00	0 seconds
      Nov-22 4:05:00 PM	 	Check 5:00	0 seconds
      Nov-22 3:05:00 PM	 	Check 5:00	0 seconds
      Nov-22 2:05:00 PM	 	Check 5:00	0 seconds
      Nov-22 1:05:00 PM	 	Check 5:00	0 seconds
      Nov-22 12:05:00 PM	 	Check 5:00	0 seconds
      Nov-22 11:05:00 AM	 	Check 5:00	0 seconds
      Nov-22 10:05:00 AM	 	Check 5:00	0 seconds
      Nov-22 9:05:00 AM	 	Check 5:00	0 seconds
      Nov-22 8:05:00 AM	 	Check 5:00	0 seconds
      Nov-22 7:05:00 AM	 	Check 5:00	0 seconds
      Nov-22 6:05:00 AM	 	Check 5:00	0 seconds
      Nov-22 5:05:00 AM	 	Check 5:00	0 seconds
      Nov-22 4:05:00 AM	 	Check 5:00	0 seconds
      Nov-22 3:05:00 AM	 	Check 5:00	0 seconds
      Nov-22 2:05:00 AM	 	Check 5:00	0 seconds
      Nov-22 1:05:00 AM	 	Check 5:00	0 seconds
      Nov-22 12:05:00 AM	 	Check 5:00	0 seconds
      Cheers
      Al
      HS 3.0.0.548: 1990 Devices 1172 Events
      Z-Wave 3.0.1.262: 126 Nodes on one Z-Net

      Comment


      • #4
        Well a 45 minute delay is worse than useless. Up to three days ago I was getting notified within a few seconds, which was good enough for my purposes, now this long delay. What concerns me is that IFTTT flag the issue - up to "one hour delay". Why is it happening? Is it a Homeseer issue (which I assumed since it is only "Applets/Recipies" using the Homeseer Channel that I am seeing this issue on)??

        Comment


        • #5
          The IFTTT plug in from Spud is showing great promise. It utilizes Dropbox for a temporary storage area and I set a trigger for Pushbullet when a new file is detected. (Spud has specific instructions in the forum on how to set this up).

          While Dropbox is also categorized as an app that can take up to an hour delay, I find that my triggers are firing within a couple of minutes using IFTTT. I never got anything close to that performance using the Homeseer IFTTT channel. HS IFTTT is also pretty limited in what you can do with it compared to firing events with the IFTTT plug-in.

          Comment


          • #6
            I have noticed some incredible delays recently. Last night my bedroom lights went on at 12:27 am - presumably from a command that was sent several hours prior to that.

            At first I thought it was the Wink hub that I am using for those lights. But after further investigation the IFTTT log shows that the command was received at 12:27.

            So did Homeseer take that long to send the command to IFTTT or did IFTTT take that long to process it?

            What makes this even harder to diagnose is that the Activity log page in IFTTT doesn't work. The more button to get more (older activities) doesn't seem to do anything.

            Of course this wouldn't be necessary if there was native Zigbee support in HS3 but I will leave that for another forum.

            Comment


            • #7
              I decided long ago when it first came out that IFTTT was not good for any thing where timing mattered and delays were not acceptable.

              According to their own Status site they seem to have issues every few days.
              http://status.ifttt.com/


              I wonder if the 1 hour delay was put in there after the DOS attacks that were happening back in October had affected myHS.?.?

              Comment


              • #8
                It's not just HomeSeer. My Ring channel has the same message, and an hour delay on a doorbell notification is totally useless.

                Comment


                • #9
                  IFTTT is growing faster than it can keep up. I stopped using it because it was only reasonably reliable during the day, completely useless in the evening times. I would never trust IFTTT to be used for anything time related or controlling devices like lights.

                  It's an awesome concept, but having serious growing pains, and this is one where I don't think you can or it fair to blame HS for.

                  Comment


                  • #10
                    IFTTT inbound to HS is working flawlessly. HS outbound to IFTTT is a disaster.

                    I have IFTTT on my wife's phone and mine. When one of us leaves Wi-Fi range, our phone reaches through IFTTT to turn off specific things we like to have on when home. When one of us returns into Wi-Fi, our phone reaches through IFTTT and turns stuff on for us.

                    This is the IFTTT Android applet connecting to IFTTT, which connects to MYHS, which connects to my HS system and turns either my wife's or my virtual device on or off, representing who is home or away. This is reliable to the extent that when I see the Wi-Fi connection bubble on my phone, my things turn on if all other event conditions are met within one second. I don't need geofencing.

                    The problem is with my empty house event. When one of us is already off Wi-Fi and the other drops off Wi-Fi, that causes both of our virtuals to be off. When we are both away, I set an additional virtual to Away. I have an event set for when that virtual changes to Away that sets a virtual for each camera to on.

                    I have an event on the camera virtuals that uses the HS IFTTT channel to reach into IFTTT to tell Netgear to arm that Arlo Q camera. Typically over the past 3 weeks this eventually succeeds about 10-15 minutes after we leave, and we'll get immediate notifications from Arlo as the dogs pass the cameras and kindly provide us a nice system check. When I set this up in early October, it triggered nearly immediately.

                    HS > IFTTT has recently degraded significantly. The massive slowdown seemed to be at Thanksgiving, and I wrote it off to nobody minding the servers.

                    Once one of us comes home (connects to Wi-Fi), our phone gets HS' Wi-Fi virtual set in a blink. That also sets the additional virtual to Home. I have an HS event on that virtual changing to Home that sets the camera virtuals of off. The HS IFTTT channel is configured to pick up that state change and tell IFTTT to tell Netgear to disarm my cameras.

                    Because I'm home and moving in front of the cameras, I become painfully aware of the delay to disarm: immediate and constant phone notifications. There's certainly no delay in Arlo sending notifications, as you would expect for a security device. The past several days, I've had to disarm the cameras in the Arlo app.

                    While writing this message, I manually flipped the Arlo camera virtuals on at 9:29pm. So far, only one of the HS IFTTT channel triggers has armed a camera, at 9:52pm. I'm using the IFTTT activity log for this proof. At Netgear's Arlo site, the correct camera for the IFTTT applet activity entry is armed. It's 10:14 and none of the other cameras have armed.

                    So:
                    - Android phone > IFTTT > HS = immediate
                    - Ring doorbell > IFTTT> HS = immediate
                    - Alexa > IFTTT > HS = immediate (as are the HomeSeer skills without using IFTTT)
                    - HS > IFTTT > Arlo = large varying delay
                    - HS > IFTTT > IFTTT's activity log that HS did something = large delay, and in many cases, ignored completely and never logged at IFTTT

                    On December 7 and 8 (I saw the MYHS down again thread), I have pages of HomeSeer Error and HomeSeer Timeout Error messages in the activity logs for my HS IFTTT channel applets.

                    Meanwhile, all my Alexa stuff is working great, but that's Alexa > AWS > MYHS > me. Inbound works great.

                    The HS IFTTT channel needs debugging. When I use Check Now on the applets at IFTTT, they fire immediately without errors, so for example the cameras arm/disarm immediately when they don't have to wait for the HS IFTTT channel to tell them to arm/disarm. I've got three other technologies making immediate connections to IFTTT and causing events to trigger in HomeSeer.

                    I can totally rely on HomeSeer responding to IFTTT, I cannot rely on HomeSeer to command IFTTT and the downstream cameras. I need the complexity of HomeSeer's event logic and what my devices and plugins contribute to the events. I can't have my phone IFTTT client arming my cameras every time I drop off Wi-Fi - I use UltraMon to check that my Wi-Fi access point has been online for at least 10 minutes before I consider the drop off Wi-Fi to be accurate.

                    Before I did any of the testing above, I shutdown and restarted HS3 and confirmed a problem-free connection to MYHS in my log.

                    Comment


                    • #11
                      Sounds like your experience is not the norm and you should consider yourself lucky. I first noticed the problem on my Ring > IFTTT > HS applet, and it's still a multiple minute delay... I have a separate Ring > IFTTT > notification applet to confirm it's not an HS issue and it has the same performance problems.

                      Comment


                      • #12
                        So what is an example of where the homeseer IFTTT integration is useful? I am scratching my head trying to think about events that work well with a one+ hour delay built in?

                        Comment


                        • #13
                          I am using HS3 to send a Lights on at sunset command to one of my Lutron Caseta dimmer switches. So far, I have not noticed a problem. It may be a few minutes delayed, but that is not really noticeable because the sunset time is also changing. I have never seen a delay of 30-60 minutes.

                          Steve Q


                          Sent from my iPad using Tapatalk
                          HomeSeer Version: HS3 Pro Edition 3.0.0.368, Operating System: Microsoft Windows 10 - Home, Number of Devices: 373, Number of Events: 666, Enabled Plug-Ins
                          2.0.83.0: BLRF, 2.0.10.0: BLUSBUIRT, 3.0.0.75: HSTouch Server, 3.0.0.58: mcsXap, 3.0.0.11: NetCAM, 3.0.0.36: X10, 3.0.1.25: Z-Wave,Alexa,HomeKit

                          Comment


                          • #14
                            I questioned IFTTT support about the 1 hour delay tag. Guess what, never got a response.

                            Comment


                            • #15
                              Originally posted by simonmason View Post
                              So what is an example of where the homeseer IFTTT integration is useful? I am scratching my head trying to think about events that work well with a one+ hour delay built in?
                              I have completely abandoned IFTTT after a couple of months of trying to do something relevant with it. Great idea but the execution is terrible. It's not just limited to HS either. IFTTT doesn't seem to have it's act together on timely submission of events. That, combined with the kiddie interface for setting up events is just not worth the hassle IMHO.

                              Comment

                              Working...
                              X