ALERT: Life360 API Changes!

[shill]

Apparently Life360 pushed out some API changes Friday evening that broke a lot of home-grown integrations (since this isn't a public API), and even some of their own legitimate clients. Thanks to the sleuthing of some other folks in the home automation community, the changes were figured out and documented and I was able to quickly incorporate them into the plugin. I have uploaded 4.1.1.0, but it requires HST to move it to the updater which they don't do on weekends, so if your system isn't working I'm afraid you'll need to wait until Monday unless you want to do the old-fashioned manual install, in which case, message me and I'll hook you up with the zip and JSON file required.

[Wade]

Same issue after updating to 4.1.1.0. Debug log attached, data dump below.

[shill]

That debug page shows a very different problem - all that {{ }} stuff should have been resolved by Homeseer by calling the plugin. And the log file doesn't have any actual errors in it, so the problem is most likely showing up in the browser console (F12 in Chrome).

I did see a note in the log that it doesn't believe the credentials are valid, but I didn't see any attempt in the log to validate them; that's the part 4.1.1.0 is supposed to address.

[Wade]

Browser console for which page? Config, debug, other?

[Wade]

Guessing this is it from debug page. Unfortunately I don't understand what I'm looking at. Does it indicate an issue with the PI or with my system?


I re-entered my credentials so pretty confident they're correct.

[Wade]

And these in the log.

[shill]

Those are normal warnings that come from HS pages internally; the fact they're making it to the HS log is because I added some logic to pipe errors from JS into Homeseer so I don't have to ask people to look there, I'm just not 100% confident yet that it's always doing the job so I ask anyway for now.

The fix itself for validating credentials isn't doing the trick yet so still looking into it. From what I've heard the release they did last Friday night blew up a lot of stuff, even "legitimate" clients, so I'm expecting more changes but we can only discover them after the fact since this isn't a published API with a developer program...

[Wade]

Understood, standing by. Let me know if I can provide any useful trial / debug data.

[shill]

Ok, turns out what you're seeing on the debug page is what happens when you load it before any updates have happened, which is a side effect of course of not being able to get an access token. So it's all connected, I just need some better error handling on the debug page... maybe later

[Wade]

Aha. And since it's not updating at all, that's what I'm getting. Now starting to understand a bit of what's going on.

[shill]

Got it figured out. Submitted 4.1.1.1, but it's after 5 so likely won't be there until tomorrow.

[tjankovs]

Thanks for your support...we will report back tomorrow. I'll have to remember to turn off my AC and shut my garage one more day (;>)

TJ

[shill]

Thanks for your support...we will report back tomorrow. I'll have to remember to turn off my AC and shut my garage one more day (;>)

TJ

Yep, hope no burglars stop by tomorrow if my wife or daughter leave since the alarm won't arm itself!

[Wade]

Same.

Thanks for quick work.

[Taz]

Any update on 4.1.1.1?