So, if you have
show_as_state:, then any “Place” defined in Life360 will change the device_tracker’s state string to the name of that Life360 place (when Life360 determines you are at that place.) One exception is if the Place’s name, converted to all lower case is exactly ‘home’, then the state will become ‘home’. (All lower case ‘home’ is special.) Also note that a Life360 Place name takes precedence over the GPS coordinates. (I believe much of this is described on my doc page.)
I would definitely recommend having all "home"s be the exact same lat/lon and the exact same radius. And note that even HA itself has both a home location in the basic homeassistant config, and optionally a zone.home.
Also note that a device_tracker’s state string will never actually be ‘Away’, but rather ‘not_home’. (The frontend shows ‘not_home’ as Away, and ‘home’ as Home.) Well, unless you happen to have a Life360 Place named ‘Away’, which you probably shouldn’t.
Until you get this figured out, you might want to remove
show_as_state, or at least comment it out. Then it will be based strictly on GPS coordinates and the HA Device Tracker component code will determine if this is in a HA zone.
You might want to check your config for the logger component. The default is debug, but it sounds like maybe you’ve changed that.
Note that letter case is important. As mentioned above, though, all lower case ‘home’ is special, and any Place name, when converted to all lower case, that matches ‘home’ would be changed to ‘home’. So in order to see two different “homes” (i.e., with two different colors in the history), they must be different than just the four letters h, o, m and e.