This is "normal" to happen sometimes. It should be re-trying on its own and succeeding. If that is the ONLY response you are getting every single polling period, then you may need to fetch a new web token.
Are you running the most recent version? At this moment that is v5.0.15. If you are not, you should get it updated ASAP. There have been MANY MANY fixes and enhancements over the past couple months to make this app pretty rock solid and as self-healing as possible.
As for polling period, I personally run at 3 min standard polling and 20 seconds for dynamic (moving). If you don't have the option for "dynamic polling" then you are definitely waaaay behind.
Yeah... I was actually recently looking at that. Hubitat is giving life360 people the "switch" icon and thinks of them as on/off, etc. But the Life360+ driver is reporting presence info also and the hubitat DOES understand present/away for them also (because I use that in routines). Teh driver exposes several capabilites of a Life360 member:
One of which, as you see, is "switch". Another odd one is "contact sensor" (which would be your "open" and "closed" that you see). I don't know if it's just as easy as removing that and all will magically fix itself or not. I haven't played wit it all yet, but will Soon(tm).
Check your dashboards though. You should be using the "presence" attribute.
I took a few minutes and hit it with a hammer. Yes it appears to be that easy. Note my Life360 members are little houses now and not switches any longer.
As for the "Contact Sensor" it's used in one place:
So when a phone is charging, it's "open" and unplugged it's "closed". Personally I think it should be the other way around, but either way I don't think this provides any real value as the charing state is already being returned and dealt with because of the "battery" capability.
Putting a PR together to remove some useless capabilities, and remove a couple confusing attributes is easy. This could/would be a breaking change for some people depending on how they have routines/dashboards setup. Again, you said the app is showing open/closed. That suggests you have something looking at the Contact Sensor attribute(s) and not the Presence ones. If the contact sensor capability were to just disappear in the next release, your stuff breaks with no warning.
Yes I am running 5.0.15. This only recently started happening. It will happen on every 2 or 3 polls for a while, then stop for several hours, then start again. Very strange.
Many thanks Matt, I first commented out and then just removed both the 'switch' and 'contact' attributes in the driver code. I'm not sure if that's what you meant by 'hit it with a hammer'. I'm still showing 'Closed' in the Android mobile app. Let me know if I need to modify some other aspect of the driver code.
Where are you still seeing this? You may have to make a manual change - and that's the point I'm trying to make. While it may be wrong, to just make it all disappear in another release could/would break people's installs and require manual intervention to fix. Still, fixing it is probably better and leaving it broke which leaves people confused.
Secondly, just commenting out those lines isn't going to change anything. You would need to disable and re-enable the app to "restart" it so all that is reread.
Well, I disabled and restarted the app.. no change. But it's just an UI issue so not a big deal. Still shows as Closed (or sometimes Opened for no apparent reason) in the Android HE app. But the functionality of the Life360+ app as a presence sensor works great and that's my primary use.
Personally, I think that's backwards. "closed" should be "charging". But either way, I think that is confusing.
Whatever, the case, if you plug your phone in and watch that device, it should change state if you didn't comment out that capability. Now that you said you did, it will never change.
How long that takes to refresh should depend on your polling period.
I have not seen the 403 error in over 10 hours since getting a new web token so I assume that was the cause. Is it suggested to change the web token every so often?
I had a bunch of 403 errors a day or 2 ago. I haven't been checking every day like I used to and I do see I haven't had any today. But, that's just to say -- you shouldn't ever have to update the token. I haven't ever changed mine.
I found that a simple mistake - logging into the Life360 website using the credentials you used when you captured the token - appears to invalidate the previous token. I need to figure out if I can create an additional login just for the Hubitat/Life360 i/f token so that I don't make that mistake again. So far, I'm just staying away from the web and my token has lasted for weeks.
For whatever it's worth, I think they have been having some problems lately. Friday was a looooong line of 403 even after changing my token - three times. It started magically working late in the evening on its own. It's been pretty solid since. A couple 403 early this morning (Sunday 2025-01-26) but that's it.
+1 on the question - what are "recommended" settings now for polling? I was at every 1 minute, but changed it to 3 mins, turned on dynamic (doh, behind that curve) and set that to 20 seconds.
Haven't seen any errors in past 15 mins - yeah, I know 15 mins, but I just rebooted and cleared logs this afternoon (for other reasons).
Honestly, I don't know that there are "recommended" settings at this point. With all the other recent work that has gone into this app, the (known) show stopping problems have been resolved. Again, I personally run at 3m/20s. There some here that don't bother with the "dynamic polling" and run a straight 20s all the time. Some just 5 minutes isd good enough.
It would indeed be nice to have a way to see what settings "work best" (keeps 403 to a minimum), but without collecting user data, shipping it off to somewhere, processing, yadda yadda, it's not going to happen.
Getting the 403 isn't uncommon. However I've gone through my logs and it looks like they were having big problems Sunday morning for a few hours (2025-01-26) and Friday evening (2025-01-24). There's a few reports here of expired tokens on Friday. I thought mine had and refreshed it THREE times, but it didn't fix itself until later in the eve so I assume it was them and not me.
All that said, I see two other one-off quick blips otherwise clean.
