Weather forecast plot (meta and nested attributes)
#213
Replies: 6 comments 17 replies
-
|
This is awesome! I use it to display the forecast for three different weather stations since they're all so different. I have temperature, humidity, dew point and precipitation probability. (I know, not the prettiest way to display, but I like it).
Question. What will become of this with the new weather entities that no longer have a "forecast" attribute, and instead needs to call a service? Any known workaround? |
Beta Was this translation helpful? Give feedback.
-
|
Wow, that's really cool! |
Beta Was this translation helpful? Give feedback.
-
|
I guess you should ask in the Home Assistant forums for a better answer |
Beta Was this translation helpful? Give feedback.
-
|
Hi @dbuezas the pirate weather integration provides individual sensors for forecast - the sensor name then appended with _1d, _2d etc up to _7d and _1h, _2h etc up to _48h. I feel this should be easy to map into a forecast in plotly but the filter fn coding is beyond me. Do you have any insight how to vary your above example please? |
Beta Was this translation helpful? Give feedback.
-
|
Here's an idea: I suggest you read the docs section about filters and $fn / $ex first. Wish you luck! |
Beta Was this translation helpful? Give feedback.
-
|
Here's what I've done In configuration.yaml - trigger:
- platform: state
entity_id:
- weather.weather_channel
action:
- service: weather.get_forecasts
data:
type: hourly
target:
entity_id: weather.weather_channel
response_variable: hourlyIn the chart card - entity: sensor.weather_channel_forecast_hourly
showlegend: false
legendgroup: 1
line:
color: '#ffcfb2'
width: 1
unit_of_measurement: °F
filters:
- fn: |-
({ meta, vars }) => ({
xs: [...meta.forecast.map(({ datetime }) => new Date(datetime))],
ys: [...meta.forecast.map(({ temperature }) => temperature)],
})
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks both for your pointers! |
Beta Was this translation helpful? Give feedback.
-
|
Very cool! Here's a way to reduce the yaml size a bit: - entity: sensor.my_weather_temperature_0h
filters:
- fn: "({xs, ys, vars}) => { vars.xs=[]; vars.ys=[]; }"
- fn: "({xs, ys, vars}) => { vars.xs.push(xs.at(-1)); vars.ys.push(ys.at(-1)); }"
- entity: sensor.my_weather_temperature_1h
time_offset: 1h
filters:
- fn: "({xs, ys, vars}) => { vars.xs.push(xs.at(-1)); vars.ys.push(ys.at(-1)); }"
- entity: sensor.my_weather_temperature_2h
time_offset: 2h
filters:
- fn: "({xs, ys, vars}) => { vars.xs.push(xs.at(-1)); vars.ys.push(ys.at(-1)); }"
#... etc
- entity: ''
internal: false
...
filters:
- fn: "({vars}) => vars" |
Beta Was this translation helpful? Give feedback.
-
|
I've got @Arrow-hub's method of forecast working - I want to plot 120 hourly datapoints into the future so even with @dbuezas's streamlined version of my code it gets a bit too chunky.
I've tried all variations of map_x and resample and !=null but to no avail. Since I want to plot vars.solar.ys onto vars.cloud.xs, I have made a rough equation that takes hass states of the various sun entities to give a y value with the only variable changing per data point the timestamp of the x value, but how would I plot that array for 120 datapoints provided by xs: [...meta.timelines[0].intervals.map(({ startTime }) => new Date(startTime))]? This is the code I would use to make y, and hopefully include in fn: ys:: |
Beta Was this translation helpful? Give feedback.
-
|
I'm trying to plot a forecast of 'sunlight'*'sun's elevation' to get the strength of the sun hourly over the next 5 days. This works well until I drag plotly along the x-axis, which seems to throw the x-alignments of the new forecast out of sync as older 'suns elevation' sensor data is loaded. So for example if I drag the plot 12hours past, now the original plots remain accurate, though the time_offset elevation sensor now loads older data into that 12 hour history, while the cloud cover forecast remains just a forecast (not filling in the old 12 hours). But the vars product of the two sensors I want to show now has this 12 hour difference between the elevation and the cloud cover. How can I ensure the two sensor x values remain in sync? I have tried many possible solutions but no luck yet. |
Beta Was this translation helpful? Give feedback.
-
|
is data available for all sensors in the past (when you scroll)? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I managed to sort it. Another unrelated question though 😅 my forecast is a work in progress and I use a fill: tonexty that looks great:
but I want to use rangebreaks as I'm only interested in viewing daytime hours.
|
Beta Was this translation helpful? Give feedback.
-
|
Mmmm that's a plotly limitation. You may be able to work around that by adding another trace with a transparent line and without rangebreaks. |
Beta Was this translation helpful? Give feedback.
-
|
I got it! If anyone else finds this looking for answers. All it took was connectgaps: true.
|
Beta Was this translation helpful? Give feedback.
-
|
hi! Today I've updated home assistant to latest: And now I have an error in all the cards that I had with a forecast line on them... I receive this ERROR: Do you have the same issue? do you know how to solve it? |
Beta Was this translation helpful? Give feedback.
-
|
The only thing that comes to mind is to use the hacs object directly to hack a call. |
Beta Was this translation helpful? Give feedback.
-
|
Same error here, the plotly forecast card is so useful, I hope someone will provide a solution ! |
Beta Was this translation helpful? Give feedback.
-
|
You'll need a template sensor and an automation as the home assistant docs recommend |
Beta Was this translation helpful? Give feedback.
-
|
Got the solution here; |
Beta Was this translation helpful? Give feedback.
-
|
Added it to the post |
Beta Was this translation helpful? Give feedback.
-
Update
In newer HA versions you'll need a template sensor since the forecast attributes are not stored automatically.
Beta Was this translation helpful? Give feedback.
All reactions