Ok, then as I suspected, you missed one of the steps. See prefix under C) Changed configuration variables.
Sorry for the trouble Phil. Thank you!
1 Like
Hello, When I use the website of life 360 I have the possibility to have the adress of the member (like : near xxx street)
Is it possible to catch it on home assistant with the custom component?
The address provided by the Life360 server is available in the address attribute with both this custom life360 integration, as well as in the new standard integration.
EDIT: See life360 documentation.
1 Like
Yea this was mentioned somewhere in another Life360 thread, that I found when I couldnât get Life30 compenent to update my 3 zones to 5. Setup alerts, then bam new zones in HA Life360 comoponent. Have since removed alerting as you mention and zone information still comes into the HA debug logs ever sinceâŠ
1 Like
Well, we are using an unofficial, undocumented API, soâŠ
Iâll keep this in mind in case it comes up again. Thx!
1 Like
HI Phil,
just noticed: no more âtime zone nameâ is displayed⊠is that correct or a bug? I know its not listed here https://www.home-assistant.io/components/life360/#additional-attributes but couldnât find a mention of it being dropped?
Time zone name came from the time_as option, which was removed. Again, you can get that from my composite custom integration if youâre interested.
What happened with Life360 component? Yesterday, Iâve moved to âofficialâ Life360 component, delete the custom one, as described, and now i saw this in my log:
Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api.life360.com', port=443): Read timed out. (read timeout=3.05)")': /v3/circles.json
19:17 components/life360/device_tracker.py (WARNING) - message first occured at 2019. jĂșlius 1. 19:36 and shows up 41 times
get_circle_members "Family": CommError: HTTPSConnectionPool(host='api.life360.com', port=443): Max retries exceeded with url: /v3/circles/fe13776b-1a79-44ab-94b1-cbac9de429b0/members (Caused by ReadTimeoutError("HTTPSConnectionPool(host='api.life360.com', port=443): Read timed out. (read timeout=3.05)"))
19:17 components/life360/device_tracker.py (ERROR) - message first occured at 2019. jĂșlius 1. 19:36 and shows up 6 times
Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api.life360.com', port=443): Read timed out. (read timeout=3.05)")': /v3/circles/fe13776b-1a79-44ab-94b1-cbac9de429b0/members
19:16 components/life360/device_tracker.py (WARNING) - message first occured at 2019. jĂșlius 1. 19:36 and shows up 12 times
get_circles: CommError: HTTPSConnectionPool(host='api.life360.com', port=443): Max retries exceeded with url: /v3/circles.json (Caused by ReadTimeoutError("HTTPSConnectionPool(host='api.life360.com', port=443): Read timed out. (read timeout=3.05)"))
19:16 components/life360/device_tracker.py (ERROR) - message first occured at 2019. jĂșlius 1. 23:02 and shows up 13 times
Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api.life360.com', port=443): Read timed out. (read timeout=3.05)")': /v3/circles/fe13776b-1a79-44ab-94b1-cbac9de429b0/members
19:16 components/life360/device_tracker.py (WARNING) - message first occured at 2019. jĂșlius 1. 19:36 and shows up 17 times
Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api.life360.com', port=443): Read timed out. (read timeout=3.05)")': /v3/circles.json
19:16 components/life360/device_tracker.py (WARNING) - message first occured at 2019. jĂșlius 1. 19:36 and shows up 30 times
These are communication errors between the life360 integration running in HA and the Life360 server. They just happen sometimes. In fact it happened to me a few times today. They should only be intermittent. Are your life360 related device_tracker entities updating? (At the very least, check their last_seen attributes.)
FYI, sometimes, even when you see these warnings/errors, itâs still âworkingâ, because it can be successful between the errors. If you see these a lot, yet the trackers are still updating, you can try increasing the warning and/or error thresholds.
Is show_as_state: places option still working with life360 component toghether with moving and driving?
No. This is mentioned in the transitioning instructions. Also see the official life360 integration documentation.
Ok, so we donât have anymore infos about in which zone is the device? Only home, not_home, driving and moving ?
It always shows when a device is in a HA zone. show_as_state: places used to show when a device was in a Life360 Place, which although similar, is not the same.
If you want to have zones in HA that match the Places you have in Life360, see the doc page. It is discussed there.
Hmm⊠not so clear.I am asking this as, after migrating to the official component, if i check the history of the device, before (with the custom component) i could see if the device was in an HA zone (for example, in my case at the tennis club). Now i can see only driving or moving and not in which HA zone it was.
In my case being in the tennis club HA zone i cannot see this just before, but only not_home.
Hope to be clear enoughâŠ
Look on the States page. What entities do you see that start with zone.?
I see the zones configured into HA. And between them there is the tennis club zone.
FYI if i check the history of the other member in Life360 i can see the right place where she is actuallyâŠ
Ok, this is the third time that Iâve heard of something like this. It happened to me, then someone else, and now you. There may be a bug in the device_tracker component-level code, but Iâm not sure.
If you look at the map when a device_tracker is clearly in a zone, do you find that the device_tracker's state does not reflect the name of the HA zone? I guess based on what youâre saying, that is indeed the case. Specifically, are there any device_tracker's that are in the home zone? And if so, if you look at the map, is the icon still visible on the map for the tracker? What is the state of the tracker? home? not_home? âŠ?
For me, what seemed to fix it (and I havenât seen it since) is simply restarting HA.
Actually i am at home and i can see the icon in the map at the right position. My wife, which is in a HA zone is rightly visible in the map at the right zone. So it seems that this problem is related only to my device tracker when not_home and in a HA zone.
Iâll restart HA and see what happensâŠ
A device tracker that is in the home zone (and whoâs state is home) will not be shown on the map. This is normal behavior and has been for as long as I know. So, if youâre home, but still visible on the map (and especially when youâre clearly in the home zone), and your deviceâs state is not home, then thatâs wrong.
When you say your wife is in another HA zone, is her device_tracker's state the name of that zone? Or is it not_home? If the former, then itâs working correctly. If the latter, then thatâs wrong, too.