If somehow the timestamp retrieved from the Life360 server was corrupted and was interpreted as some time in the future, it is possible to see this warning until a new timestamp comes that is after it. However, this invalid timestamp will not be retained across HA restarts. So, restarting HA should resolve the problem (unless it happens again for some reason.)
Honestly, this doesn’t happen much that I’m aware of, and when it does it seems to resolve itself in short order. And from the few times I’ve heard of it or seen it happen directly, the problem was more that an old timestamp was unexpectedly received as opposed to one in the future.
Bottom line, there isn’t a whole lot that can be done about it. The HA integration has to believe the data it is receiving from the Life360 server. If the server sends bad data sometimes,
Does the warning happen constantly for this one person? Are there good updates in between? Do the GPS coordinates in HA tend to keep up with that person’s device?
You could try adding this to your config:
Then restart HA. After a while you can check home-assistant.log and look for messages concerning life360. There might be some messages, especially DEBUG messages, that can shed light on how this person’s device is behaving.