davidfw1960 / bom-weather-card Goto Github PK

Good morning,

I have updated the BOM Weather Card via HACS to 0.89a this morning, but it seems the card still is not working for me.
I have logged this as a query rather than a fault as I am sure the issue could be my end.

I had the card working perfectly in HA 2021.5.x, but I still cannot get the card to display in 2021.6.x

Steps taken so far:
Updated card via HACS.
Updated HA to 2021.6.2
Checked Beta versions in HACS (same, 0.89a)
Restarted HA again.
Uninstalled BOM Weather Card via HACS
Reinstalled BOM Weather Card via HACS

Any tips would be appreciated. I am sure there must be something simple I am missing.
Thanks

Since HA 0.118 the format of numbers is according to the selected language, PR#7516.

It would be great if the numbers of the bom-weather-card would be formated the same way.

Hi David,

Firstly I love what your work and I am pretty new to Home Assistant so still learning, but am a programmer (just not good at Python yet).

I have the graphs set up, but they only update when I do a refresh. of the page. Is this a bug or something I have configured wrongly.

Also the data provided by the core bom sensor code for observations is not that great. They are using data that only updates every 30 minutes, but the bom actually provide data every 10 minutes. I have an mqqt server hosted on google that pulls all that data and publishes it. I have had a look at creating a bom-mqqt integration but I am really not sure where to start. If you interested flick me an email and I'll share some stuff privately. (simon at makin-thing.com)

Cheers
Simon

I migrated to your wonderful card as part of moving from Darksky to OpenWeatherMap. On desktop, it works perfectly, however, in the Android companion app, the card causes the page to become wider than the screen as shown in the images below (the page scrolls side to side instead of having chevrons on the top bar). I have tried both with my layout tweaks and with the default configuration and it makes no difference. Removing the card returns the page width to normal. I have skimmed the code looking for a culprit but I am no expert...

https://www.reddit.com/r/homeassistant/comments/drdzye/unable_to_create_icons_folder_in_configwww/

I'm having the same problem as the people In the link above. I can make a folder called 'new folder', but as soon as I try and rename to "icons" it won't let me. If I try to make the icons folder elsewhere, and then just copy it across, I get "could not find this item". I'm using the Samba share add-on

Edit: Thanks, removing the icon, and underscore wildcard lines from under 'veto_files:' did the trick.

Hi,

I've recently updated to 2021.6.1 and then 2021.6.2, and the weather card no longer works.

If I look in the system log I see the following error:

Logger: frontend.js.latest.202106030
Source: components/system_log/init.py:190
First occurred: 10:30:19 PM (5 occurrences)
Last logged: 10:31:56 PM

https://hass/local/custom_ui/bom-weather-card.js?v=0.1:891:13 TypeError: null is not an object (evaluating 'root.childElementCount')

Any suggestions welcome.

James

Love your work. One small issue I noted when I upgraded to v0.78 today. I received the following warning in the log file (BTW, it appears to work fine):

Log Details (WARNING)
Logger: hacs.repository.plugin.DavidFW1960.bom-weather-card
Source: custom_components/hacs/repositories/helpers/methods/installation.py:17
First occurred: 12:59:19 (1 occurrences)
Last logged: 12:59:19

'install' is deprecated, use 'async_install' instead

Hello! I updated to the latest 0.87b and started having issues with the forecast icons not rendering. I've narrowed down the problem to the way the Home Assistant URL has .replace("night", "day") called on it, which presents a problem if the base URL contains the sequence "night" in it, like mine does, causing the images to be retrieved from an invalid URL. I'm unfamiliar with this codebase so I'm unsure of the best way to solve this problem, but I'd suppose performing the replace on more specific parts of the URL where required, leaving the base URL unmodified would work?

Two icons missing - see screenshot below

I used the card from your lovelace.yaml and the sensors from template.md. Most things are working nicely except the max and min temp for the day. These seem to come from the following sensors which in turn use a state attr of a sensor I cannot find.

bom_today_max: value_template: > {{ state_attr('sensor.today_temp_bom', 'max_value') }}

bom_today_min: value_template: > {{ state_attr('sensor.today_temp_bom', 'min_value') }}

In browser console I have these errors when I go to view with bom-weather-card:

Uncaught (in promise) TypeError: Cannot set property 'textContent' of null
    at HTMLElement.updateValues (bom-weather-card.js:832)
    at HTMLElement.set hass [as hass] (bom-weather-card.js:787)
    at HTMLElement.value (hui-stack-card.ts:40)
    at layout-card.js:1
    at Array.forEach (<anonymous>)
    at HTMLElement.updated (layout-card.js:1)
    at HTMLElement.performUpdate (updating-element.ts:720)
    at HTMLElement._enqueueUpdate (updating-element.ts:653)

My configuration:

