Nice work on the latest version. Shame that the Australian BOM shows so little info. The card doesn’t look good.

I’ve gone back to dark-sky, but have an issue from before 0.3.0. The min/max temp only shows the first value. Is there something I’m missing? I click on the card to get the more-info popup and it has a tonne of info in there, it just wont read anything else.

I’ve gone back to dark-sky, but have an issue from before 0.3.0. The min/max temp only shows the first value. Is there something I’m missing? I click on the card to get the more-info popup and it has a tonne of info in there, it just wont read anything else.

Well, dark sky doesn’t expose a min temp so that’s why.
What do you mean with - it just wont read anything else ?

marksev1:

I dont see anything obvious…I do use dark-sky-weather card also…are they conflicting each other?

Well, dark sky doesn’t expose a min temp so that’s why.
What do you mean with - it just wont read anything else ?

Well, that explains that then. What I mean by not reading anything else, the forecast temp I’m getting is the first one on the list. So it’s 9:30am here, it’s showing the temp for 9am, not the max for the day which is at 12pm.

Oh, I see.
The structure of the different weather platforms seem to differ a lot unfortunately, some weather platforms expose the forecast in days, and some in hours, and some not at all. Their other exposed attributes are also vastly different.

I find this kinda strange, I thought they would have a more unified structure, similar to the media_player domain.

Same issue with the BOM weather component here in Australia. I too have switched over to DarkSky for now. It would be great if we can push data into this component using sensor values instead of the weather component.