A pre-release of platinum-weather-card 0.0.4b2 has been made available.
It hopefully fixes the issues of the wrong days been shown in the forecast section.
Also for people using NWS or EnviroCanada that have 2 forecasts per day it should also hopefully work. The work was done by someone from the USA (I’d tag them here but I don’t know the persons id in this community).
2 Likes
We are now starting to try and separate the 2 cards. If you need help with the new Platinum Weather Card, please head over here.
2 Likes
Any chance to have this card working with an alternative of Dark Sky which is already unavailable (at least on my environment)?
it will work with any weather provider if you configure it for the correct sensors
Is there any update on the best way to pull pressure data (either through the integration or a custom sensor)?
Is there any chance to increase the space between the slot-lines? In my opinion the slots could have a little bit more space between them but I cannot figure out how to do it in css.
Anyone a tip?
Got it myself. If anoyne is interested how I configured the whole card:
:host {
left: 61.5%;
top: 40%;
width: 72%;
height: 76%;
--ha-card-border-width: 0px 3px 3px 0px;
--ha-card-border-color: #212121;
}
ha-icon {
height: 35px;
width: 35px;
}
.f-slot-horiz {
height: 160px;
margin-top: 15px;
}
.f-slot-horiz-text {
height: 30px;
font-size: 25px;
}
.currentTemps {
font-size: 25px;
margin-right: 40px;
}
.big-icon {
top: 10px;
}
.slot-text {
padding-right: 3px;
line-height: 50px;
margin-top: 20px;
}
.slot-list li {
height: 30px !important;
font-size: 25px;
margin-bottom: 15px;
}
.slot-list-item-1 {
margin-left: 50px;
}
.slot-icon {
width: 50px !important;
height: 50px !important;
}
.line {
margin-bottom: 0px;
margin-top: 0px;
}
.icon {
height: 80px !important;
width: 80px !important;
margin-bottom: -20px;
}
.lowTemp {
font-weight: bold;
opacity: 0.7;
}
.apparent {
top: 10px !important;
font-size: 25px;
color:
{% if states('sensor.chemnitz_realfeel_temperature') | int <= 10 %}
lightblue;
{% elif states('sensor.chemnitz_realfeel_temperature') | int >= 25 %}
#ff2929;
{% else %}
#4ad032;
{% endif %}
}
.unit-temp-small {
top: 8px !important;
font-size: 15px;
opacity: 0.8;
}
.slash {
padding-left: 8px;
padding-right: 8px;
}
ha-card {
height: 100%;
border-radius: 1vw;
position: relative;`
````````````````````````````````````````````````````(Hope this is the right place - I can’t find other BoM related topics)
Since the update to 2023.8.2, I’m not getting the following error:
This error originated from a custom integration.
Logger: homeassistant.config_entries
Source: custom_components/bureau_of_meteorology/PyBoM/collector.py:87
Integration: Bureau of Meteorology (documentation, issues)
First occurred: 17 August 2023 at 11:50:13 (1 occurrences)
Last logged: 17 August 2023 at 11:50:13
Error setting up entry Croydon for bureau_of_meteorology
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 388, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/bureau_of_meteorology/__init__.py", line 70, in async_setup_entry
await collector.async_update()
File "/config/custom_components/bureau_of_meteorology/PyBoM/collector.py", line 87, in async_update
self.locations_data = await resp.json()
^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/client_reqrep.py", line 1104, in json
raise ContentTypeError(
aiohttp.client_exceptions.ContentTypeError: 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://api.weather.bom.gov.au/v1/locations/r1r340')
All of the entities are now saying they are unavailable. They were all OK for some months now.
Is it me or is it something that needs to be changed in the integration?
Susan
You need to update the integration to the latest version.
As the great man says: “Doh”
If I’d looked at the HACS page it was telling me to restart!!!
Thanks
Susan
Hi All;
Recently my weather integrations went pear shaped for reasons I couldn’t understand, which ultimately led to various automations to stop functioning. It was a simple fix by just deleting my BOM Weather Integrations & adding them again.
However the Pressure Sensor hasn’t returned? I figured it maybe my local station didn’t have them, but I can see “Melbourne Airport” does - yet the integration doesn’t add it?
I tried digging into the integration code, and I can’t find it listed? Can it be added or was it deleted?
ta
I don’t think it is available via the API. I vaguely remember asking about that.
The BOM api being used has never provided any pressure information.
This is to be expected. Read the HA core 2023.9 release notes.
The developer is very busy right now but fortunately there are 6 months before this actually becomes an issue.
1 Like
The new beta release v1.2.0 that solves the warning above, has omitted the forecast attribute. This has made issues with likes of platinum-weather-card that use this attribute to show icons, temp, etc. for forecast field. Is this intentional?
(forecast attribute is a list of dictionaries which points to upcoming days’ forecasts. Each dict has keys like date, condition, temperature, etc.)
You need to create a triggered template sensor. Like this:
https://www.home-assistant.io/integrations/template/#trigger-based-handling-of-service-response-data
Though I’d replace the time pattern trigger with a state trigger that monitors the weather entity for updates,
template:
- trigger:
- platform: state
entity_id: weather.whatever
action:
- service: weather.get_forecast
data: etc...
1 Like
Thanks for the quick reply. So the omission of forecast attribute is intentional.
I think HA wants people to actually use their new service with return value 
.
Looking at above template sensor, I think if for a couple of days e.g. weather.whatever's state stays rainy, it won’t get triggered. Maybe sticking to time-pattern makes more sense?
A state trigger with no to or from specified triggers on all state and attribute changes. So it will trigger whenever anything in the entity changes.
1 Like
Great. I didn’t know that 
.
On another note, while testing on developer tools, it looks like v1.2.0 of the bom integration does not support weather.get_forecast yet. Or might be another mistake on my side.
Failed to call service weather.get_forecast. Entity weather.my_suburb does not support this service.