- id: climate
    icon: mdi:cloud
    title: "Klimat"
    path: climate
    panel: true
    cards:
      - type: custom:layout-card
        max_columns: 5
        cards:
          - type: vertical-stack
            cards:
              - type: custom:bom-weather-card
                entity_sun: sun.sun
                entity_daily_summary: sensor.dark_sky_daily_summary
                entity_current_conditions: sensor.dark_sky_icon
                entity_humidity: sensor.humidity_outdoor
                entity_pressure: sensor.pressure_outdoor
                entity_temperature: sensor.temperature_outdoor
                entity_apparent_temp: sensor.dark_sky_apparent_temperature
                entity_visibility: sensor.dark_sky_visibility
                entity_wind_bearing: sensor.dark_sky_wind_bearing
                entity_wind_speed: sensor.dark_sky_wind_speed
                entity_forecast_high_temp_1: sensor.dark_sky_daytime_high_temperature_1d
                entity_forecast_high_temp_2: sensor.dark_sky_daytime_high_temperature_2d
                entity_forecast_high_temp_3: sensor.dark_sky_daytime_high_temperature_3d
                entity_forecast_high_temp_4: sensor.dark_sky_daytime_high_temperature_4d
                entity_forecast_high_temp_5: sensor.dark_sky_daytime_high_temperature_5d
                entity_forecast_low_temp_1: sensor.dark_sky_overnight_low_temperature_1d
                entity_forecast_low_temp_2: sensor.dark_sky_overnight_low_temperature_2d
                entity_forecast_low_temp_3: sensor.dark_sky_overnight_low_temperature_3d
                entity_forecast_low_temp_4: sensor.dark_sky_overnight_low_temperature_4d
                entity_forecast_low_temp_5: sensor.dark_sky_overnight_low_temperature_5d
                entity_forecast_icon_1: sensor.dark_sky_icon_1d
                entity_forecast_icon_2: sensor.dark_sky_icon_2d
                entity_forecast_icon_3: sensor.dark_sky_icon_3d
                entity_forecast_icon_4: sensor.dark_sky_icon_4d
                entity_forecast_icon_5: sensor.dark_sky_icon_5d
                entity_summary_1: sensor.dark_sky_summary_1d
                entity_summary_2: sensor.dark_sky_summary_2d
                entity_summary_3: sensor.dark_sky_summary_3d
                entity_summary_4: sensor.dark_sky_summary_4d
                entity_summary_5: sensor.dark_sky_summary_5d
                entity_pop_1: sensor.dark_sky_precip_probability_1d
                entity_pop_2: sensor.dark_sky_precip_probability_2d
                entity_pop_3: sensor.dark_sky_precip_probability_3d
                entity_pop_4: sensor.dark_sky_precip_probability_4d
                entity_pop_5: sensor.dark_sky_precip_probability_5d
                time_format: 24
                locale: pl
                tooltips: true
                tooltip_width: 100
                tooltip_bg_color: "#FAFAFA"
                tooltip_fg_color: "#212121"
                tooltip_border_color: "#D9D9D9"
                tooltip_left_offset: -14
                slot_l1: "wind"
                slot_l2: "visibility"
                slot_l3: "sun_following"
                slot_l4: "remove"
                slot_l5: "remove"
                slot_r1: "humidity"
                slot_r2: "pressure"
                slot_r3: "sun_next"
                slot_r4: "remove"
                slot_r5: "remove"
                old_icon: "true"

I've stated getting this just recently:
Today's Low NaN °C

on my card using:
entity_daytime_low: sensor.bom_today_min

This is the one I use, the other is commented out. Not sure on the differences between the two, but both seem to give me the error.

      bom_today_min:
        value_template: >
          {%- if states('sensor.suburbname_temp_min_0') == 'n/a' -%} 
            {{ state_attr('sensor.today_temp_bom', 'min_value') }}
          {% else %}
            {{ states('sensor.suburbname_temp_min_0') }}
          {% endif %}

bom_today_min is "Unknown"

sensor.suburbname_temp_min_0 is "Unknown"

Is this just a problem with the BOM data?
Thanks

First off, Thanks. Nice work here. It looks amazing. Took me a while to get it working fully.

Issues I had was that an icon for entity_current_conditions would not display for a current state of 'storm'. I poked through the js and found it was looking for scattered thunderstorms icon which was missing from the weather_icons.zip. Found the icons on SouthernWolf95 additions and added them to the icons directory. This still didn't work until I had renamed the files to remove the uppercase and -Animated/-Static parts of the file name. For example -> 'Scattered-Thunderstorms - Animated.svg' changed to 'scattered-thunderstorms.svg. So really the issue is just the zip doesn't contain all the files which makes the install instructions a bit confusing.

Good morning,

I have updated the BOM Weather Card via HACS to 0.89a this morning, but it seems the card still is not working for me.
I have logged this as a query rather than a fault as I am sure the issue could be my end.

I had the card working perfectly in HA 2021.5.x, but I still cannot get the card to display in 2021.6.x

Steps taken so far:
Updated card via HACS.
Updated HA to 2021.6.2
Checked Beta versions in HACS (same, 0.89a)
Restarted HA again.
Uninstalled BOM Weather Card via HACS
Reinstalled BOM Weather Card via HACS

I checked Home Assistant log file and I see this error:

http://homeassistant:8123/hacsfiles/bom-weather-card/bom-weather-card.js:914:14 Uncaught TypeError: Cannot read property 'childElementCount' of null
11:10:23 AM - (ERROR) components/system_log/init.py

Any tips would be appreciated. I am sure there must be something simple I am missing.
Thanks

Hi David.
Given, today my card was reporting "Morning Fog", I noticed for the first time that this field was not displaying correctly. The 2 "g" characters are being cropped. Almost to the point where they look like a "q".
Which setting can I manipulate to give this field more depth. Perhaps it is the data below that is to tall and it is overlapping current_text. Not sure.

Thanks!

