You know that moment when your weather app cheerfully says "sunny" and your soaking wet laundry on the line strongly disagrees? I built a Lovelace card for that.
It puts what your weather station actually measured over the past few days right next to what the forecast says is coming, on one chart. Today is the column where the two halves meet — convenient for "did the forecast lie to me again?" research.
Got a weather station? Past comes from your sensors. The forecast is graded.
No weather station, just a weather.* entity? A toggle pulls past data from Open-Meteo so you still get the side-by-side view.
Sensors but no forecast? Also fine. Just your data, no fortune-telling.
On top sits a live "now" panel — temperature, condition icon, clock — driven directly by your sensors, so it doesn't quietly disagree with the chart underneath it.
Installation is via HACS as a custom repository. Setup is mostly pointing the card at your sensors and pressing save; the README has the full reference for the day you want to make it complicated.
Feedback, bug reports and translations very welcome — easier to wrangle in GitHub Issues or Discussions than buried in this thread.
Big thanks to @mlamberts78, whose weather-chart-card is the upstream this forked from. None of this would exist without that chart layout.
Thanks for the detailed report and screenshots, @chairstacker — that was exactly the right catch.
You were seeing it correctly: with Round temperatures turned off, the card was just showing whatever precision the weather data happened to have, so
the daily/today views showed one decimal while the hourly view looked rounded to whole numbers. That inconsistency is fixed in v2.1.1: Release v2.1.1 · chriguschneider/weather-station-card · GitHub
Now, with Round temperatures off, every temperature — daily, today and hourly — shows exactly one decimal place (e.g. 28.0°). With it on, you still
get whole numbers everywhere, same as before. Nothing to change in your YAML; just update via HACS and hard-reload.
Thanks for both posts, this one slipped past us until you reported it.
The one-click install button was handing HACS the wrong category, which caused that pop-up. Adding the repo manually, like you did, was the right workaround. It's fixed now, so the button works without the error.
Very interesting Card!
Before find this, I used the Weather Chart Card from @mlamberts78, in association with a weather template.
The Weather Template combine the data from Met.No for the forecasts and from my Meteobridge for the local data.
The ability to show past data from the local weather station is very kind.
Thanks for the screenshot — that made it easy to spot. Good news: the icon isn't broken or failing to load. A circle with an exclamation mark is actually the card's "severe weather" symbol, and the card was wrongly deciding that you were having a storm.
Here's why: to pick a weather symbol, the card looks at your wind. Internally it expects wind in metres per second, but your station reports in km/h. The card wasn't converting between the two, so a perfectly normal breeze of ~31 km/h was read as if it were 31 m/s — that's hurricane-force — and it put the severe-weather symbol on the current conditions and on every past day. Your future days looked fine because those icons come straight from your weather integration, which the card doesn't re-evaluate.
The same issue also affected °F temperatures (snow could show as rain) and rainfall measured in inches, so I fixed all three at once.
@PecosKidd Turns out hard-coding "mm" was a bold assumption about how the world measures rain. Fixed in v2.1.3 — inch sensors now read in / in/h on their own, and Units → "Convert precipitation to" lets you force either. Thanks for catching my metric tunnel vision. Update via HACS.
