Thanks Auke. I thought I was keeping up with the changes.
I have fixed the depreciated options but I think the real fix was changing the matching strategy to “full-time”. This particular location only updates every 10 minutes at most (both direction and speed), often a lot less, and I think that was what was skewing the output when using “direction-first”.
Finally implemented a feature requested back in 2023. It was a big one, needed a lot of code changes.
If you encounter bugs, please let know by reporting a github issue.
Feature:
Show current wind speed arrow on the legend bars, implements #49
Add this config to a windspeed entity block: current_speed_arrow: true
Fixes:
When not showing all speed ranges in the legend bar (windspeed_bar_full: false), render_relative_scale did not work.
This is great, I just implemented it! Is there any way to have a setting to tell it to appear on the other side of the bar so that it does not sometimes cover the label?
Example (I would love it if the arrows were on the other side of the bar pointing upwards!):
@KruseLuds
The size of the percentages on the rose configurable. That can be added.
I’m not sure it’s a feature request yet. Can you add it on GitHub?
@maurizio53
This option is used by people on for example a boat.
The windrose will rotate depending on the heading of the boat.
About the input_number, I’m using a helper, because I don’t have a real compass available in Home Assistant.
You can create helpers in Settings > Devices & services > Tab: Helpers.
Sorry for the shorts time since the previous release. I think it’s important to get this change public, because of the new HA version 2025.4
Features:
Hold action support. Fixes #146
Support for new state_class for directional sensors.
Since HA 2025.4 the new state class measurement_angle is introduced.
With this change we have long term statistics (LTS) for wind direction sensors.
Looks like this LTS data needs to build up, before you get any data.
Hi,
I had a look at your previous messages. You want to use a weather entity right?
You can do that now, since the card has attribute support. No need to create template entities anymore.