I'm not sure if I'm just being impatient, and this is just a bit of a glitch with the new way of retrieving the BOM information, or if I've done something wrong.

As an example:
entity_current_conditions: sensor.australiansuburbname_mdi_icon_0

which right now is supposed to display:
mdi:weather-sunny

I have a sunny.png in \config\www\bom_icons
and I've tried \config\www\icons\bom_icons

but nothing seems to be appearing. Any ideas, please?

Hi David - Firstly - brilliant piece of work!

Hello from a fellow Australian down here in Nowra. I got your weather card fully working but all my code is in the configuration.yaml file - I couldn't get it working by having the weather.yaml file in a packages folder. I kept getting an error "extra keys not allowed @ data['weather']" I'm clearly having some formatting/naming issues. I've carefully read and tried to research the issue but thought you might be able to offer a bit of guidance in your readme about how to correctly point to the file from your configuration.yaml file. Perhaps include a 'safe' copy of our own configuration.yaml (or a portion thereof).

Anyway thanks so much for a great visual treat on the HA platform.
Cheers
Simon

Home Assistant Version:

Version
core-2021.4.5
[latest]

Repro steps:

1. Navigate to 'Supervisor | Add-on Store'
2. Top right drop down menu (3 dots) | Repositories
3. Enter URL 'https://github.com/DavidFW1960/bom-weather-card' and click Add
4. Check system logs to see errors below

Error log:

21-04-17 06:31:46 INFO (MainThread) [supervisor.store.git] Cloning add-on https://github.com/DavidFW1960/bom-weather-card repository

21-04-17 06:31:48 ERROR (MainThread) [supervisor.store] https://github.com/DavidFW1960/bom-weather-card is not a valid add-on repository

21-04-17 06:31:48 INFO (MainThread) [supervisor.resolution.module] Create new issue IssueType.CORRUPT_REPOSITORY - ContextType.STORE / 8ee35b6c
21-04-17 06:31:48 INFO (MainThread) [supervisor.resolution.module] Create new suggestion SuggestionType.EXECUTE_REMOVE - ContextType.STORE / 8ee35b6c
21-04-17 06:31:48 WARNING (MainThread) [supervisor.store.data] No repository information exists at /data/addons/git/8ee35b6c
21-04-17 06:31:48 INFO (MainThread) [supervisor.store] Loading add-ons from store: 66 all - 0 new - 0 remove
21-04-17 06:31:48 INFO (MainThread) [supervisor.resolution.fixups.store_execute_remove] Remove invalid Store: 8ee35b6c
21-04-17 06:31:48 INFO (MainThread) [supervisor.store.git] Removing custom add-on repository https://github.com/DavidFW1960/bom-weather-card

Not sure if this warning is from this card, but figured it might be as my subrbname, the real one, was listed...

Source: helpers/template.py:1210
First occurred: 3:48:15 PM (27 occurrences)
Last logged: 3:48:36 PM

