Make sure the template sensor is returning real values. If you use the average integration I recommend there was a breaking change that duplicated the sensors with an _2 prefix that you need to fix. Easiest way is to delete the entities in configuration>entities and restart home assistant after which will remove the _2’s for you and all sensors will have the original names.
David, yes I’m using the HACS Average integration. Do I need to delete all 130 entities from the BOM integration or only those with _2 in their name?
don’t delete the _2 ones… delete the original ones without the _2 and restart and it will magically fix itself. It’s only the ones created by average.
Well, I ended up deleting the BOM and Average integrations, re-start HA, add them back, re-start HA. Card still showing the NaN for High and Low.
Do you still have the _2’s? You most probably do because you will have the original ones ‘restored’ so do what I suggested above!
Have you seen this one before David?
Logger: frontend.js.latest.202105311
Source: components/system_log/__init__.py:190
First occurred: 13:37:58 (1 occurrences)
Last logged: 13:37:58
https://10.1.1.100:8123/hacsfiles/bom-weather-card/bom-weather-card.js:914:9 TypeError: root is null
never…
The only error I’m seeing is a litelement (not related to this card already fixed) and a bunch of apexchart errors but none like that.
Clear Cache & Hard Reload?
I was getting some log errors after updating to b3 just before but after a restart none…
OK did you update to 0.89a? It guards for thisshadowroot but I only released it as a beta. I will do a release now as it seems I didn’t screw anything up.
No but I was testing core b3. Had to rollback as it shot my CPU use through the roof and I don’t have time to debug it right now.
1 Like
I’ve noticed in the last few days, i think since updating to latest core that my custom card no longer appears at all, log file looks clear except this entry
2021-06-04 04:08:14 ERROR (MainThread) [frontend.js.latest.202106011] http://192.168.1.2:8123/hacsfiles/bom-weather-card/bom-weather-card.js:914:14 Uncaught TypeError: Cannot read property ‘childElementCount’ of null
- title: weather
path: weather
icon: mdi:weather-pouring
badges: []
cards:
- type: custom:bom-weather-card
title: BOM Weather
entity_current_conditions: sensor.skye_icon_descriptor_0
entity_temperature: sensor.frankston_ballam_park_temp
entity_forecast_high_temp_1: sensor.skye_temp_max_1
entity_forecast_high_temp_2: sensor.skye_temp_max_2
entity_forecast_high_temp_3: sensor.skye_temp_max_3
entity_forecast_high_temp_4: sensor.skye_temp_max_4
entity_forecast_high_temp_5: sensor.skye_temp_max_5
entity_forecast_icon_1: sensor.skye_icon_descriptor_1
entity_forecast_icon_2: sensor.skye_icon_descriptor_2
entity_forecast_icon_3: sensor.skye_icon_descriptor_3
entity_forecast_icon_4: sensor.skye_icon_descriptor_4
entity_forecast_icon_5: sensor.skye_icon_descriptor_5
entity_forecast_low_temp_1: sensor.skye_temp_min_1
entity_forecast_low_temp_2: sensor.skye_temp_min_2
entity_forecast_low_temp_3: sensor.skye_temp_min_3
entity_forecast_low_temp_4: sensor.skye_temp_min_4
entity_forecast_low_temp_5: sensor.skye_temp_min_5
entity_summary_1: sensor.skye_short_text_1
entity_summary_2: sensor.skye_short_text_2
entity_summary_3: sensor.skye_short_text_3
entity_summary_4: sensor.skye_short_text_4
entity_summary_5: sensor.skye_short_text_5
entity_sun: sun.sun
entity_daytime_high: sensor.skye_temp_max_0
entity_daytime_low: sensor.skye_temp_min_0
entity_wind_bearing: sensor.frankston_ballam_park_wind_direction
entity_wind_speed: sensor.frankston_ballam_park_wind_speed_kilometre
entity_wind_gust: sensor.frankston_ballam_park_gust_speed_kilometre
entity_humidity: sensor.frankston_ballam_park_humidity
entity_apparent_temp: sensor.frankston_ballam_park_temp_feels_like
entity_daily_summary: sensor.skye_extended_text_0
entity_pop: sensor.skye_rain_chance_0
entity_pop_intensity: sensor.frankston_ballam_park_rain_since_9am
entity_possible_today: sensor.skye_rain_amount_range_0
entity_pos_1: sensor.skye_rain_amount_range_1
entity_pos_2: sensor.skye_rain_amount_range_2
entity_pos_3: sensor.skye_rain_amount_range_3
entity_pos_4: sensor.skye_rain_amount_range_4
entity_pos_5: sensor.skye_rain_amount_range_5
entity_pop_1: sensor.skye_rain_chance_1
entity_pop_2: sensor.skye_rain_chance_2
entity_pop_3: sensor.skye_rain_chance_3
entity_pop_4: sensor.skye_rain_chance_4
entity_pop_5: sensor.skye_rain_chance_5
entity_fire_danger_summary: sensor.skye_fire_danger_0
entity_uv_alert_summary: sensor.skye_uv_category_0
slot_l1: daytime_high
slot_l2: daytime_low
slot_l3: wind
slot_l4: uv_summary
slot_l5: remove
slot_r1: pop
slot_r2: popforecast
slot_r3: possible_today
slot_r4: possible_tomorrow
slot_r5: remove
You probably are using an old version of the card. Update to 0.89a
Are you using Average sensor? Can you show your yaml config for weather.
That error almost 100% is a caching issue… Press F12 - what version does that say?
Try right clicking refresh and empty cache and hard reload… then CTRL+R a few times…
I cant find a yaml config for weather anywhere, and i dont’ think im using the average sensor.
I’m getting the same issue in both chrome and firefox
Check all the entities you are parsing to the card exist - check the state in dev-tools.
all entities in the card exist, i have two entities with a value of unknown though,
sensor.skye_temp_min_0
sensor.skye_fire_danger_0
Can you PM me your lat/long so I can setup and see what the issue is please? Maybe try substituting the min_0 for min_1 just to see. The fire danger is optional so should not be a problem. Nothing has changed here though so if it was working before it should work now.
here’s a ripper - since upgrading from core-2021.5.5 to core-2021.6.0 and 2020.6.1 I can’t get the weather card to display anymore on a PC - works fine on mobile devices though.
have tried multiple devices, even a new one that’s never seen HA before… any ideas, David?
Cache. See above.
It’s not the card. I assume you have latest version from a few days ago?
Yeah, I’ve updated the card when I saw you’d released the new version.
I’ve tried everything, including a brand new Ubuntu install (completely unused browser) and it won’t load the card post 2021.5.5 …
Got me stumped, and I want to get off 2021.5.5 to fix the Garmin integration…
Mind you, the Fitbit component broke with 2021.6.0, so seems the world is against me (as well as being in Covid lockdown in Melbourne) 