search

hepcat72 / node-red-contrib-life360

GNU General Public License v3.0
3 stars 4 forks source link

Rare random arrival event #14

Open hepcat72 opened 2 years ago

hepcat72 commented 2 years ago

On Monday, while my wife and I were in bed, I received an SMS sent by my pi that notified me of it running automations triggered by my Life360 "First to arrive" rule. This has happened a few times in the past, but I'd always chalked it up to the fact that my wife (likely) had her Wifi off (and thus location accuracy was poor), but since she was right next to me, I checked her phone, and her Wifi was on, and had been on all day. The Life360 app also confirmed that.

Other things I noted:

I haven't checked my logs yet, but since I have multiple automations to control the floods, the SMS notification always tells me which automation was responsible, so I know it was Life360.

Have you guys experienced erroneous Life360 events? @brianmay @MaksimShakavin

brianmay commented 2 years ago

May not help much, but I have found:

Possibly if I process the latitude/longitude and geofencing myself I might get better results, not sure, haven't tried this yet.

hepcat72 commented 2 years ago

I actually have mine set large (5,280 feet) so that the air conditioners have started to cool down the house a tad by the time I arrive, but I haven't had a problem with accuracy (barring a brief time when Life360 was acting very buggy). That said, if it was an accuracy issue, I'd expect to see app notifications too.

I haven't encountered the WiFi issue (though I rarely check that it's accurate, because I know my wife turns off her WiFi at work).

hepcat72 commented 2 years ago

OK. I just started debugging this because I got another errant Life360 event this morning (without an app notification), and I noted that my flow is still setup to receive events from my old Life360 IFTTT applet (via webhookrelay), so it could be that the errant events are somehow coming from it. Instead of just deactivating the IFTTT input, I split it up and added a source note to the SMS so that I can confirm where the events are coming from, but I'd be willing to bet the source is not Life360, since there's no app notification.

If I confirm it's coming from webhookrelay, I'll dig deeper to figure out whether it's actually an event from my still-active IFTTT account or whether my WHR account is compromised...

hepcat72 commented 9 months ago

Happened twice over-night (10/10/2023 at precisely 5:48:47am and 5:54:17am). My flow notified me of the arrival event while already home. Definitely coming from my Life360 Arrival event node. Actually, it came out of both my individual arrival node and my "first to arrive node" even though my wife was home too. And there was no Life360 app notification. The app shows I have been home since 1:47pm yesterday (10/9/2023), and my wife since 2:30pm yesterday.

So weird. Since the app is unaware of the arrival event, this must(?) be an issue with this node? I wish I had saved the JSON that came from the node so I could have inspected it. If you don't count these 2 events as separate events, then this issue's frequency is around once a year.

I just updated my flow to save the JSON. I guess it may be over a year before I have more debug information. I'm kicking myself for not having already implemented that.

hepcat72 commented 9 months ago

Looking at the server.js code... I bet there's a rare edge case involving state. Clearly, the original developer implemented a debug mode to check leave events involved with identifying location changes...