Customising the BOM Weather and lovelace - now in HACS

Which was the breaking change? Mine has disappeared from my dashboard now :crazy_face:

itā€™s in the info.md file that was displayed when you updated. Did you make any changes for v1.00 or did you go straight to v1.01? I canā€™t imagine any change causing the card to not load. Can you show the card config? also reset cacheā€¦

Same cofig used, nothing changed. I did a reset of the cache. Config below:

type: custom:bom-weather-card
title: BOM Weather
entity_current_conditions: sensor.sylvania_icon_descriptor_0
entity_temperature: sensor.sydney_airport_temp
entity_forecast_high_temp_1: sensor.sylvania_temp_max_1
entity_forecast_high_temp_2: sensor.sylvania_temp_max_2
entity_forecast_high_temp_3: sensor.sylvania_temp_max_3
entity_forecast_high_temp_4: sensor.sylvania_temp_max_4
entity_forecast_high_temp_5: sensor.sylvania_temp_max_5
entity_forecast_icon_1: sensor.sylvania_icon_descriptor_1
entity_forecast_icon_2: sensor.sylvania_icon_descriptor_2
entity_forecast_icon_3: sensor.sylvania_icon_descriptor_3
entity_forecast_icon_4: sensor.sylvania_icon_descriptor_4
entity_forecast_icon_5: sensor.sylvania_icon_descriptor_5
entity_forecast_low_temp_1: sensor.sylvania_temp_min_1
entity_forecast_low_temp_2: sensor.sylvania_temp_min_2
entity_forecast_low_temp_3: sensor.sylvania_temp_min_3
entity_forecast_low_temp_4: sensor.sylvania_temp_min_4
entity_forecast_low_temp_5: sensor.sylvania_temp_min_5
entity_summary_1: sensor.sylvania_short_text_1
entity_summary_2: sensor.sylvania_short_text_2
entity_summary_3: sensor.sylvania_short_text_3
entity_summary_4: sensor.sylvania_short_text_4
entity_summary_5: sensor.sylvania_short_text_5
entity_apparent_temp: sensor.sydney_airport_temp_feels_like
entity_daily_summary: sensor.sylvania_extended_text_0
entity_pop: sensor.sylvania_rain_chance_0
entity_pop_intensity: sensor.sydney_airport_rain_since_9am
entity_possible_today: sensor.sylvania_rain_amount_range_0
entity_pos_1: sensor.sylvania_rain_amount_range_1
entity_pos_2: sensor.sylvania_rain_amount_range_2
entity_pos_3: sensor.sylvania_rain_amount_range_3
entity_pos_4: sensor.sylvania_rain_amount_range_4
entity_pos_5: sensor.sylvania_rain_amount_range_5
entity_pop_1: sensor.sylvania_rain_chance_1
entity_pop_2: sensor.sylvania_rain_chance_2
entity_pop_3: sensor.sylvania_rain_chance_3
entity_pop_4: sensor.sylvania_rain_chance_4
entity_pop_5: sensor.sylvania_rain_chance_5
entity_uv_alert_summary: sensor.sylvania_uv_category_0
entity_humidity: sensor.sydney_airport_humidity
entity_wind_bearing: sensor.sydney_airport_wind_direction
entity_wind_speed: sensor.sydney_airport_wind_speed_kilometre
entity_wind_gust: sensor.sydney_airport_gust_speed_kilometre
entity_daytime_high: sensor.bom_today_max
entity_daytime_low: sensor.bom_today_min
entity_sun: sun.sun
card_mod:
  style: |
    ha-card {
      background-color: var(--primary-background-color);
      background: rgb(0, 49, 83, 0.4);
      box-shadow: none;
      }
columns: 1

I wonder if the card-mod stuff at the bottom is conflicting with the new layout? Can you try deleting that. Also as always check all your sensors are existing and have values in dev-tools

Yeah tried without card-mod stuff, but no good. Will go thru the sensors now :slight_smile:

1 Like

It is because you are using default slot values. Slot_l4 displays pressure, but you have no pressure sensor defined.

He says he didnt change the config though.

All sensors appear to be working. Tried on a fresh dashboard too and no goodā€¦

There is a fix coming, but for now you can probably add a line to your config

slot_l4: remove
1 Like

So seems new we pull the UoM from the entity if there is no entity it cracks the shits

1 Like

Boom that worked, thanks legends

The next pre-release will fix the problem and you will be able to remove that line from your config.

1 Like

Do we need the (broken) average sensor and templates now that we have this?

As @DavidFW1960 said. For us using the BoM integration all of the values are provided in the data and its slots adjust during the day. For example right now my card shows:
image
Shortly after 9am it will change to display Max and Overnight Min. Basically it works the same way the BoM app does.

Now it is a bit after 9am and it changes to this:
image

1 Like

What is your slot configuration for that Simon?

This is the relevant part:

entity_temp_next: sensor.pearce_now_temp_now
entity_temp_next_label: sensor.pearce_now_now_label
entity_temp_following: sensor.pearce_now_temp_later
entity_temp_following_label: sensor.pearce_now_later_label
slot_l5: temp_next
slot_r5: temp_following

Clearly you need to update the sensor names to match your sensors.

1 Like

In case youā€™re interested I fixed Brave by using a state switch card with media query to use one card for desktop screens with the new css I showed you yesterday but for mobiles/smaller screens it uses the normal settings.

I donā€™t have any temp_now or temp_later sensors. The integration is up to date (1.1.2).

you need to delete it and readd it to get the new sensors

Ugh. Really?