Yeah like I said you will need a template to extract which fire rating you want to display.
UV unavailable… check your template there as well. Check my post above - I edited my template a few times… there was an error there up till a couple of hours ago and I haven’t pushed a fix for that to a new release yet.
Updated the templates but as you noted the data is available again, so no real test possible yet.
Perth Coastal Plain
{% set val = states('sensor.bom_fire_danger_summary').split(',')[0] %}
{{ val | title }}
Perth Hills
{% set val = states('sensor.bom_fire_danger_summary').split(',')[1] %}
{{ val | title }}
Better:
1 Like
Good job… it’ll work better on mobile if you get rid of the ‘Perth Coastal Plain’ part for the slot… it’s not like you don’t know that…
Yeah did not check the phone:
{% set val = states('sensor.bom_fire_danger_summary').split('Perth Coastal Plain: ')[1] .split(':')[1] %}
{{ val | title }}
1 Like
I seem to be stuck on v0.54 of the Lovelace card. I have not been able to update to any of the new versions up to and including 0.57.
Odd! HACS says 0.57 available and installed for me. Can you manually download it? Sounds like a HACS issue? (I update via HACS)
Yeah it’s available but nothing happens when I hit the update button:
Every other card I’ve tried updates ok.
EDIT1: Ok this is weird. I uninstalled the plugin. Restarted. Waited for HACS to update, pressed install on v0.57 of the weather card and… it installed (or thinks it installed) v0.54.
Wat?
EDIT2: I downgraded to v0.53, that worked. I then successfully upgraded to 0.57. Very odd that 0.54 to higher version did not work.
Weird is all I can say…
@DavidFW1960 (hmm - no issues link on your github??)
Re your lovelace.yaml:
slot_l1: daytime_high #daytime_high
slot_l2: daytime_low #daytime_low
slot_l3: wind #wind
slot_l4: pressure #pressure
slot_l4: 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
You have two slot_l4…
Secondly, using your lovelace.yaml - I get the following issue:
any idea why the text is overwriting?
and forced the browser to reload, and suddenly the text is fine…
oh well.
hahaha…
Thanks for telling me about the slot - corrected on github now.
The current text has config variables…
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
Looks like refreshing fixed it…
1 Like
Hi there.
I tried to install your weather card and bom_forecast! Unfortunatly I am getting an error on start up, I did a manual install as i have no hacs but it seems to be configured correctly but i get an error on start up.
Any advice thanks! Running on RPi 3 and Home Assistant 0.102.3 (hassio)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 150, in _async_setup_platform
await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/bom_forecast/sensor.py", line 252, in setup_platform
bom_forecast_data.update()
File "/usr/src/homeassistant/homeassistant/util/__init__.py", line 240, in wrapper
result = method(*args, **kwargs)
File "/config/custom_components/bom_forecast/sensor.py", line 491, in update
ftp.retrbinary('RETR ' + self._product_id + '.xml', file_obj.write)
File "/usr/local/lib/python3.7/ftplib.py", line 442, in retrbinary
with self.transfercmd(cmd, rest) as conn:
File "/usr/local/lib/python3.7/ftplib.py", line 399, in transfercmd
return self.ntransfercmd(cmd, rest)[0]
File "/usr/local/lib/python3.7/ftplib.py", line 365, in ntransfercmd
resp = self.sendcmd(cmd)
File "/usr/local/lib/python3.7/ftplib.py", line 273, in sendcmd
return self.getresp()
File "/usr/local/lib/python3.7/ftplib.py", line 246, in getresp
raise error_perm(resp)
ftplib.error_perm: 550 Failed to open file.
Can you show your configuration for the component please? Assume you installed the core BOM component as well?
When you validate config do you see any errors?
Config check = Configuration valid!
config.yaml
######## BOM FORECAST ######
- platform: bom_forecast
product_id: IDQ60900
name: Brisbane #In my examples I use Gosford
forecast_days: 6
rest_of_today: true
friendly: false
friendly_state_format: '{max}, {summary}'
monitored_conditions:
- 'max'
- 'min'
- 'chance_of_rain'
- 'possible_rainfall'
- 'summary'
- 'detailed_summary'
- 'icon'
- 'uv_alert'
- 'fire_danger'
##### END BOM_FORECAST #######
weather:
- platform: bom
station: IDQ60901.94561
raw config editor
resources:
- type: module
url: /local/mini-graph-card-bundle.js?v=0.8.2
- type: js
url: /local/custom-lovelace/bar-card/bar-card.js?v=1.0.0
- type: module
url: /local/custom_ui/bom-weather-card.js?v=0.1
I’ll take a look tomorrow… bedtime now…
No rush mate 
Your product id for bom forecast is wrong:
Use IDQ10095 for bom_forecast
The station for weather looks ok… (probably) BUT you want the sensor not the weather component
See also my example on my github.
Lastly, you are showing an incomplete lovelace configuration if you are wanting to use the custom card
I am an idiot i did have bom setup with sensor i forgot to quote it.
All working sweet now thanks !!!
Actuallly: fire danger and UV alerts are not working but i will read up the thread to see if there was a fix … it doesnt show up in the card but shows up in the states:
[sensor.bom_brisbane_fire_danger_0] Very High
if i use slot_r3: fire_summary nothing happens, same with uv_summary. They seem to be in the config.yaml though.
do you have the latest version of the card?