@DavidFW1960 have you seen this before?
It shows up as (null) on the card 
Never seen null direction
Yeah, weird. Only was one reading and it was missing in both the api data and the ftp data, so I guess they had a sensor problem.
1 Like
@curtis-r not everything, but I combined forecast sensors from this integration with my real-time sensors, so I can compare forecasted temperature, wind, rain, … with real one values.
@theRat hmmm, potential timezone issue make sense to me, will wait if someone fix it.
As part of the ongoing work for the platinum-weather-card I have been looking at the icons that are being used. Not blaming anyone as most where just inherited from previous iterations of the card(s).
The next release of the card will be removing the old/hybrid/new option as it really adds no value. The card will retain the option for animated/static.
A major part of this has involved me updating and standardizing a bunch of icons. The long term goal is that you will be able to map any text condition to any available icon.
Still a work in progress, but the new icons can be found in a new repo.
There are still a few conditions that I think are missing. I am also not great at graphical design. So if there are conditions you feel are missing and/or you want to help make them better, please create an issue on the repo.
1 Like
These icons look great! Thank you so much for all your hard work on this weather card. I am so glad that it has been given new (and much better) life instead of becoming extinct. The customization has made it possible to have two cards side by side with my weather provider and my backyard weather station, which I really like. Kudos on a job well done! 
Thanks for all the hard work thats gone into this! such an amazing card and so easy to setup
I have noticed that when i create a new view and add some cards to it they are all in one column? normally 2 separate cards would sit side by side?
If i add another card below the 2 in the config below it will be in the first column too, but if i move it up between them they split to 2 columns.
Im guessing there is some card height that needs to be set or something?
- theme: Backend-selected
title: WeatherForecast
path: weatherforecast
badges: []
cards:
- card_config_version: 4
entity_apparent_temp: sensor.today_temp_bom
entity_current_conditions: sensor.doubleview_icon_descriptor_0
entity_current_text: sensor.doubleview_short_text_0
entity_daily_summary: sensor.doubleview_extended_text_0
entity_fire_danger_summary: sensor.doubleview_fire_danger_0
entity_forecast_max: sensor.bom_today_max
entity_forecast_min: sensor.bom_today_min
entity_humidity: sensor.swanbourne_humidity
entity_pop: sensor.doubleview_rain_chance_0
entity_possible_today: sensor.doubleview_rain_amount_range_0
entity_pressure: sensor.makerpower_mppt_outside_pressure
entity_sun: sun.sun
entity_temperature: sensor.makerpower_mppt_outside_temperature
entity_todays_fire_danger: sensor.bom_fire_danger
entity_todays_uv_forecast: sensor.bom_uv_alert
entity_uv_alert_summary: sensor.doubleview_uv_category_0
entity_wind_bearing: sensor.swanbourne_wind_direction
entity_wind_gust: sensor.swanbourne_gust_speed_kilometre
entity_wind_speed: sensor.swanbourne_wind_speed_kilometre
option_time_format: system
section_order:
- title
- overview
- extended
- slots
- daily_forecast
show_section_daily_forecast: false
show_section_title: true
slot_l1: forecast_max
slot_l2: forecast_min
slot_l3: wind
slot_l4: pressure
slot_l5: sun_next
slot_l6: remove
slot_l7: remove
slot_l8: remove
slot_r1: popforecast
slot_r2: humidity
slot_r3: uv_summary
slot_r4: fire_summary
slot_r5: sun_following
slot_r6: remove
slot_r7: remove
slot_r8: remove
text_card_title: Perth Weather
type: custom:platinum-weather-card
- card_config_version: 4
daily_extended_forecast_days: 7
daily_extended_use_attr: false
daily_forecast_days: 5
daily_forecast_layout: vertical
entity_extended_1: sensor.doubleview_extended_text_1
entity_forecast_high_temp_1: sensor.doubleview_temp_max_1
entity_forecast_icon_1: sensor.doubleview_icon_descriptor_1
entity_forecast_low_temp_1: sensor.doubleview_temp_min_1
entity_pop_1: sensor.doubleview_rain_chance_1
entity_pos_1: sensor.doubleview_rain_amount_range_1
entity_summary_1: sensor.doubleview_short_text_1
option_daily_show_extended: true
section_order:
- title
- overview
- extended
- slots
- daily_forecast
show_section_extended: false
show_section_overview: false
show_section_slots: false
text_card_title: Forecast
type: custom:platinum-weather-card
- type: vertical-stack
cards:
- type: custom:bom-radar-card
frame_count: 30
center_latitude: -31.8998
center_longitude: 115.7811
marker_latitude: -31.8998
marker_longitude: 115.7811
show_marker: true
show_range: true
show_zoom: true
show_recenter: true
show_playback: true
zoom_level: 10
map_style: Satellite
show_radar_location: true
show_radar_coverage: true
As you have guessed setting the card height correctly for this card is not easy (and I haven’t completed it quite yet). It’s on the todo list.
And the sensor for observation time? is that a template from the current temperature sensor attribute?
If you are talking about the timestamp in the title section, then it is any entity that has a valid timestamp as its state. The BoM integration doesn’t create that so you probably need to pull it from an attribute somewhere using a template sensor. This is the time format.
I created this one which pulls the observation time from the current temperature sensor from the BOM integration, it works well enough for now… perhaps we could be able to select an attribute for that field in the future? similar to the way you can select an attribute on an entity card
- platform: template
sensors:
bom_observation_time:
value_template: >
{{ as_datetime(state_attr('sensor.swanbourne_temp', 'observation_time')) }}
Just a quick heads up to anyone following this thread.
No exact timeline but sometime in the next week I am aiming at a new release. The main points are:
- Some config bug fixes (addressing issues that threw exceptions when setting up a new card or configuring a non-existent entity)
- If you configure an entity for the main condition icon, when it provides an unknown state, the text value is now shown under the icon
- A huge rework of the weather icons (and deprecating the old/new/hybrid options). The icons have been reworked to have a consistent theme that works well with the card. We will continue to support the static/animated version of the icons.
Feedback welcome as always.
5 Likes
I have just done a pre-release (0.0.4b0). It is just some bug fixes as well as completing the code to calculate the card size correctly.
@chris.huitema are you able to check the card size stuff? I have left the debug output that prints the card height in px and the card size being returned.
1 Like
Looks good to me… works as expected now, and seems to be dynamic with the number of days in a vertical forecast layout.
Thanks very much
It can only be dynamic based off the config (ie. I can’t use data that changes to get it right). It goes through the config and adds up the number of px for each part of the card. For elements that have a variable height (extended forecast text) I just have to guess the number of lines and hope it averages out.
I am thinking about adding a config option to allow people to override the card size (might be needed by people that do crazy stuff with card mod).
A new pre-release version (1.1.14b0) of the BoM integration is now available on HACS. The main improvement is that you can now reconfigure the integration (no more deleting and re-adding to adjust the settings). Many thanks to @Djelibeybi for this contribution!
Let us know if there are issues. If all seems ok I’ll do a proper release on the weekend.
It also creates one or more devices to which each of the weather and sensor entities are connected which makes it a lot easier to put them all in an area.
3 Likes
If anyone has already tried 1.1.14b0, it will probably fail. Just redownload as I fixed it a few minutes ago. I had a fat finger problem
Nice work Avi!
1 Like
Aw, thanks. You’re welcome!