Template warning: 'timestamp_custom' got invalid input '00:00' when compiling template '{{ '00:00' | timestamp_custom('%H:%M') }}' but no default was specified. Currently 'timestamp_custom' will return '00:00', however this template will fail to render in Home Assistant core 2021.12
Template warning: 'float' got invalid input 'unknown' when rendering template '{%- if states('sensor.suburbname_wind_speed_kilometre') | float >= 118 -%} 12 {%- elif states('sensor.suburbname_wind_speed_kilometre') | float >= 103 -%} 11 {%- elif states('sensor.suburbname_wind_speed_kilometre') | float >= 89 -%} 10 {%- elif states('sensor.suburbname_wind_speed_kilometre') | float >= 75 -%} 9 {%- elif states('sensor.suburbname_wind_speed_kilometre') | float >= 62 -%} 8 {%- elif states('sensor.suburbname_wind_speed_kilometre') | float >= 50 -%} 7 {%- elif states('sensor.suburbname_wind_speed_kilometre') | float >= 39 -%} 6 {%- elif states('sensor.suburbname_wind_speed_kilometre') | float >= 29 -%} 5 {%- elif states('sensor.suburbname_wind_speed_kilometre') | float >= 20 -%} 4 {%- elif states('sensor.suburbname_wind_speed_kilometre') | float >= 12 -%} 3 {%- elif states('sensor.suburbname_wind_speed_kilometre') | float >= 6 -%} 2 {%- elif states('sensor.suburbname_wind_speed_kilometre') | float >= 2 -%} 1 {%- else -%} 0 {%- endif -%}' but no default was specified. Currently 'float' will return '0', however this template will fail to render in Home Assistant core 2021.12
Template warning: 'round' got invalid input 'unknown' when rendering template '{% if states('sensor.suburbname_temp_min_0') == 'unknown' %} {% set min = states('sensor.bom_today_min') %} {% else %} {% set min = states('sensor.suburbname_temp_min_0') %} {% endif %} {% if states('sensor.suburbname_temp_max_0') == 'unknown' %} {% set max = states('sensor.bom_today_max') %} {% else %} {% set max = states('sensor.suburbname_temp_max_0') %} {% endif %} {{ max|round(0)}}°/{{ min|round(0)}}°/{{states('sensor.suburbname_rain_chance_0')|round(0)}}%' but no default was specified. Currently 'round' will return 'unknown', however this template will fail to render in Home Assistant core 2021.12```

Anyone else find the same?

After updating to 0.86a (HA 2020.12.1), the card is not displayed and there are errors in the browser console:

Uncaught (in promise) TypeError: Cannot read property 'state' of undefined
    at HTMLElement.slotValue (bom-weather-card.js:124)
    at HTMLElement.getSlot (bom-weather-card.js:100)
    at HTMLElement.render (bom-weather-card.js:57)
    at HTMLElement.update (app.e45b0549.js:10297)
    at HTMLElement.performUpdate (app.e45b0549.js:10297)
    at HTMLElement._enqueueUpdate (app.e45b0549.js:10297)

Card configuration:

          - type: custom:bom-weather-card
            entity_sun: sun.sun
            entity_daily_summary: sensor.dark_sky_daily_summary
            entity_current_conditions: sensor.dark_sky_icon
            entity_humidity: sensor.humidity_outdoor
            entity_pressure: sensor.pressure_outdoor
            entity_temperature: sensor.temperature_outdoor
            entity_apparent_temp: sensor.dom_realfeel_temperature
            entity_wind_bearing: sensor.dark_sky_wind_bearing
            entity_wind_speed: sensor.dark_sky_wind_speed
            entity_pop: sensor.dark_sky_precip_probability
            entity_pop_intensity: sensor.dom_precipitation
            entity_forecast_high_temp_1: sensor.dark_sky_daytime_high_temperature_1d
            entity_forecast_high_temp_2: sensor.dark_sky_daytime_high_temperature_2d
            entity_forecast_high_temp_3: sensor.dark_sky_daytime_high_temperature_3d
            entity_forecast_high_temp_4: sensor.dark_sky_daytime_high_temperature_4d
            entity_forecast_high_temp_5: sensor.dark_sky_daytime_high_temperature_5d
            entity_forecast_low_temp_1: sensor.dark_sky_overnight_low_temperature_1d
            entity_forecast_low_temp_2: sensor.dark_sky_overnight_low_temperature_2d
            entity_forecast_low_temp_3: sensor.dark_sky_overnight_low_temperature_3d
            entity_forecast_low_temp_4: sensor.dark_sky_overnight_low_temperature_4d
            entity_forecast_low_temp_5: sensor.dark_sky_overnight_low_temperature_5d
            entity_forecast_icon_1: sensor.dark_sky_icon_1d
            entity_forecast_icon_2: sensor.dark_sky_icon_2d
            entity_forecast_icon_3: sensor.dark_sky_icon_3d
            entity_forecast_icon_4: sensor.dark_sky_icon_4d
            entity_forecast_icon_5: sensor.dark_sky_icon_5d
            entity_summary_1: sensor.dark_sky_summary_1d
            entity_summary_2: sensor.dark_sky_summary_2d
            entity_summary_3: sensor.dark_sky_summary_3d
            entity_summary_4: sensor.dark_sky_summary_4d
            entity_summary_5: sensor.dark_sky_summary_5d
            entity_pop_1: sensor.dark_sky_precip_probability_1d
            entity_pop_2: sensor.dark_sky_precip_probability_2d
            entity_pop_3: sensor.dark_sky_precip_probability_3d
            entity_pop_4: sensor.dark_sky_precip_probability_4d
            entity_pop_5: sensor.dark_sky_precip_probability_5d
            current_data_top_margin: 7em
            time_format: 24
            locale: pl
            tooltips: true
            tooltip_width: 100
            tooltip_bg_color: "#FAFAFA"
            tooltip_fg_color: "#212121"
            tooltip_border_color: "#D9D9D9"
            tooltip_left_offset: -14
            slot_l1: "wind"
            slot_l2: "pop"
            slot_l3: "sun_following"
            slot_l4: "remove"
            slot_l5: "remove"
            slot_r1: "humidity"
            slot_r2: "pressure"
            slot_r3: "sun_next"
            slot_r4: "remove"
            slot_r5: "remove"
            old_icon: "true"
            show_decimals: true

Hi,
I have installed your Card via HACS.
While everything looks great, I can not getting the icons to load

using the following:
entity_current_conditions: sensor.richmond_icon_descriptor_0, HA provides a value of mostly_sunny

Is there something I am missing?

Also, how do we get a background like the one in your images.
Thanks

This is the whole code for my card

type: custom:bom-weather-card
title: BOM Weather
entity_current_conditions: sensor.richmond_icon_descriptor_0
entity_temperature: sensor.richmond_temp
entity_wind_bearing: sensor.richmond_wind_direction
entity_forecast_high_temp_1: sensor.richmond_temp_max_1
entity_forecast_high_temp_2: sensor.richmond_temp_max_2
entity_forecast_high_temp_3: sensor.richmond_temp_max_3
entity_forecast_high_temp_4: sensor.richmond_temp_max_4
entity_forecast_high_temp_5: sensor.richmond_temp_max_5
entity_forecast_icon_1: sensor.richmond_icon_descriptor_1
entity_forecast_icon_2: sensor.richmond_icon_descriptor_2
entity_forecast_icon_3: sensor.richmond_icon_descriptor_3
entity_forecast_icon_4: sensor.richmond_icon_descriptor_4
entity_forecast_icon_5: sensor.richmond_icon_descriptor_5
entity_forecast_low_temp_1: sensor.richmond_temp_min_1
entity_forecast_low_temp_2: sensor.richmond_temp_min_2
entity_forecast_low_temp_3: sensor.richmond_temp_min_3
entity_forecast_low_temp_4: sensor.richmond_temp_min_4
entity_forecast_low_temp_5: sensor.richmond_temp_min_5
entity_summary_1: sensor.richmond_short_text_1
entity_summary_2: sensor.richmond_short_text_2
entity_summary_3: sensor.richmond_short_text_3
entity_summary_4: sensor.richmond_short_text_4
entity_summary_5: sensor.richmond_short_text_5
entity_sun: sun.sun
entity_daytime_high: sensor.richmond_temp_max_0
entity_daytime_low: sensor.richmond_temp_min_0
entity_wind_speed: sensor.richmond_wind_speed_kilometre
entity_wind_gust: sensor.richmond_gust_speed_kilometre
entity_humidity: sensor.richmond_humidity
entity_apparent_temp: sensor.richmond_temp_feels_like
entity_daily_summary: sensor.richmond_extended_text_0
entity_pop: sensor.richmond_rain_chance_0
entity_pop_intensity: sensor.richmond_rain_since_9am
entity_possible_today: sensor.richmond_rain_amount_range_0
entity_pos_1: sensor.richmond_rain_amount_range_1
entity_pos_2: sensor.richmond_rain_amount_range_2
entity_pos_3: sensor.richmond_rain_amount_range_3
entity_pos_4: sensor.richmond_rain_amount_range_4
entity_pos_5: sensor.richmond_rain_amount_range_5
entity_pop_1: sensor.richmond_rain_chance_1
entity_pop_2: sensor.richmond_rain_chance_2
entity_pop_3: sensor.richmond_rain_chance_3
entity_pop_4: sensor.richmond_rain_chance_4
entity_pop_5: sensor.richmond_rain_chance_5
entity_uv_alert_summary: sensor.richmond_uv_category_0
locale: en
static_icons: false
tooltip_bg_color: rgb( 75,155,239)
tooltip_border_color: orange
tooltip_border_width: 3
tooltip_caret_size: 10
tooltip_fg_color: '#fff'
tooltip_left_offset: -12
tooltip_width: 100
tooltips: true
old_daily_format: false
time_format: 12
show_beaufort: true
old_icon: 'true'
show_decimals: false

Hi,

When I enter the following line into the card, the card displays nothing:
"entity_wind_speed: sensor.sydney_observatory_hill_wind_speed_kilometer"

With this line removed, everything else seems to be working, looking like your example card. Animations, etc all work (It is great card and love the way it looks!!!). I seem to have the entity imported from the BOM integration and it seems to graph with reasonable values.

I think I have copied over all of your icons, directories, weather.yaml, etc. (I am still new to HA, so wasn't sure where resources... type:module text should go)

It all otherwise looks ok, and thanks for your help.

Craig

After upgrade HA to 0.116.0 card is not displayed and there is an error in browser console:

Uncaught TypeError: Cannot read property 'childElementCount' of null
    at HTMLElement.updateValues (bom-weather-card.js:878)
    at HTMLElement.set hass [as hass] (bom-weather-card.js:868)
    at HTMLElement.value (chunk.b78314dc93f493d4fbaf.js:10215)
    at HTMLElement.value (chunk.b78314dc93f493d4fbaf.js:10215)
    at HTMLElement.<anonymous> (chunk.b78314dc93f493d4fbaf.js:10215)
    at n (app.5c62d6a4.js:1)
    at chunk.b78314dc93f493d4fbaf.js:14638

Allow the ‘title’ attribute for the card to be presented in the UX for the card.

This is not an issue with this card as such, but due to this issue I am unable to install the card correctly.
Using the current (2021.4.x) version of Home Assistant, trying to create the folder config\www\icons fails.
I can create a folder of any other name, but trying to create this folder does not work.
When I go to a TTY terminal and create the folder manually on Home Assistant, the folder can create but is not visible via a share.

I am using Home Assistant, with Home Assistant OS (HassOS).

Any advice would be helpful with this.

Hi David;
These instructions are convoluted and very difficult to follow. 2 nights attempting to get this working and no success. Would it be possible to show proper examples of what you are entering into config.yaml / ui-lovelace.yaml in clear instructions? I've tried multiple combinations after "installing" this from HACS, yet nothing is working and no entities appearing. Something is missing yet after reading your instructions repeatedly I can not work out what it is.
Thanks

Double checked paths files etc. In the console I can see that the the Card cannot find the relevant animated picture.

When I use File Explorer in Chrome, access the animated picture via Samba, open it and it shows up with following in the address line:

file://10.1.1.100/config/www/Icons/weather_icons/animated/fair-day.svg.

It is probably a very simple solution but I break my head about it. Advise is appreciated.

Since updating Home Assistant to 2021.4, I have received the following Invalid config notification. I believe this relates to the bom-weather-card and am hoping that you will be able to provide some help in fixing. I cannot decipher the code. It does mention Script in the notification, and the code it provides in the Log suggests line 14 of my configuration.yaml file which is my scripts.yaml. I have gone through Scripts and there is no script pertaining to the BOM-Weather-Card...

Logger: homeassistant.config
Source: config.py:437
First occurred: 10:41:38 (1 occurrences)
Last logged: 10:41:38

Invalid config for [script]: expected a dictionary. Got OrderedDict([('homeassistant', OrderedDict([('name', 'Home'), ('latitude', -xx.xxxxxx), ('longitude', xxx.xxxxx), ('elevation', 24), ('unit_system', 'metric'), ('time_zone', 'Australia/Sydney'), ('internal_url', 'http://homeassistant.local:8123'), ('packages', OrderedDict([('weather', OrderedDict([('sensor', [OrderedDict([('platform', 'template'), ('sensors', OrderedDict([('bom_current_text', OrderedDict([('value_template', "{% set val = states('sensor.zetland_short_text_0').split('.')[0] %} .... (See /config/configuration.yaml, line 14).

And my config yaml for reference.

homeassistant: !include homeassistant.yaml

logger:
  default: info

default_config:
mobile_app:
discovery:
frontend: !include frontend.yaml
tts: !include tts.yaml

cloud: !include cloud.yaml
group: !include groups.yaml

script: !include scripts.yaml
automation: !include automations.yaml
scene: !include scenes.yaml

device_tracker: !include device_tracker.yaml
input_select: !include input_select.yaml
sensor: !include sensor.yaml
binary_sensor: !include binary_sensor.yaml
zone: !include zones.yaml
proximity: !include proximity.yaml

light: !include light.yaml
switch: !include switch.yaml
climate: !include climate.yaml

spotify: !include spotify.yaml
#spotcast: !include spotcast.yaml

Hi there,

First of all, great write up and very detailed - love it for people like me who are just learning this. I followed every step, got BOM installed, set my location, it created the sensors.

I copied your code, change the sensor names to mine but unfortunately it isnt working... any ideas? I would like to get the card you have in your example.

Thank you!

There is a typo in the readme.md file, that means if you are copying and pasting the example entity values, the card will not work. It's a simple fix, so I created a matching pull request #59.

Thanks for the great card.

Just a user-friendly feature request to enable to the ability to configure this awesome card from the lovelace card picker? Apparently a few lines of code, not sure how realistic the "easiness" is.

https://www.reddit.com/r/homeassistant/comments/jovt1l/usedevelop_custom_cards_your_card_could_be_in_the/?utm_source=share&utm_medium=web2x&context=3

Thanks for you great work.

I started with a fresh HASSIO install and restored just the configuration from a Snapshot. The rest I installed via the Store and HACS.

The BOM Weather Card didn't show anything. I isolated the problem to the entity_pop line. Without this line the weather is displayed.

Lines 935 and 936 of the bom_weather_card.js seems to where there is a problem. On another HA machine I don't have the second line and the weather card is working fine.

  if (this.config.entity_pop && !this.config.alt_pop) try { root.getElementById("pop-text").textContent = `${Math.round(this._hass.states[this.config.entity_pop].state)}` } catch(e) {}
  if (this.config.entity_pop && !this.config.alt_pop) try { root.getElementById("pop-text-today").textContent = `${this._hass.states[this.config.entity_possible_today].state}` } catch(e) {}

Would be great to be able to tap each item, and bring up the sensor's standard more-info box. (ie, tapping on the tempearture brings up the sensor.bom_xx_ sensor, for viewing its history, etc.

Would also love it if the forecast panels were expandable / collapsed by default.

I just converted over from the original Dark Sky card, everything seems to be working perfectly except the Visibility is no longer shown in the UI.

Any thoughts?

Hi I am trying to work out why since the recent upgrade for HASSIO and updated the your integrations and BOM its not finding this value. All other values are ok. So just want to understand how your weather yaml code works for find out why its not collecting it.
I have tried both methods using the average integration as per your guide. It was working prior to upgrade.

I am using warrawee as my custom local connection and Terrey Hills for everything else (as per the setup prompts)
I did unistall the bureau meterology integration and reinstalled it, same for your custom card.

So sensor.bom_today_max = unknown, and sensor.warrawee_temp_max_0 = 25 (I waited 24 hours in case it took time to update)
Below is screen shot of your weather.yaml and snippet of what I have in my card.

entity_daytime_high: sensor.bom_today_max
entity_daytime_low: sensor.bom_today_min

However

I think it's calling rainy-5.svg when maybe it should be calling rainy-2.svg

In my opinion, the new icons look much worse than the old ones.
I think the best solution would be to choose icons in the card configuration.
Is it possible?

Hi David - on updating my configurations I'm coming up against an issue with this section of code:

    name: today_temp_bom
    entities:
      - sensor.gosford_temperature
    start: '{{ now().replace(hour=0).replace(minute=0).replace(second=0) }}'
    end: '{{ now() }}'


      bom_today_max:
        value_template: >
          {%- if states('sensor.kariong_max_0') == 'n/a' -%} 
            {{ state_attr('sensor.today_temp_bom', 'max_value') }}
          {% else %}
            {{ states('sensor.kariong_max_0') }}
          {% endif %}
      bom_today_min:
        value_template: >
          {%- if states('sensor.sensor.kariong_min_0') == 'n/a' -%} 
            {{ state_attr('sensor.today_temp_bom', 'min_value') }}
          {% else %}
            {{ states('sensor.kariong_min_0') }}
          {% endif %}

this throws up a indenting error

If I move the bom_today_max back 1 tab the error goes away in the file editor but trying "check configuration" fails

I think I've installed the "average" integration properly - any ideas?

Hi,

I get the word 'Fire' in front of the summary information for fire danger summary

In the template tool: {{ states('sensor.bom_perth_forecast_fire_danger_summary') }}
Displays: Perth Coastal Plain: Low-Moderate, Perth Hills: Low-Moderate

In the card:
entity_fire_danger_summary: sensor.bom_perth_forecast_fire_danger_summary
See the attached image for how it shows

Apart from that, this is a great card - thank you 👍

Hi David,
Thanks for your awesome work! However I am having a small issue getting the appearance correct.
Can you point me in the right dirction to get the text up the top in the right place?
Kind regards,
Chris,

cards:
  - entity_apparent_temp: sensor.bom_bairnsdale_feels_like_c
    entity_current_conditions: sensor.bom_bairnsdale_icon_0
    entity_current_text: sensor.bom_current_text
    entity_daily_summary: sensor.bom_bairnsdale_detailed_summary_0
    entity_daytime_high: sensor.bom_today_max
    entity_forecast_high_temp_1: sensor.bom_bairnsdale_max_temp_c_1
    entity_forecast_high_temp_2: sensor.bom_bairnsdale_max_temp_c_2
    entity_forecast_high_temp_3: sensor.bom_bairnsdale_max_temp_c_3
    entity_forecast_high_temp_4: sensor.bom_bairnsdale_max_temp_c_4
    entity_forecast_high_temp_5: sensor.bom_bairnsdale_max_temp_c_5
    entity_forecast_icon_1: sensor.bom_bairnsdale_icon_1
    entity_forecast_icon_2: sensor.bom_bairnsdale_icon_2
    entity_forecast_icon_3: sensor.bom_bairnsdale_icon_3
    entity_forecast_icon_4: sensor.bom_bairnsdale_icon_4
    entity_forecast_icon_5: sensor.bom_bairnsdale_icon_5
    entity_forecast_low_temp_1: sensor.bom_bairnsdale_min_temp_c_1
    entity_forecast_low_temp_2: sensor.bom_bairnsdale_min_temp_c_2
    entity_forecast_low_temp_3: sensor.bom_bairnsdale_min_temp_c_3
    entity_forecast_low_temp_4: sensor.bom_bairnsdale_min_temp_c_4
    entity_forecast_low_temp_5: sensor.bom_bairnsdale_min_temp_c_5
    entity_humidity: sensor.bom_bairnsdale_relative_humidity
    entity_pop: sensor.bom_bairnsdale_chance_of_rain_0
    entity_pop_1: sensor.bom_bairnsdale_chance_of_rain_1
    entity_pop_2: sensor.bom_bairnsdale_chance_of_rain_2
    entity_pop_3: sensor.bom_bairnsdale_chance_of_rain_3
    entity_pop_4: sensor.bom_bairnsdale_chance_of_rain_4
    entity_pop_5: sensor.bom_bairnsdale_chance_of_rain_5
    entity_pop_intensity: sensor.bom_bairnsdale_rain_today
    entity_summary_1: sensor.bom_bairnsdale_summary_1
    entity_summary_2: sensor.bom_bairnsdale_summary_2
    entity_summary_3: sensor.bom_bairnsdale_summary_3
    entity_summary_4: sensor.bom_bairnsdale_summary_4
    entity_summary_5: sensor.bom_bairnsdale_summary_5
    entity_temperature: sensor.bom_bairnsdale_air_temp_c
    entity_wind_bearing: sensor.bom_bairnsdale_wind_direction
    entity_wind_speed: sensor.bom_bairnsdale_wind_speed_kmh
    title: BOM Weather
    type: 'custom:bom-weather-card'
type: vertical-stack
```

