Couple of days ago, I noticed that my Life360 badges had stop updating the status. My initial thoughts were, may be my firewall is blocking the connection, as I have recently introduced a new router and firewall in my house. To prov the theory I tried with another GSM router, no firewall. I am still having the issues connecting to Life360.
I had my Life360 integration but I deleted, when I was trying to workout what was going, now I don’t even have integration.
Error message from the log file:
Unexpected error communicating with Life360 server: HTTPSConnectionPool(host=‘api.life360.com’, port=443): Max retries exceeded with url: /v3/oauth2/token.json (Caused by NewConnectionError(’<urllib3.connection.HTTPSConnection object at 0x7f70e2b190>: Failed to establish a new connection: [Errno -2] Name does not resolve’))
18:23:34 – Life360 (ERROR) - message first occurred at 12:49:20 and shows up 44 times
Well, not sure what to tell you. Clearly from the HA error message there was a DNS lookup issue: “Name does not resolve”.
How did you install HA? Is it possible the “Terminal on HA” is not running in the same context/container/etc. that HA runs in, which might cause it to be able to resolve the name whereas HA can’t?
Do you have other entities in HA that communicate with outside servers, such as a weather entity, etc.?
The URL that is failing is the first one that the life360 package uses, which is to obtain an authorization toke (basically logging in.) If that doesn’t work of course nothing else will.
Again, apologies for the late reply. From your previous post, you mentioned DNS, one thing I didn’t think. So I excluded the HA IP Address from the DNS Filter and it started to work.
I just got a new Asus router that has DNS Filter mode, that allows you to protect specific LAN devices against harmful online content by forcing them to use a DNS server that provides filtering services. For some reason Life 360 / HA is filtered and causing issues. For time being I have excluded HA entry until I figure out what to do. All other services like weather were also causing errors, but now working