Announcement

Collapse
No announcement yet.

HSBuddy and intermittent geoFencing (irritating)

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

    #16
    For what it's worth, there are myriad reasons why a push notification would be delayed. The communication doesn't go directly from your HS system to your phone, it gets delivered to the Apple or Android servers, which then send it out to as a generic push message, then your phone has to receive it, parse it, decide what to do with it, and finally pop it on the screen. There are so many variables between point A and point B (network latency, service load, phone battery optimization, security settings, etc., etc.) that relying on push notifications for real-time communication is always going to be variable.

    (Disclaimer: I haven't yet used HSBuddy for push (I just actually tried it out - don't ask, must have been living under a rock, where has this been all my life?!?) but will be looking to switch from my current pushover setup to this in order to simplify my setup to have less moving parts/running plugins.)

    Comment


      #17
      Originally posted by bearhntr View Post
      I still cannot get the PUSH NOTIFICATION to work.
      Are you still having issues receiving notifications? Just to make sure it isn't related to the special event configuration for the lock - can you try creating an event with only a push notification action and triggering it manually? Normally you would receive the notification on the selected device within seconds.

      Also note, sometimes when HSBuddy is reinstalled (I've also seen it with some OS updates), it is possible the same device gets registered in HS twice. If you go to the HSBuddy configuration page and you see 2 devices with the same name ("Curtis' Galaxy S10+" in your case) you can delete all duplicates except for the one that has connected the most recently.

      Comment


        #18
        Originally posted by avargaskun View Post

        Are you still having issues receiving notifications? Just to make sure it isn't related to the special event configuration for the lock - can you try creating an event with only a push notification action and triggering it manually? Normally you would receive the notification on the selected device within seconds.

        Also note, sometimes when HSBuddy is reinstalled (I've also seen it with some OS updates), it is possible the same device gets registered in HS twice. If you go to the HSBuddy configuration page and you see 2 devices with the same name ("Curtis' Galaxy S10+" in your case) you can delete all duplicates except for the one that has connected the most recently.
        OK... I just tried this - see picture for the Event I created. I clicked the 'running man' icon - The first time I did this, it was almost 30 seconds before the phone made the noise and I got the pop-up notification. I had the phone AWAKE and holding in my hand. I then did it again once the screen had gone off (locked). I got the notification in about 2 seconds. I waited about 3 minutes and did it again...this time, no sound or notification until I woke up the phone (with my fingerprint) and then about 6 seconds later I got the notification.

        Click image for larger version  Name:	Testing GeoFence.png Views:	0 Size:	201.1 KB ID:	1479794
        I would really like to get this working...as I want to be able to LEAVE the house and Trust that the doors lock, etc. Right now, I manually lock them as I leave - as I do not feel confident that the "LEAVES" event is running. So far over the last couple weeks - the ARRIVES even does 'seem' to be working. Either I get out of the car in the driveway and I hear the Schlage lock unlocking...or I go to the door and it opens right up. Not sure of the "passing through" even is working - I would like to do a notification on there too - while testing - so that if I happen to pass-through the GeoFence - the door does not UNLOCK - and then never re-locks. (see below):

        Click image for larger version

Name:	Drive-Thru GeoFence.png
Views:	11
Size:	277.0 KB
ID:	1479795

        Curtis

        Comment


          #19
          ‚Äč
          Originally posted by bearhntr View Post
          The first time I did this, it was almost 30 seconds before the phone made the noise and I got the pop-up notification. I had the phone AWAKE and holding in my hand.
          This is definitely odd. I looked this up online, I didn't find much. Samsung appears to be especially aggressive at sleeping apps and background processes. There are a few settings that can be tweaked to avoid that. But if you had the device with the screen on and the app running that doesn't sound like the reason. I came across the concept of 'priority' notifications (Android only) and put support for that in the most recent version of the plugin (3.25.614.1)

          After upgrading you'll be able to mark a notification as 'high priority' which may help get rid of that delay, but not quite sure since I have not been able to reproduce the delay in delivery myself. In any case, I have tested this for the past couple days with an event scheduled to run every 30 minutes for 12 hours a day. Each time I received the notification on the second it was expected.

          Click image for larger version

Name:	notification test.png
Views:	0
Size:	62.6 KB
ID:	1480125

          Comment

          Working...
          X