New release is out! v0.7.0 is available through HACS and Github releases. Few things available in this release:
Cardinal wind bearing
Since some integrations report wind bearing using cardinal directions (e.g., N, E, S, W) instead of numeric degrees, the card now includes full support for these values. The card will automatically interpret these strings to display the correct wind direction indicator.
Temperature Precision
As it isn’t always easy to control temperature precision in weather entities (without creating a weather template), this release adds the ability to set temperature precision for current weather and forecasts separately. This allows more flexibility with weather integrations that report values with varying precision, or simply gives you more granular control over the UI.
Note that In simple forecast mode, precision settings will not have an effect because the layout width is limited. In this mode, precision is always fixed to 0.
Secondary Info Attributes
You can now define which attribute is displayed in the current weather’s secondary info area, below the current temperature.
By default, aligned with the built-in weather forecast, the card attempts to display:
Temperature extrema (if available)
Precipitation (if available)
Humidity
If you wish, you can now manually specify any available weather attribute to be displayed in this space.
Bug Fix: Bubble Card Compatibility
Thanks to @Mordano’s contributions, we have fixed an issue with forecast rendering when the card is used inside a Bubble Card popup. The card should now consistently render the forecast section!
Hi Troinine, thanks very much for the update. I also second the request to increase the font size. I also have a bug. The time is normally displayed in 10, 12, 14 etc. but as you can see from the screenshot, for some reason “16” is displayed as “16.32”?
This is not a bug. By default the card has configuration property use_sun_times set to true. This will show sunset and sunrise times in the hourly forecast in format hh:mm. You can disable suntimes using the card editor or in your YAML configuration.
This release brings improved internationalization support and more flexibility for customizing current weather attributes. A big thank you to everyone who reported issues and provided feedback!
Localized Time Formats
The card now properly supports localized time formats with suffixes, addressing a long-requested feature from users in different regions.
For users with 12-hour clock settings, the forecast now displays times in a clean two-row layout:
Hourly forecast: Hour on the first row, AM/PM on the second (e.g., “9” / “AM”)
Daily forecast: Weekday on the first row, day of month on the second (e.g., “Mon” / “15”)
For users with locale specific suffixes (such as Uhr, etc.), the hourly forecast now correctly formats the time with 24-hour clock settings when in use.
For users with 24-hour clock settings, the display remains unchanged with a single-row layout.
Custom Entities for Current Weather
You can now use custom sensor entities to override any current weather attribute. This is particularly useful when:
Your weather integration doesn’t provide certain attributes
You have more accurate local sensors for specific measurements
You want to mix data from multiple sources
Simply specify the entity ID for any attribute you want to override, and the card will use that sensor’s value instead of the weather entity’s attribute.
Scrolling Fix
Fixed an issue where the forecast component could interfere with vertical scrolling of the Home Assistant dashboard, particularly noticeable on mobile devices.
Excellent weather card, thank you!
The US National Weather Service uses a twice daily setup instead of daily one with maximum/minimum temperatures. It therefore gives me an error if I use it in your card. Would it be possible to adapt?
I’m using OpenWeatherMap and everything is fine, but that’s a good point - is there a list of weather services that this card would be compatible with? Or, maybe any weather services following HA weather format should be fine?
@troinine - good card indeed! And I appreciate the constant improvements.
Also does this card have any minimum browser requirement? I am guessing the card is not likely going to work on older Safari on iPhones 4 or iPad 2, or WebView versions that are too old, but how old is old? I’m asking because people use this on dashboards, and the many of those hardware running dashboards might not be modern enough.
Excellent weather card, thank you!
The US National Weather Service uses a twice daily setup instead of daily one with maximum/minimum temperatures. It therefore gives me an error if I use it in your card. Would it be possible to adapt?
As I personally don’t have, or use twice daily weather services, I didn’t consider this a high priority. However, it surely can be added to the card. Mind if I ask you to provide your weather entity details and weather forecasts from the Developer Tools? I would need
State (including all weather entity attributes)
The results of action: weather.get_forecasts for types daily, twice_daily and hourly
This would help to mock the data and test the feature.
The card supports most weather integrations, provided they offer daily and/or hourly forecasts. If an integration only provides twice_daily data, it won’t work quite yet though I’m planning to add support for that soon if someone can hook me up with some test data.
Regarding browser support: the card relies on specific CSS features that older browsers don’t support, which is likely to cause rendering issues. Trying to support “legacy” browsers would add a lot of complexity to the code. My best advice is to use the most up-to-date version possible, or at least a browser still actively supported by your device vendor.
Thanks, awesome!! Here’s the gloom that I’m experiencing over the next week.
A bonus feature could be a dewpoint line, but really don’t want to ask too much here
weather state:
temperature: 9
temperature_unit: °F
humidity: 78
pressure: 30.26
pressure_unit: inHg
wind_bearing: 220
wind_speed: 5.75
wind_speed_unit: mph
visibility: 10
visibility_unit: mi
precipitation_unit: in
attribution: Data from National Weather Service/NOAA
friendly_name: kcle
supported_features: 6
v0.9.0 is out! I’m trying something different in this release. Let’s see if it is a hit or a miss. I personally enjoy it quite much so here goes:
Release Highlights
This release introduces an interactive chart attribute selector! You can now dynamically switch between different weather data visualizations directly from the chart, making it easier than ever to explore your weather data.
Hope you will enjoy it!
Interactive Chart Attribute Selector
The chart mode now supports interactive attribute selection, allowing you to switch between different weather data visualizations on the fly. No more multiple cards to visualize your weather data!
Available visualizations:
Temperature & Precipitation - The classic view showing temperature curves and precipitation bars
Apparent Temperature - See how the weather actually feels
Humidity - Track relative humidity trends
Pressure - Monitor atmospheric pressure changes
UV Index - Plan your outdoor activities with UV forecasts
Two ways to access the selector:
Hold action - Press and hold anywhere on the chart to open the attribute dropdown (works by default)
Settings icon - Enable show_attribute_selector: true to display a quick-access settings icon in the chart’s top-right corner
The selector intelligently shows only the attributes available from your weather integration, so you’ll never see options for data that isn’t available. You can also set the default chart attribute using default_chart_attribute card configuration property.
And of course, configuration is also available in the card editor!
I’m close on releasing 1.0.0. But few items would need to be tested so I decided to make a pre-release. You can download it via HACS by re-downloading the card and selecting a different version. Here are some of the changes in this pre-release:
Pre-release highlights
We’re closing in on v1.0.0! This pre-release adds the last critical features missing from the card. After a testing period, if no issues are
discovered, the final v1.0.0 release will follow.
Thanks to everyone for reporting issues and helping test the card. You are awesome!
Support for twice-daily weather integrations
This pre-release adds support for weather entities that provide twice_daily forecasts instead of daily. If both are available, daily is still
preferred. This brings the card on par with most weather integrations and the built-in weather forecast card.
Note that the layout for twice_daily forecasts differs slightly from daily in terms of header items. This ensures vertical spacing remains consistent
across both forecast modes.
Better support for single forecast type integrations
The card can now render weather entities that only provide a single forecast type, such as daily. In these cases, toggling between forecasts is
disabled since only one is available. The card automatically selects whichever forecast type the entity provides.
Configuration refactoring
temperature_entity has been moved to the current object. Don’t worry, the old configuration still works and will be automatically migrated when you
edit the card with the card editor.
First production-ready release is out! You can download or update it in HACS.
Release highlights
This marks a few months of active development on this card and it has been an interesting learning path towards creating a custom card for Home Assistant. Most of the active issues have now been resolved and the feature set covers a wide range of use cases.
Many thanks to everyone who have reported issues and helped to test the card. You are awesome! I’ll personally take a break from this card in order to focus on other projects. However, I try my best to fix any critical issues that may arise.
Hope you will enjoy this card for a long time! Here is a recap what changes there are compared to v0.9.0.
Support for twice-daily weather integrations
This release adds support for weather entities that provide twice_daily forecasts instead of daily. If both are available, daily is still
preferred. This brings the card on par with most weather integrations and the built-in weather forecast card.
Note that the layout for twice_daily forecasts differs slightly from daily in terms of header items. This ensures vertical spacing remains consistent
across both forecast modes.
Better support for single forecast type integrations
The card can now render weather entities that only provide a single forecast type, such as daily. In these cases, toggling between forecasts is
disabled since only one is available. The card automatically selects whichever forecast type the entity provides.
Configuration refactoring
temperature_entity has been moved to the current object. Don’t worry, the old configuration still works and will be automatically migrated when you
edit the card with the card editor. In addition, scroll_to_selected and use_color_thresholds have been set to true by default as these provide functionality relevant for most users.
Font size styling
Font size styling is now better explained in the README.md. In addition, you can now control the size of label sizes when using chart mode.