The data. They list all the endpoints you can use
Oh, I understand (but don’t need those). I’m after a developer token since I don’t own a station myself.
The data is available via their public website, but I cannot login to get a token.
Strange. I just tried the developer key you mentioned on the official swagger and it works fine for me.
You need to know the ID of a Station AND the person owning this station must have it set to Public, else it won’t work.
Thought I would post here as I have weird issue with the solar radiation sensor that impacts both the core integration by @jeeftor and the cloud integration by @briis.
See history below for solar radiation. Notice how ‘perfect’ the data is today. It’s too perfect. I see this happen every few days.
The strange thing is there is something weird with the data on the days I see this perfect pattern. I have only noticed this issue since trying to create a sensor that calculates total daily solar radiation.
Chart below shows solar radiation for last 3 days. Today the data is is a perfect parabola.
This with my total for the day overlayed. You can see total is not increasing like it should
All I can think is if you went off line the could will then “guess” what stuff should be I think ???
Are you able to also run the local integration as well? You could compare local to cloud
I have exactly the same on cloud and local. Good that the data matches but does not help with the issue.
I don’t think it has anything to do with online/offline as I have this same pattern regularly.
I have only noticed this issue since I created a utility meter helper sensor to calculate total daily solar radiation and it’s not working on days with when the data looks weird.
FYI - I am discussing this with @briis via a github issue/feature request here - didn’t want you to think i’m cross posting.
I do get this error in my log related to the utility meter sensor - not sure if this is helpful…
Entity sensor.solar_radiation_daily (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) is using state class 'total_increasing' which is impossible considering device class ('irradiance') it is using; expected None or one of 'measurement'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+utility_meter%22
I’ve got a new bug fix that was pushed - not sure when it comes in.
Hi @jeeftor,
how can the weather forecast data be used in an automation?
For example, I would like to close my shutters at 11 a.m. if the max. daily temperature is going to be above 30 °C.
Did I miss something?
I’m on my phone right now, so I don’t have the computer in front of me, but the forecast object itself has various hourly and daily attributes.
If you really wanna dig through a blueprint that I wrote that uses the hourly forecast so you can look through the following link
But I think you don’t actually care about the forecast you just care that if the time is after 11 AM and it’s hotter than 30 C close the blinds, right?
Trigger time - 11am.
Action:
service call: weather.get_forecasts using the weatherflow entity and choosing the daily forecast type, set the response variable to forecast.
If action, with a template action.
{{ forecast['weather.weatherflow']['forecast'][0]['temperature']|float(0) > 30 }}
This will be true if the max temp today is over 30, and thus the actions that follow will be executed, but if the max temp is not over 30, then the if will end and either the automation will end doing nothing, or if you put in an else then you can have something else happen instead. Note the assumption in that bit of code is that the weather entity is called weather.weatherflow - but you will need to change that to whatever your entity is called.
No, it’s a kind of prevention. I want to close the blinds before it reaches 30 °C.
@jeeftor and @mobile.andrew.jones, thank you very much for your information, I will have a look at both.
Edit
@jeeftor, you use the old weatherflow hass integration in the blueprint, right?
With this integration it was no problem to fetch the forecast data, but I’m not able to fetch forecast data from the WeatherFlow Cloud core integration.
It should work -
trigger:
- platform: time_pattern
seconds: /5
- platform: state
entity_id: !input forecast_var
id: Changes
enabled: true
condition: []
action:
- service: weather.get_forecasts
target:
entity_id: "{{forecast_var}}"
data:
type: hourly
response_variable: forecast_response
It is using the new procedure to get the forecast data.
Have you updated Home Assistant as the weatherflow cloud integration was failing on 2024.6.3 because of a missing key (air_density)
I’m on 2024.6.4.
My problem is, that I have no YAML knowledge. With the old WeatherFlow integration it was no problem for me. But now I don’t understand it because the entities for the prediction don’t exist.
Anyway, many thanks for your support!