After last update there is a huge gap between the current conditions columns and the current temperature/icon.

Earlier versions:

Current version:

Configuration:

- type: custom:bom-weather-card
  entity_sun: sun.sun
  entity_daily_summary: sensor.dark_sky_daily_summary
  entity_current_conditions: sensor.dark_sky_icon
  entity_humidity: sensor.humidity_outdoor
  entity_pressure: sensor.pressure_outdoor
  entity_temperature: sensor.temperature_outdoor
  entity_apparent_temp: sensor.dark_sky_apparent_temperature
  entity_visibility: sensor.dark_sky_visibility
  entity_wind_bearing: sensor.dark_sky_wind_bearing
  entity_wind_speed: sensor.dark_sky_wind_speed
  entity_forecast_high_temp_1: sensor.dark_sky_daytime_high_temperature_1d
  entity_forecast_high_temp_2: sensor.dark_sky_daytime_high_temperature_2d
  entity_forecast_high_temp_3: sensor.dark_sky_daytime_high_temperature_3d
  entity_forecast_high_temp_4: sensor.dark_sky_daytime_high_temperature_4d
  entity_forecast_high_temp_5: sensor.dark_sky_daytime_high_temperature_5d
  entity_forecast_low_temp_1: sensor.dark_sky_overnight_low_temperature_1d
  entity_forecast_low_temp_2: sensor.dark_sky_overnight_low_temperature_2d
  entity_forecast_low_temp_3: sensor.dark_sky_overnight_low_temperature_3d
  entity_forecast_low_temp_4: sensor.dark_sky_overnight_low_temperature_4d
  entity_forecast_low_temp_5: sensor.dark_sky_overnight_low_temperature_5d
  entity_forecast_icon_1: sensor.dark_sky_icon_1d
  entity_forecast_icon_2: sensor.dark_sky_icon_2d
  entity_forecast_icon_3: sensor.dark_sky_icon_3d
  entity_forecast_icon_4: sensor.dark_sky_icon_4d
  entity_forecast_icon_5: sensor.dark_sky_icon_5d
  entity_summary_1: sensor.dark_sky_summary_1d
  entity_summary_2: sensor.dark_sky_summary_2d
  entity_summary_3: sensor.dark_sky_summary_3d
  entity_summary_4: sensor.dark_sky_summary_4d
  entity_summary_5: sensor.dark_sky_summary_5d
  entity_pop_1: sensor.dark_sky_precip_probability_1d
  entity_pop_2: sensor.dark_sky_precip_probability_2d
  entity_pop_3: sensor.dark_sky_precip_probability_3d
  entity_pop_4: sensor.dark_sky_precip_probability_4d
  entity_pop_5: sensor.dark_sky_precip_probability_5d
  time_format: 24
  locale: pl
  tooltips: true
  tooltip_width: 100
  tooltip_bg_color: "#FAFAFA"
  tooltip_fg_color: "#212121"
  tooltip_border_color: "#D9D9D9"
  tooltip_left_offset: -14
  slot_l1: "wind"
  slot_l2: "visibility"
  slot_l3: "sun_following"
  slot_l4: "remove"
  slot_l5: "remove"
  slot_r1: "humidity"
  slot_r2: "pressure"
  slot_r3: "sun_next"
  slot_r4: "remove"
  slot_r5: "remove"
  old_icon: "true"

