Please describe the idea
Hi, first of all — this card is absolutely fantastic. The level of customization, the date picker with group sync, and the primary_state_as option together make this one of the most useful cards in my Home Assistant setup. Thank you for the incredible work!
I built a "Records" card using primary_state_as: min/max with show_graph: false that displays key weather extremes from my Ecowitt GW3000A weather station — coldest temperature, warmest temperature, strongest wind gust, peak solar radiation, and rainiest day — all synced via date_picker_group so they update automatically when switching between week/month/year views.
It works beautifully, but there's one thing that would make it truly complete: knowing when the record occurred.
Feature request: When using primary_state_as: min or max, add a per-entity show_timestamp: true option that displays the timestamp of when that extreme value was recorded — shown after the value on the same line.
Example of what it could look like:
Coldest -21.9 °C Jan 14, 03:42
Warmest 10.2 °C Apr 15, 14:18
Strongest gust 17.0 m/s Mar 3, 11:55
Configuration example:
entities:
- entity: sensor.outdoor_temperature
name: Coldest
primary_state_as: min
show_timestamp: true
This would transform the card from "what was the record" to "what was the record and when did it happen" — which is exactly the kind of insight weather enthusiasts are looking for.
Thanks again for maintaining and improving this gem! 🙏
Please describe the idea
Hi, first of all — this card is absolutely fantastic. The level of customization, the date picker with group sync, and the primary_state_as option together make this one of the most useful cards in my Home Assistant setup. Thank you for the incredible work!
I built a "Records" card using primary_state_as: min/max with show_graph: false that displays key weather extremes from my Ecowitt GW3000A weather station — coldest temperature, warmest temperature, strongest wind gust, peak solar radiation, and rainiest day — all synced via date_picker_group so they update automatically when switching between week/month/year views.
It works beautifully, but there's one thing that would make it truly complete: knowing when the record occurred.
Feature request: When using primary_state_as: min or max, add a per-entity show_timestamp: true option that displays the timestamp of when that extreme value was recorded — shown after the value on the same line.
Example of what it could look like:
Configuration example:
This would transform the card from "what was the record" to "what was the record and when did it happen" — which is exactly the kind of insight weather enthusiasts are looking for.
Thanks again for maintaining and improving this gem! 🙏