Lovelace Windrose Card

Share your Projects! Dashboards & Frontend
243

Hi,
I added knot as an option the card recognises. It will be in the next release.

And I see 2 feature requests.

Can you add the other one here: https://github.com/aukedejong/lovelace-windrose-card/issues/new?template=Blank+issue

Currently I’m working on entity attribute support. This needs some refactoring, takes longer then expected.

244

Thanks, done Add option to hide the wind direction arrow · Issue #124 · aukedejong/lovelace-windrose-card · GitHub

1 Like
245

I seem to have the same issue as Reflex above. I created a png, named it bg.png. It has 314 by 314 pixels, so it is square. Put it into the same folder as the windrose-card.js, though it is not the “hacsfiles” one - which I can’t find - but config/www/community/. I assumed this should work and the hacsfiles only points to this folder, but it doesn’t work.

Any hint what I can do, maybe how to find and access the “hacsfile” original folder, if this is the issue?

Apart from that - thanks a lot for this wonderful card!
image

246

Hi,
In the browser F12 network tab, can you find the failing bg.png download?
Can you check the url of the download and where it differs from the windrose-card.js download.
The urls should be the same, except for the filename offcourse.

247

Released version 1.14.0

Features:

  • Attribute support for compass, corner info, wind direction and wind speed entities.
  • Improved feedback about configuration errors in the card. Before some error where only reported in the browsers console.
  • Added paragraph about data retention in the readme.
248

Released version 1.15.0
Features:

  • Statistics period can be configured. Long-term statistics can now be used by te card.
  • The windspeed unit can be auto determined for weather entity’s. Reading attribute wind_speed_unit. Fixes #129
  • When the windspeed unit can not be auto determined, an error message will be display on the card. Fixes #129
  • Measurement and match statistics can be logged to the console (F12), set this property to true: log_measurement_counts in data_period.
    In a future release these stats and counts can be displayed on the card.
249

When trying out your max configuration I got to errors one is there is “KNPTS” as wind unit in the yaml, which is easy to correct.
Second is there is “Error: Entity input_number.compass not found”, which seems to be correct cause I never declared an input_number.compass, but I have no clue what should be placed in this input text?.

Another error I get is in this:

  top_right:
    label: Wind direction
    unit: °
    color: red
    entity: sensor.wind_direction_azimuth
    input_unit: degrees
    output_unit: letters

error — s[i] is undefined / with an exclamation mark in front of it.
Error given is strange I only can delete this one by removing this whole section.

250

You can remove the whole compass_direction part.

This is used on for example a boat, so the graph can rotate to correspond with the boats direction.

Other option is to set the auto_rotate config to false.
Then the entity config is not checked.
I changed it to false now in the readme.

I’ll get back to you about the last error.

The easiest way to start using this card, is to just use the generated config, when you add the card.

251

I can not reproduce the last error.
The entity defined in there, what state does it use? Degrees or letters? Should be degrees with this configuration.

252

Release version 1.15.1

Fixes:

  • Config check for conflicting speed range configurations
  • When the average wind speed is zero, first dynamic speed range was not selected.
  • Readme errors corrected
  • When using log_measurement_counts, also log average wind speed.

Thanks to il77781

253

Unsure if the latest update is the cause but my headings at the top of the cards are over flowing the card.

image
image1232×810 167 KB

254

Hello all!

I could not find how to send a feature request here, sorry.
My feature sugestion is to implement a “hear map” of wind direction… Would be nice!
Thank you!
Alex, Brazil

255

Hello. This card is a heat map. Do you have an example?

1 Like
256

Could be the update, I’ll check.
Can you share your card config?

Maybe best to discuss this in a github issue. Is that an option for you?

257

Released version 1.15.2

Fix: top overflow error.
Thanks @Chykan and @gedger for reporting this issue.

1 Like