Yeah it’s the weather platform one not working. I’ve never used that but maybe your config isn’t valid?
The templates I posted will give you that card you said you wanted (the forecast ones in the weather.yaml package). You also need to set the days to 6 not 3 if you want that card.
Not sure how you created your one… looks like you have not got the sensors created that the template uses.
I’d suggest removing everything to do with weather platforms and just follow my repo. Then build on that.
currest2620
(Steven Curren)
February 16, 2020, 5:02am
283
Thanks, I have removed all and started again a few times. I guess I added the bom weather: entry as part of installing the bom core package.
I removed the forecast: entry, but it didn’t make a difference. One thing I did notice though, after I removed “_summary” from bom_current_text, (ie change ‘sensor.bom_forecast_canberra_summary_0’ to ‘sensor.bom_forecast_canberra_0’ I did manage to get data from sensor.bom_current_text:
Still nothing for bom_forecast_0:
Maybe I’ll try again, but without for forecast entry.
Sensor.bom_forecast_0 is created by a template… the fact it says unknown for everything means the sensors it’s reading don’t exist.
Without you showing everything you have for the config it’s hard to see exactly what is going on.
1 Like
Nicko1
(Nick)
February 16, 2020, 10:41pm
285
Hi David
Pi-hole was blocking the FTP connection.
I stopped the add-on and it worked
Thanks
1 Like
Nicko1
(Nick)
February 16, 2020, 11:50pm
286
When loading the Bom weather card plug-in through HACS where do i find the card in the lovelace ui
I don’t understand the question…
Nicko1
(Nick)
February 17, 2020, 2:01am
288
Sorry I’m new to this
How do I access the custom card once the plug-in is installed
there is a lovelace.yaml example with full configuration for the card in the repo
Hi David,
Love your work you have taken my original project to the next level. Love it.
I have finally gotten around to testing this out and my card is looking just a little bit off… any ideas?
Hey Brendan… good to see you around. Is that actually my card? Did you follow the github instructions? It looks like it might not actually be my card. Otherwise can you show your lovelace config and I’ll take a look.
I could never have done what you did and needed help to add the fire and uv stuff… so thank YOU!
Edit:
Managed to fix it, although i’m not sure why it looked like that in the first place. Added these two lines:
current_text_top_margin: 68px
current_text_left_pos: 0em
Something odd with the template you are using for current_text… (which is weird because the template looks right) But it should just be Humid… not sure why it leaves Clear there as well…
current_text_top_margin: 4.5em #default 39px px or em
current_text_left_pos: 0em #default 5em px or em
current_text_font_size: 1.5em #default 1.5em em
current_text_alignment: center #default center
current_text_width: 100% #default 100%
I added those options to move the current_text as it is by defauly jammed over to the left and the icon kept running into it. The defaults will (sould) be applied if you don’t specify them.
currest2620
(Steven Curren)
February 18, 2020, 12:43am
294
Hey David, I think I’ve got it working. I changed:
“friendly:” from True to False (in platform: bom_forecast)
changed “sensor.bom_today_max” to “bom_canberra_max_temp_c_0” (same with today_min).
Thanks for your work and for responding to my posts and questions.
Cheers,
Yeah I use false. That’s what the docs say right?
So then there are 2 consequences to that…
After the minimum/maximum for the day, those will be showing as n/a states. It looks like you didn’t make the template sensors which will replace the n/a state with the min/max recorded for the day. The template sensors use the statistics sensor so you might have missed that as well… All templates are in the docs.
1 Like
currest2620
(Steven Curren)
February 18, 2020, 3:28am
296
Yeah, I misunderstood how it worked. I thought I could have both a summary and the more detailed information together. I also changed back to sensor.bom_today_max.
Thanks again for the advice. Have it all working now. Think I’ll give the bom weather card a go now.
1 Like
currest2620
(Steven Curren)
February 18, 2020, 4:48am
297
Hello again,
Now I have run into an issue with the bom weather card. I am getting a ‘No card type found’ error. It looks OK as far as I can see. I installed the card via HACS and added the resources information to lovelace and I can see the js file in my config/www folder. (config/www/community/bom-weather-card/bom-weather-card.js)
resources:
- type: module
url: /community_plugin/mini-graph-card/mini-graph-card-bundle.js
- type: module
url: /community_plugin/bom-weather-card/bom-weather-card.js
I’m going by the example file here .
Here’s what I have pasted into manual card in lovelace:
- type: custom:bom-weather-card
title: BOM Weather
entity_current_conditions: sensor.bom_canberra_icon_0
entity_temperature: sensor.bom_canberra_air_temp_c
entity_forecast_high_temp_1: sensor.bom_canberra_max_temp_c_1
entity_forecast_high_temp_2: sensor.bom_canberra_max_temp_c_2
entity_forecast_high_temp_3: sensor.bom_canberra_max_temp_c_3
entity_forecast_high_temp_4: sensor.bom_canberra_max_temp_c_4
entity_forecast_high_temp_5: sensor.bom_canberra_max_temp_c_5
entity_forecast_icon_1: sensor.bom_canberra_icon_1
entity_forecast_icon_2: sensor.bom_canberra_icon_2
entity_forecast_icon_3: sensor.bom_canberra_icon_3
entity_forecast_icon_4: sensor.bom_canberra_icon_4
entity_forecast_icon_5: sensor.bom_canberra_icon_5
entity_forecast_low_temp_1: sensor.bom_canberra_min_temp_c_1
entity_forecast_low_temp_2: sensor.bom_canberra_min_temp_c_2
entity_forecast_low_temp_3: sensor.bom_canberra_min_temp_c_3
entity_forecast_low_temp_4: sensor.bom_canberra_min_temp_c_4
entity_forecast_low_temp_5: sensor.bom_canberra_min_temp_c_5
entity_summary_1: sensor.bom_canberra_summary_1
entity_summary_2: sensor.bom_canberra_summary_2
entity_summary_3: sensor.bom_canberra_summary_3
entity_summary_4: sensor.bom_canberra_summary_4
entity_summary_5: sensor.bom_canberra_summary_5
entity_sun: sun.sun
# entity_visibility: sensor.dark_sky_visibility
entity_daytime_high: sensor.bom_today_max
entity_daytime_low: sensor.bom_today_min
entity_wind_bearing: sensor.bom_canberra_wind_direction
entity_wind_speed: sensor.bom_canberra_wind_speed_kmh
entity_humidity: sensor.bom_canberra_relative_humidity
# entity_pressure: sensor.dark_sky_pressure
entity_apparent_temp: sensor.bom_canberra_feels_like_c
entity_daily_summary: sensor.bom_canberra_detailed_summary_0
entity_pop: sensor.bom_canberra_chance_of_rain_0
entity_pop_intensity: sensor.bom_canberra_rain_today
entity_possible_today: sensor.bom_canberra_possible_rainfall_0
entity_pos_1: sensor.bom_canberra_possible_rainfall_1
entity_pos_2: sensor.bom_canberra_possible_rainfall_2
entity_pos_3: sensor.bom_canberra_possible_rainfall_3
entity_pos_4: sensor.bom_canberra_possible_rainfall_4
entity_pos_5: sensor.bom_canberra_possible_rainfall_5
entity_pop_1: sensor.bom_canberra_chance_of_rain_1
entity_pop_2: sensor.bom_canberra_chance_of_rain_2
entity_pop_3: sensor.bom_canberra_chance_of_rain_3
entity_pop_4: sensor.bom_canberra_chance_of_rain_4
entity_pop_5: sensor.bom_canberra_chance_of_rain_5
entity_current_text: sensor.bom_current_text
entity_uv_alert: sensor.bom_uv_alert
entity_fire_danger: sensor.bom_fire_danger
entity_uv_alert_summary: sensor.bom_uv_alert_summary
entity_fire_danger_summary: sensor.bom_fire_danger_summary
locale: en
sunset: true
static_icons: false
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
old_daily_format: false
time_format: 12
show_beaufort: false
refresh_interval: 60
show_separator: false
temp_top_margin: -0.3em #default -0.3em px or em
temp_font_weight: 300 #default 300 numeric
temp_font_size: 4em #default 4em em
temp_right_pos: 0.85em#default .85em px or em
temp_uom_top_margin: -9px #default -9px px or em
temp_uom_right_margin: 7px #default 7px px or em
apparent_top_margin: 45px #default 45px px or em
apparent_right_pos: 1em #default 1em px or em
apparent_right_margin: 1em #default 1em px or em
current_text_top_margin: 4.5em #default 39px px or em
current_text_left_pos: 0em #default 5em px or em
current_text_font_size: 1.5em #default 1.5em em
current_text_alignment: center #default center
current_text_width: 100% #default 100%
current_data_top_margin: 10em #default 7em px or em
large_icon_top_margin: -3.5em #default -3.5em px or em
large_icon_left_position: 0em #default 0em px or em
separator_top_margin: 6em #default 6em px or em
summary_top_padding: 2em #default 1em px or em
summary_font_size: 0.8em #default 0.8em px or em
slot_l1: daytime_high #daytime_high
slot_l2: daytime_low #daytime_low
slot_l3: wind #wind
slot_l4: pressure #pressure
slot_l5: sun_next #sun_next
slot_r1: pop#pop
slot_r2: humidity #humidity
slot_r3: uv_alert #uv_alert
slot_r4: fire_danger #fire_danger
slot_r5: sun_following#sun_following
Pretty sure I have the sensors setup right. Don’t understand why I am getting ‘No card type found’. Any tips appreciated. Thanks again.
need a space here:
slot_r5: sun_following #sun_following
Check all mapped entities exist and clear cache - looks ok otherwise…
1 Like
currest2620
(Steven Curren)
February 19, 2020, 1:32am
300
I checked every entity listed below against developer tools states and they all exist and have values. The one thing I have noticed is that not all of the slots at the bottom are defined as entities. For example slot_l3 is assigned as ‘wind’, but the entities are ‘entity_wind_bearing’ and ‘entity_wind_speed’. Is that an issue? Should they be defined in sensor.yaml?
The error under the card config says: “Cannot read property ‘setConfig’ of undefined” in addition to “No card type found”
I’m a bit stumped TBO. Still I have the entities card working and that’s great.
- type: 'custom:bom-weather-card'
title: BOM Weather
entity_current_conditions: sensor.bom_canberra_icon_0
entity_temperature: sensor.bom_air_temp_c
entity_forecast_high_temp_1: sensor.bom_canberra_max_temp_c_1
entity_forecast_high_temp_2: sensor.bom_canberra_max_temp_c_2
entity_forecast_high_temp_3: sensor.bom_canberra_max_temp_c_3
entity_forecast_high_temp_4: sensor.bom_canberra_max_temp_c_4
entity_forecast_high_temp_5: sensor.bom_canberra_max_temp_c_5
entity_forecast_icon_1: sensor.bom_canberra_icon_1
entity_forecast_icon_2: sensor.bom_canberra_icon_2
entity_forecast_icon_3: sensor.bom_canberra_icon_3
entity_forecast_icon_4: sensor.bom_canberra_icon_4
entity_forecast_icon_5: sensor.bom_canberra_icon_5
entity_forecast_low_temp_1: sensor.bom_canberra_min_temp_c_1
entity_forecast_low_temp_2: sensor.bom_canberra_min_temp_c_2
entity_forecast_low_temp_3: sensor.bom_canberra_min_temp_c_3
entity_forecast_low_temp_4: sensor.bom_canberra_min_temp_c_4
entity_forecast_low_temp_5: sensor.bom_canberra_min_temp_c_5
entity_summary_1: sensor.bom_canberra_summary_1
entity_summary_2: sensor.bom_canberra_summary_2
entity_summary_3: sensor.bom_canberra_summary_3
entity_summary_4: sensor.bom_canberra_summary_4
entity_summary_5: sensor.bom_canberra_summary_5
entity_sun: sun.sun
entity_daytime_high: sensor.bom_today_max
entity_daytime_low: sensor.bom_today_min
entity_wind_bearing: sensor.bom_wind_direction
entity_wind_speed: sensor.bom_wind_speed_kmh
entity_humidity: sensor.bom_relative_humidity
entity_apparent_temp: sensor.bom_feels_like_c
entity_daily_summary: sensor.bom_canberra_detailed_summary_0
entity_pop: sensor.bom_canberra_chance_of_rain_0
entity_pop_intensity: sensor.bom_rain_today
entity_possible_today: sensor.bom_canberra_possible_rainfall_0
entity_pos_1: sensor.bom_canberra_possible_rainfall_1
entity_pos_2: sensor.bom_canberra_possible_rainfall_2
entity_pos_3: sensor.bom_canberra_possible_rainfall_3
entity_pos_4: sensor.bom_canberra_possible_rainfall_4
entity_pos_5: sensor.bom_canberra_possible_rainfall_5
entity_pop_1: sensor.bom_canberra_chance_of_rain_1
entity_pop_2: sensor.bom_canberra_chance_of_rain_2
entity_pop_3: sensor.bom_canberra_chance_of_rain_3
entity_pop_4: sensor.bom_canberra_chance_of_rain_4
entity_pop_5: sensor.bom_canberra_chance_of_rain_5
entity_current_text: sensor.bom_current_text
entity_uv_alert: sensor.bom_uv_alert
entity_fire_danger: sensor.bom_fire_danger
entity_uv_alert_summary: sensor.bom_uv_alert_summary
entity_fire_danger_summary: sensor.bom_fire_danger_summary
locale: en
sunset: true
static_icons: false
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
old_daily_format: false
time_format: 12
show_beaufort: false
refresh_interval: 60
show_separator: false
temp_top_margin: -0.3em
temp_font_weight: 300
temp_font_size: 4em
temp_right_pos: 0.85em
temp_uom_top_margin: -9px
temp_uom_right_margin: 7px
apparent_top_margin: 45px
apparent_right_pos: 1em
apparent_right_margin: 1em
current_text_top_margin: 4.5em
current_text_left_pos: 0em
current_text_font_size: 1.5em
current_text_alignment: center
current_text_width: 100%
current_data_top_margin: 10em
large_icon_top_margin: -3.5em
large_icon_left_position: 0em
separator_top_margin: 6em
summary_top_padding: 2em
summary_font_size: 0.8em
slot_l1: daytime_high
slot_l2: daytime_low
slot_l3: wind
slot_l4: pressure
slot_l5: sun_next
slot_r1: sun_following
slot_r2: humidity
slot_r3: uv_alert
slot_r4: fire_danger
slot_r5: possible_today
currest2620:
Is that an issue?
Not an issue… just make sure that entity_wind_bearing and entity_wind_speed exist.
Can you check the card was downloaded correctly? Past the first few lines of the js file here…
1 Like