Not 100% sure but now it’s showing as a low of 25 and high of 30…
Happy to email you the config if you like? I just filled in the blanks when I configured it.
Just post it here for that integration… I’m not 100% sure if the statistics integration resets on a HA restart… you could also try the average custom component. It’s something to do with how you have it configured though.
1 Like
What does the history for sensor.sydney_temp look like in History? This is my one for Gosford
I am thinking for some reason you’re not getting much data so the stats sensor doesn’t have much to use? In any case the min and max temperature is calculated from that sensor. There is nothing obviously wrong in your config.
The statistics sensor also needs the recorder integration running and for you not to have excluded the entity from the stats as well. See
Failing all that, I don’t know what is happening. The card only uses what you are feeding it.
Looks like I have flat lined…
I’ve just greyed out all entries I had in the recorder.yaml file to see if it was something there…
anything in your logfile for the BOM integration?
Yep
2021-09-13 09:21:24 ERROR (MainThread) [homeassistant.config] Invalid config for [automation]: expected dictionary. Got OrderedDict([('default_config', {}), ('homeassistant', OrderedDict([('name', 'Home'), ('latitude', -33.00000), ('longitude', 151.00000), ('elevation', 24), ('unit_system', 'metric'), ('time_zone', 'Australia/Sydney'), ('internal_url', 'http://homeassistant: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').... (See ?, line ?).
Seems to be an automation (the Icon update one). But I was referring to the integration for BOM… for some reason your sensor isn’t updating properly.
Can you see what https://api.weather.bom.gov.au/v1/locations/r659gg/observations returns? Using your geohash to replace r659gg in that URL. You will have to find that in the .storage folder probably… (or use https://api.weather.bom.gov.au/v1/locations?search=sydney )
Any idea what file I should be looking at in .storage?
no idea… you will have to search for bureau or one of the sensor/entity names I think Or use the URL I posted and it should give you the geohash I think 
https://api.weather.bom.gov.au/v1/locations/r659gg/observations returns
{"metadata":{"response_timestamp":"2021-09-13T05:36:32Z"},"data":[{"geohash":"r3gx2sp","id":"Sydney-r3gx2sp","name":"Sydney","postcode":"2000","state":"NSW"},{"geohash":"r3grt8x","id":"Sydney Olympic Park-r3grt8x","name":"Sydney Olympic Park","postcode":"2127","state":"NSW"},{"geohash":"r3gx8b6","id":"North Sydney-r3gx8b6","name":"North Sydney","postcode":"2060","state":"NSW"},{"geohash":"r3gx0qr","id":"Darlington-r3gx0qr","name":"Darlington","postcode":"2008","state":"NSW"},{"geohash":"r3gx2u4","id":"The Rocks-r3gx2u4","name":"The Rocks","postcode":"2000","state":"NSW"}]}
Which I assume is then I put r3grt8x in to the first URL you mentioned, which returns:
{"errors":[{"code":"WEATHER-400","title":"Invalid Geohash","status":"400","detail":"The geohash string was not 6 character."}]}
Looks like something to do with it not accepting the 7 character GeoHash?
looks like that… have a look in .storage for the code you have in your config
Couldn’t find anything. Ended up reinstalling the integration, but nothing really changed. The sydney_temp sensor is changing now though…
However BOM is stills aying 12.1 will be the lowest today, and the Weather Card is following the current temp, would that have something to do with the recorder history? I thought it was a forecast into the future?
OK but the statistics will only track the current temperature and show the ACTUAL LOW from that - it’s not a forecast low it’s the actual low. You can show the forecast high/low if you want to by using that _0 entity however there is a drawback of using that in that BOM will report that as unavailable during the day so I prefer to use the average/stats sensor which will show the actual for the current day. I do also have my mini card displayed which shows the forecast but it’s your call what you use so do whatever makes sense to you. The card will only show what you configure it to show.
1 Like
Ah right so I have been misunderstanding this the whole time. The idea is to show you what the lowest temperature has been so far since midnight?
Will talk to the wife to see what she wants…
Yes that’s the idea. With the old BOM integration the low forecast for today would be shown as n/a at around 4am in the morning… With the new integration, it seems that bom make it n/a around 4pm. The high used to disappear around 4pm but now it seems to do it around 10pm. So it’s really up to you what you want to show. The actual low here is around 4am and the high maybe 2PM so I just choose to show the values from average/statistics as that’s what makes sense to ME
1 Like
I have been reading about this stuff. May I confuse the issue? The actual weather recording statistics are based on a day starting at times depending on the country standard. The BOM uses 9am to 9am. BOM stats
The actual temperature observation is published every 30 minutes so the average sensor will give you the average for whatever period you specify. The forecast info for a day is for the time between 9am to 9am.
Hi David. Is there a way to pull the current animated weather icon out easily? Briefly looking just now all the relevant entities seem to have the non animated BOM icon associated with them so i assume they are grabbed dynamically within the card. Hoping it’s a simple thing i’ve missed?
If you have this set in your card config:
static_icons: false
and are still not seeing the animated icons, you probably need to download them:
1 Like