The weather integrations for Home Assistant supports a wind_speed attribute. However no unit seems to be defined.

In my case, I'm using the default Meteorologisk institutt (Met.no) integration, which provides the wind-speed in km/h, however this card displays the data as mi/h. Home Assistant does not do any unit conversions, which results in the data being displayed with the wrong unit.

I assume that this is because I have Home Assistant set to use imperial units, but this is resulting in incorrect data being displayed. To fix this could this card be updated to display the wind speed in the weather card as km/h instead of mi/h IF the source returns data in km/h?
Alternatively this card can do km/h -> mi/h conversion, but I think that may be out of scope.

Related issue filed in Home Assistant core: home-assistant/core#55824

David, is there currently available a way to set background colour of BOM weather card to semi transparent.

I need some further instruction of setting this weather card up.

I have setup bom forecast and using weather.yaml packages template all working as expected. However, have some difficulty to get frontend bom-weather-card properly displayed.

I have installed HACS and installed Bom Weather Card through it. Also has weather icons downloaded extracted in the right path.

In the Readme.md - Configuration - 2, for HACS installation. Where should I put resources and module type? If I add lines at the top of home dashboard - raw configuration editor, system will alert me to add configuration in lovelace UI configuration.
So I go to Configuration - Lovelace Dashboards - Resources. I saw URL shows '/hacsfiles/bom-weather-card/bom-weather-card.js', Type shows 'JavaScript Module'. I have no way to change it type to 'module', the only option is 'Stylesheet'.
If I change the URL 'hacsfiles' to /config/www/community', HACS will alert me this frontend bom-weather-card is not loaded.

