Google_maps last_seen attribute goes backwards

Nope, there isn’t. There is a volatile variable that holds the most recently seen timestamp for each member from the Life360 server. That gets updated when a new timestamp is received which is later in time. But if the new timestamp is older than the most recently seen timestamp, then you get that message. When HA restarts this variable is effectively cleared.

So, again, this is happening because that is what the Life360 server is sending. I have no idea why it does this sometimes.

FWIW, I use both life360 and google_maps for three users/devices. I see this message all the time with google_maps (by that I mean it’s not uncommon, not that it’s constant), but I almost never see it with life360. Two of the devices are Android based, and one is an iPhone.

Unsure if this has anything to do with the Life360 issue or something else. Unsure if it was there before. Many likely related messages afterwards. How do I issue a Session.rollback()?

Source: components/recorder/__init__.py:357
Integration: Recorder ([documentation](https://www.home-assistant.io/integrations/recorder), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+recorder%22))
First occurred: 8:44:36 AM (17 occurrences)
Last logged: 9:20:45 AM

* Error in database connectivity during keepalive: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.DatabaseError) database disk image is malformed [SQL: INSERT INTO events (event_type, event_data, origin, time_fired, created, context_id, context_user_id, context_parent_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?)] [parameters: ('state_changed', '{}', 'LOCAL', '2020-07-10 16:12:14.004532', '2020-07-10 16:12:14.010703', 'bf6bf4cacbd54b99869042aef3781431', None, None)] (Background on this error at: http://sqlalche.me/e/4xp6) (Background on this error at: http://sqlalche.me/e/7s2a).```

to answer your questions. This persons life 360 reports have never shown up in HA life360, only this error message. They are using an android device. Can see updates fine using Life 360 app. I have been excluding this person in config to avoid errors but this was an effort to resolve it if possible. I’m not a developer, simply trying to follow instructions and very much enjoying the adventure. Using a Pi 4 HASSIO 0.112.3 (0.112.4 seemed to cause WYZE Sense issues).

No idea what that is. I doubt it’s related.

seems I some clean up to do ( perhaps db file is corrupt), before making progress. Restoring to 0.112.3 may have created some issues.

Will revisit if I learn anything that I think might be useful to you. Thanks for the assistance.

1 Like