Revisit Home map history after Life360 0.10.2 settles

[CCOSTAN]

Summary

The Home view became browser-unresponsive because three family map cards were rendering 24 hours of high-frequency Life360 recorder history. The page expanded to about 24,068 DOM elements, including roughly 22,503 SVG path nodes.

Birdseye was tested separately and confirmed not to be the cause.

Current mitigation

• The three family maps in config/dashboards/overview/sections/10_family.yaml are back to hours_to_show: 0.
• Current family positions remain visible.
• Historical routes remain available from the dedicated Family Locator view.
• Birdseye remains restored.

Underlying update

• Upgraded the custom Life360 integration from 0.7.0 to 0.10.2 and its life360 dependency from 7.0.1 to 7.2.0.
• HACS now reports Life360 0.10.2 as downloaded and managed.
• HACS exposes available integration releases as update entities, but does not install them automatically unless an update automation or manual install invokes update.install.

August 24 retest

• Measured fresh recorder churn at roughly 21,000 combined tracker/person rows over 24 hours, so the upstream update has not eliminated high-frequency writes.
• Trialed a one-hour map window. The rendered Home page stayed healthy at about 1,659 elements, three maps, zero card errors, and a 180 ms reload.
• The trial was inconclusive for route rendering because nobody moved during the test window.
• Reverted the Home maps to current-position-only until a meaningful movement test is available.

Revisit on or after September 23, 2026

• Measure a fresh 24-hour recorder write count for the four family trackers and their person.* entities.
• Re-profile the Home view after at least one family member has moved during the candidate history window.
• Trial a bounded history window starting at 1 hour, not 24 hours.
• Keep current-position-only maps if recorder churn or browser rendering regresses.
• Run dashboard validation, the full Home Assistant configuration check, and targeted UI smoke tests before considering this resolved.