Would using the :first-child pseudoclass not work? Furthermore, the hide_current_location parameter in the card’s options will show the current location of the selected entity.
Hey @konewka17 — been using the card daily since you released it, great work.
Small contribution from my side for anyone who wants history beyond the recorder window (the card reads from the recorder, which purges after purge_keep_days): I built GPS Timeline, a companion integration that archives every GPS fix into its own SQLite file in the HA config folder — kept until you explicitly delete it.
It serves the same history API the card uses, so I proposed adding an opt-in history_source option to the card in a PR. As suggested, I’m keeping that as a small fork for now: everything else is identical to the upstream card, the option is opt-in, and the original card works exactly as before.
- Integration: GitHub - iamyacin/gps-timeline: GPS history timeline Integration for Home Assistant · GitHub
- Card fork (adds the opt-in history source): GitHub - iamyacin/timeline_card · GitHub
Backfill service imports your existing recorder window at install so the timeline starts with no gap. Works with tracker and Places queries alike.
1 Like
Thanks for the contribution @iamyacin, I will be following the adoption of GPS Timeline and when the integration gains enough traction, we can consider to integrate the usage of this into the main card later on
1 Like