I assume JavaScript Module is the correct type. Then I go back to home page. Edit Dashboard, add card, manual, modify and paste content from bom-weather-card/lovelace.yaml but nothing shows up.

Would you please suggest which step I may have missed? Thanks a lot.

"\192.168.x.x\config\www\icons\bom_icons\mostly_sunny.png" exists, but it's not being displayed for some reason.

https://imgur.com/a/WrHnz18

Is it just me?

Cheers

G'day David, I have recently started using this card again.. which is amazing by the way.

Today and tomorrows icon code is "wind":

Yet, the card is showing the icon for cloudy

Hi,

I'm seeing an odd issue with the currentText object - it ends up printing underneath the apparent temperature, and the bounding box extends off the right hand edge of the card, which causes scroll bars to appear on my kitchen display.

I found that just removing the "width: ${currentTextWidth};" on line 621 or thereabouts produced something which renders sanely, but I'm not sure if that is the correct way to fix this.

Cheers

David

(oh, also it might be worth adding a console.info log line somewhere in there so it is obvious what version of the card is currently loaded, some other cards seem to have a line like this:
console.info("%c BOM-WEATHER-CARD \n%c Version 0.63 ", "color: orange; font-weight: bold; background: black", "color: white; font-weight: bold; background: dimgray"))

I've been through the setup in my current hass.io setup which I have been using dark sky successfully in. I've also created a new blank hass.io setup with the same results. In both instances I've used HACS to install bom_forecast and bom-weather-card with your weather.yaml file making sure to replace _gosford with _melbourne. I've tried both the basic lovelace config and your own lovelace config without any success. Are there any known issues that could cause this?

It was fixed a while ago I saw in the other issues.
I updated to 2021.8.0. I updated all the components to the latest version too.

Seems when I load the card I get - bom-weather-card.js:903:14 Uncaught TypeError: Cannot read property 'childElementCount' of null

I upgraded the average custom component as it was complaining it was depreciated but even when it was updated I am getting this error. How can we debug this and maybe fix it?

Could you please shed some light on this comment in the README.md

"VERY IMPORTANT NOTE: As of HA 0.117.x, the BOM Core Sensor component is removed as it violates ADR14 rule regarding web scraping."

Does this mean it is permanently disabled?

I am trying to install for the first time in this version.