Where is a code?
Did you see my post above as working. I had to delete and reinstall and clean the yaml
The config for the wind direction entity has changed.
See the readme on github for details.
literally in the screenshot. Sorry I didn’t bother to put it proper block quoted text as I felt like it was plenty readable.
Thanks, Indeed I have massively overlooked the first line of the description. I do feel like this really should be made a bit more obvious so it jumps into your face that there was a breaking change. It is for sure worth its own headline!
And honestly I am not entirely sure why it was necessary to introduce the breaking change in the first place. In home assistant this code:
wind_direction_entity:
entity: sensor.gw1100a_v2_2_1_wind_direction
is quite equivalent to this code:
wind_direction_entity: sensor.gw1100a_v2_2_1_wind_direction
but it is a newly introduced breaking change in the wind rose card.
Just my 2 cents. Got it working again. Thanks a bunch for your work! 
1 Like
Do you know that people here uses a REAL code for helping - i.e. to paste in a test setup and check what is wrong? Not to mention a fact that in MANY cases (may be not for this particular card) a code displayed in that error windows may be not exactly the real one.
@0xDE4DBEEF
About the breaking change.
You need extra code to support the old en new way to configure the card. This makes the card complex and harder to maintain.
But you’re right, I could’ve made the old way deprecated and remove it in a later version. I learned from this.
In the current version the hours_to_show config is deprecated and wil be removed later. The browser console shows an warning when the old config is used.
But many users will not see this warning, I’m afraid.
If you’re using HACS, the breaking change should be visible in the change logs.
The title has the words ‘breakings changes’ in there for version 1.0.0
Offen the version number indicates when there is a breaking change.
a.b.c
a: breaking/big change
b: feature changes, not breaking
c: bug fixes.
Glad you got it working again.
Version 1.2.1 released.
A bug caused the windrose not to update at the interval times.
Thanks Lou for reporting this issue on GitHub.
Version 1.3.0 released.
New option to hide the windspeed bar(s): hide_windspeed_bar
2 Likes
Version 1.4.0 released.
Currently the width of the block depends on the relative size of the speedrange.
With the new option render_relative_scale set to false (default true), the speedranges are rendered with the same size.
This option is part of the windspeed_entities configuration.
Example:
windspeed_entities:
- entity: sensor.gorredijk_wind_speed
name: Speed
speed_unit: auto
use_statistics: false
render_relative_scale: false
1 Like
I can’t get the bar hidden, what I’m doing wrong?
The bar is on the right
You added this config property:
hide_windspeed_bar: true
Maybe a browser refresh? What card version is printed in the browsers console (F12)?
If above won’t help, please share your card config.
My bar would not hide. Reloaded / Refreshed etc. No difference.
HACS said I had already Version 1.4.0
I redownloaded the HACS card. Voila it works! Thank you for improving all the time
1 Like
With downloading 1.4 the bar is now hidden, thank you
1 Like
Is this a bug with the windspeed bar? The bar auto adjusts the scales it shows when the windspeed_bar_full setting is set to false. With this behavior, I would then expect the color scale size to be at least be proportional to the displayed percentages. In the image shown, why would 54%, the largest percentage, be shown with the smallest color area?
The width of the blocks are relative to the windspeed range size, not the percentage.
It is possible to evenly distribute the blocks with this option: render_relative_scale set to false. See readme on Github.
Maybe you can add an feature request on Github?
I think it’s only useful when speed_range_beaufort is true (is default)
1 Like
That took a while to get working for me 
For others having a blank card:
My issue was the windspeed_entities and speed_unit within was set to auto.
Changing this to my sensors unit (kph) made this work.
type: custom:windrose-card
title: Past 24 hours
data_period:
hours_to_show: 24
max_width: 400
refresh_interval: 60
windspeed_bar_location: bottom
windspeed_bar_full: true
wind_direction_entity:
entity: sensor.weather_station_esp32_station_wind_direction_bearing
direction_unit: degrees
use_statistics: false
direction_compensation: 0
windspeed_entities:
- entity: sensor.weather_station_esp32_station_wind_speed
name: WIndspeed
speed_unit: kph
use_statistics: false
output_speed_unit: kph
input_speed_unit: kph
speed_range_beaufort: false
windrose_draw_north_offset: 0
cardinal_direction_letters: NESW
matching_strategy: direction-first
center_calm_percentage: false
speed_range_max: 50
speed_range_step: 5```
1 Like
Thanks, I missed render_relative_scale in the readme before. However, I don’t see it resizing the blocks in the windspeed bar when I enable it. What do you mean “the blocks are relative to the windspeed range size”? I have Beaufort enabled so would this be to that scale? If yes, and by my pic, those blocks should be getting subsequently bigger then, which is not the case. What am I missing here?
@tom_l would you mind sharing your yaml for your layout. I relly liked it and will do something similiar. 
Thanks!
Hi there, I tried to bring the windrose card up and running, but it fasils.
That is the code from my dashboard:
<
type: custom:windrose-card
title: Past 24 hours
data_period:
hours_to_show: 24
max_width: 400
refresh_interval: 60
windspeed_bar_location: bottom
windspeed_bar_full: true
wind_direction_entity:
entity: sensor.netatmo_basis_windmesser_direction
direction_unit: degrees
use_statistics: false
direction_compensation: 0
windspeed_entities:
- entity: sensor.netatmo_basis_windmesser_wind_strength
name: Windspeed
speed_unit: kph
use_statistics: false
output_speed_unit: kph
input_speed_unit: kph
speed_range_beaufort: false
windrose_draw_north_offset: 0
cardinal_direction_letters: NESW
matching_strategy: direction-first
/>
In the card nothing shows up.
Here the sensors I created for my netatmo wind sensor:
<
sensor:
- platform: history_stats
name: Windgeschwindigkeit_History
entity_id: sensor.netatmo_basis_windmesser_wind_strength
state: “mean”
type: time
#start: ‘{{ today_at() }}’
#end: ‘{{ now() }}’
start: “{{ now().replace(hour=0, minute=0, second=0, microsecond=0) }}”
end: “{{ now() }}” - platform: history_stats
name: Windrichtung_History
entity_id: sensor.netatmo_basis_windmesser_direction
state: “mean”
type: time
#start: ‘{{ today_at() }}’
#end: ‘{{ now() }}’
start: “{{ now().replace(hour=0, minute=0, second=0, microsecond=0) }}”
end: “{{ now() }}”
/>
Could someone give me a hint? currently I do not know where my problem is. Is it in the history stats configuration.yaml or in the windrose-card?
I now updated my configuration.yaml with:
<
recorder:
include:
entities:
- sensor.netatmo_basis_windmesser_direction
- sensor.netatmo_basis_windmesser_wind_strength
purge_keep_days: 30
/>
Will check if that changes something.
Thanks for your feedback!!
