BOM Definitely has that data available in their API but Brendan’s integration isn’t reading it into a sensor. There might already be a Github request for it so I’d check there and that’s the place for a feature request. Brendan has been quiet for a while now and I know he had a new baby a few months ago…
@DavidFW1960 This was the first card I added to home assistant and it is brilliant. I have altered some of the default settings. In particular to the width of the tooltip to fit the extended text. The extended text can annoyingly stretch up the screen. Also, some of the longer forecasts extended text have the entity daily summary truncated.
I’d like two changes:
- An option for tooltip to span the width of the card
- A way of fitting the extended forecast in the entity daily summary or a similar hover text to the tooltips.
Thanks for the suggestions.
Not 100% sure what you mean - are you using the template sensors as per the instructions?
You are also free to use whatever templates you want to provide the data you want and can use card-mod to make other changes as well as the variables already provided in the card config.
I have very limited js expertise and probably won’t be making the kinds of changes you are suggesting. If it’s within your abilities I would be happy to consider and PR you make.
The template seems to be functioning properly. Here is my template https://pastebin.com/2Rj4yJWb.
Here is an image of my card.
As you can see the tooltip could span of the card to make the text more readable. I suppose the same thing could be achieved if the tooltip width could be wider and the position adjusted so that it does not extending beyond the card.
I have also marked the area for the entity daily summary. An option to increase this to fit more text would be good.
I’ll have a look at the js but I think it maybe a few levels beyond me.
The summary space should expand to the required space to display the full summary which will be 255 characters - the limit for a state in home assistant. I don’t see a benefit in expanding the tooltip to include all that extra information.
What does everyone else think?
I use the brief summary for the tooltip so it’s not an issue for me.
1 Like
I understand that. for instance I have in custom:bom-weather-card
entity_current_conditions: sensor.ryde_mdi_icon_0
the sensor.ryde_mdi_icon_0 has a value of mdi:weather-sunny
if I go to my directory where the icons are:
config/www/icons/weather_icons/animated that value does not exist. There are plenty of other ones there, clear-day.svg etc. Even if I download an icon and name it weather-sunny.svg it still doesnt work.
The current condition is a template sensor that is text and that text is mapped to an icon (not an MDI icon. It has nothing to do with an mdi icon). The conditions mapped to icons are fixed to the standard BOM conditions and and others people not using BOM might have needed for their weather provider, Please follow the docs on github for this.
@DavidFW1960 Thank you very much for the card.
Just want to check with you to see if anyone has reported that in the iOS HA app, the card is causing the whole dashboard to not use the whole horizontal space, leaving a gap. If I remove the card, the dashboard goes back to normal.
Think I had a similar problem some time ago. Adjusting tooltip_left_offset: to -12 fixed it for me.
Mine’s already set to -12. I think it’s to do with the card, not the tooltip.
Actually, you are right. I changed tooltip_left_offset from -12 to -30 and it looks ok now. So it’s the tooltip that’s 'pushing’s away from the right border.
I use iOS app and chrome and never seen that… Pretty sure I’m using the default. My cards are all in vertical stacks…
Thanks for the card.
FYI in current sample/master lovelace.yaml there are the following entries:
entity_daytime_high: sensor.bom_today_max
entity_daytime_low: sensor.bom_today_min
For me I had to change these to my local suburb as created by the BOM integration to get the card to work (before I made this change the card would not show up at all) i.e. I think they should be as follows in the sample lovelace.yaml… might trip some people up otherwise.
entity_daytime_high: sensor.kariong__temp_max_0
entity_daytime_low: sensor.kariong_temp_min_0
No you need to follow the instructions and add either the statistics or average sensor and template sensors which will provide those sensors. You can use the specific suburb one if you want to however be aware during the day at some point BOM will publish thise as N/A so they will disappear… hence the average/statistics and template sensors recommended.
Ah OK apologies, I must have misunderstood.
Would you mind directing me to the part of the instructions I should be looking at? I have used the standard weather.yaml and changed nothing other than observation/suburb names, and I thought that included the necessary templates.
it is in the weather.yaml file down the bottom with examples for statistics and average… you will need to edit those with the name of your current temperature (and install the average component to use that one)
Got it, I had missed installing the “average” custom integration. Thanks for your help and all your work.
1 Like
Hi @DavidFW1960 - having issues where sensor.bom_today_min isn’t updating.
Currently I can see on the BOM site it should be 18.1 for today but the min_value is returning the same figure of the max_value attribute, being 29.6.
Min Sensor Template;
bom_today_min:
value_template: >
{{ state_attr('sensor.today_temp_bom', 'min_value') }}
And sensor.today_temp_bom:
sampling_size: 150
count: 1
mean: 29.6
median: 29.6
quantiles: unknown
standard_deviation: unknown
variance: unknown
total: 29.6
min_value: 29.6
max_value: 29.6
min_age: '2021-09-12T04:23:32.402621+00:00'
max_age: '2021-09-12T04:23:32.402621+00:00'
change: 0
average_change: 0
change_rate: 0
unit_of_measurement: °C
friendly_name: today_temp_bom
icon: mdi:calculator
Unsure if you’d need to see anything else to figure this one out?
Snippet of what it should be here:
Snippet of the card:
How do you have the statistics/average configured? It’s not seeing any updates so maybe you set a short interval?