I guess I’m going to have to update soon.
No 'version' key in the manifest file for custom integration 'bom'. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of 'bom'
No 'version' key in the manifest file for custom integration 'bom_forecast'. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of 'bom_forecast'
I added the manifest version a few days ago and released a new version. Didn’t think about the old bom one but I’ll fix that tomorrow… It’s just 1 line in the manifest file.
Thanks David, I appreciate it.
I mean I am going to have to update to the new version some time. It’s just that I have 5 monitored sites, countless derived sensors and automations that all have to be checked. I reckon there’s at least 3 hours work in changing. Trying to put it off until I get home.
Both the old BOM replacement component and bom forecast component have the version required for 2021.3.x HA. Should be able to update both via HACS or simply copy the manifest.json file from the repo.
Hi David - great work on the card!
I am struggling a little with configure. I have the card displaying (mostly) but missing a number of entities. I have noticed the problem ones are BOM ones like:
entity_daytime_high: sensor.bom_today_max
entity_daytime_low: sensor.bom_today_min
I am using the BOM Weather integration and these entities do not appear to come across.
What am I missing?
Thanks for any help that you can provide.
Cheers
Jamie
You need to follow the instructions and create the template sensors as per the docs
Thanks - got it now. Did not read down far enough. Thanks for the quick response.
Just a heads up… if you are still using the core BOM component I forked I believe it stopped working a few days ago so time to migrate to Brendans new custom component.
I also released a new 0.88c a few days ago to correct a night icon. If you are using the hybrid icons make sure you download the new icons and card. See info.md in the repo or the info shown in HACS.
Hi @DavidFW1960 I only recently updated to your version post the breaking change (I know, I was holding out a long time) but now can’t seem to see where my issue is. The card doesn’t display at all (no error, just no card). Perhaps a second set of eyes will help.
type: 'custom:bom-weather-card'
title: BOM Weather
entity_current_conditions: sensor.morley_icon_descriptor_0
entity_temperature: sensor.perth_temp
entity_forecast_high_temp_1: sensor.morley_temp_max_1
entity_forecast_high_temp_2: sensor.morley_temp_max_2
entity_forecast_high_temp_3: sensor.morley_temp_max_3
entity_forecast_high_temp_4: sensor.morley_temp_max_4
entity_forecast_high_temp_5: sensor.morley_temp_max_5
entity_forecast_icon_1: sensor.morley_icon_descriptor_1
entity_forecast_icon_2: sensor.morley_icon_descriptor_2
entity_forecast_icon_3: sensor.morley_icon_desciptor_3
entity_forecast_icon_4: sensor.morley_icon_desciptor_4
entity_forecast_icon_5: sensor.morley_icon_desciptor_5
entity_forecast_low_temp_1: sensor.morley_temp_min_1
entity_forecast_low_temp_2: sensor.morley_temp_min_2
entity_forecast_low_temp_3: sensor.morley_temp_min_3
entity_forecast_low_temp_4: sensor.morley_temp_min_4
entity_forecast_low_temp_5: sensor.morley_temp_min_5
entity_summary_1: sensor.morley_short_text_1
entity_summary_2: sensor.morley_short_text_2
entity_summary_3: sensor.morley_short_text_3
entity_summary_4: sensor.morley_short_text_4
entity_summary_5: sensor.morley_short_text_5
entity_sun: sun.sun
entity_daytime_high: sensor.morley_max_0
entity_daytime_low: sensor.morley_min_0
entity_wind_bearing: sensor.perth_wind_direction
entity_wind_speed: sensor.perth_wind_speed_kilometre
entity_wind_gust: sensor.perth_gust_speed_kilometre
entity_humidity: sensor.perth_humidity
entity_apparent_temp: sensor.perth_temp_feels_like
entity_daily_summary: sensor.morley_extended_text_0
entity_pop: sensor.morley_rain_chance_0
entity_pop_intensity: sensor.perth_rain_since_9am
entity_possible_today: sensor.morley_rain_amount_range_0
entity_pos_1: sensor.morley_rain_amount_range_1
entity_pos_2: sensor.morley_rain_amount_range_2
entity_pos_3: sensor.morley_rain_amount_range_3
entity_pos_4: sensor.morley_rain_amount_range_4
entity_pos_5: sensor.morley_rain_amount_range_5
entity_pop_1: sensor.morley_rain_chance_1
entity_pop_2: sensor.morley_rain_chance_2
entity_pop_3: sensor.morley_rain_chance_3
entity_pop_4: sensor.morley_rain_chance_4
entity_pop_5: sensor.morley_rain_chance_5
entity_fire_danger_summary: sensor.morley_fire_danger_0
large_icon_left_position: 0px
large_icon_top_margin: '-3.2em'
locale: en
old_daily_format: false
refresh_interval: 60
separator_top_margin: 6em
show_beaufort: false
show_decimals: false
show_separator: false
slot_l1: daytime_high
slot_l2: daytime_low
slot_l3: wind
slot_l4: pressure
slot_l5: sun_next
slot_r1: pop
slot_r2: humidity
slot_r3: uv_alert
slot_r4: fire_danger
slot_r5: sun_following
static_icons: false
summary_font_size: 0.8em
summary_top_padding: 2em
sunset: true
temp_font_size: 4em
temp_font_weight: 300
temp_right_pos: 0.85em
temp_top_margin: 0px
temp_uom_right_margin: 7px
temp_uom_top_margin: '-12px'
time_format: 24
tooltip_bg_color: 'rgb( 75,155,239)'
tooltip_border_color: 'rgb(255,161,0)'
tooltip_border_width: 1
tooltip_caret_size: 5
tooltip_fg_color: '#fff'
tooltip_left_offset: -12
tooltip_width: 110
tooltips: true
Check the entities all exist. Probably you didn’t add the template sensors. The ONLY reason the card won’t display is that you are parsing through a non existent entity.
hmm. I don’t have template sensors set up but those three entities that require templates (entity_current_text: sensor.bom_current_text, entity_uv_alert: sensor.bom_uv_alert, entity_fire_danger: sensor.bom_fire_danger) aren’t used in my card
I repeat… the ONLY reason is you are parsing a sensor that doesn’t exist. Check the slots have existing defined sensors too.
Something is missing. That is the only reason.
Well that took the better part of a day but I think I have all my sensors and automations transferred over to the new BoM integration.
Any progress on pressure and dew point?
Also I was unable to add observations for the Australian Antarctic stations. I used to be able to get these obs. It was quite useful for my job. I have opened an issue but suspect that only Australian continental stations are available on this new service.
I saw the issue Tom…
I use my own BME280 for pressure and I use that custom dew_point integration for the other. Seems the best solution to me.
Did you get it working Dave? If not, post the yaml code you are using to configure templates (or weather.yaml if you use that)
How do I stop this sensor:
- platform: statistics
name: today_temp_bom
sampling_size: 150
entity_id: sensor.hobart_temp
max_age:
hours: 24
From generating this error at start-up?
Logger: homeassistant.components.statistics.sensor
Source: components/statistics/sensor.py:159
Integration: statistics (documentation, issues)
First occurred: 19:42:36 (1 occurrences)
Last logged: 19:42:36
sensor.today_temp_bom: parsing error, expected number and received None
The sensor sensor.hobart_temp comes from the BoM integration and is available shortly after start-up.
Statistics is a core integration… I haven’t seen that error but I use Average… I assume you checked the docs for changes?
I assume it’s this new error trapping. It looks like home assistant generates the error before all the integrations have finished starting. I’ll post it in the release notes topic.
It’s weird though because it should restore the previous state shouldn’t it?
I dont know.