You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that the current code expects the attribute wind_bearing in the forecast to be a numeric bearing in degrees.
The Home Assistant documentation offers two alternatives to weather forecast integrations - either numeric degrees or a string 1-3 chars representing direction (e.g. NNW).
Name
Type
Description
wind_bearing
float or string
The current wind bearing in azimuth angle (degrees) or 1-3 letter cardinal direction.
This second format does not appear to be supported. Can it be?
Excellent bug report! Thank you so much for these details. I'll look at this when I have time -- probably later this week. Contributions welcome if someone else gets to it first.
Thanks! Working for me. Shame the wind barb display option isn't available in this circumstance but great to have the directions displayed as text now.
Thanks for confirming that the fix works. Ya, the wind barb wouldn't be accurate anyway cause the cardinal directions are so imprecise. I figured it was better to block that combination rather than showing misleading info.
It appears that the current code expects the attribute wind_bearing in the forecast to be a numeric bearing in degrees.
The Home Assistant documentation offers two alternatives to weather forecast integrations - either numeric degrees or a string 1-3 chars representing direction (e.g. NNW).
This second format does not appear to be supported. Can it be?
One example that outputs strings is the Australian 'Bureau of Meteorology' custom integration available through HACS, which puts uppercase directions in wind_bearing (e.g. SSE, W, NE etc).
The text was updated successfully, but these errors were encountered: