Console Error - No matching speed found for direction. about lovelace-windrose-card HOT 9 CLOSED

Hmm, your speed entity only gets updated twice an hour? That is not very often.

I think it best to wait for the next version and try using HA statistics.
Matching code is rewritten.

Now I'm also thinking about an other matching strategy.
Something like this: for every direction measurement, look back in time for the last speed measurement. No matter how long ago, within the timeframe, the last measured one should be the one used.
Automatic select the direction or speed as leading, which one has the most measurements.

Thanks for letting me know, with these issues, I can improve things.

from lovelace-windrose-card.

Nieuwe version with better matching logic is released.

Version 1.0.0

It has breaking changes, see you need to update the configuration. Easiest is just to add card and modify the generated configuration.

from lovelace-windrose-card.

This means that the direction and speed measurements are not close enough in time. Default is 1second before or after.

You can try to increase direction_speed_time_diff config value.
Changing the matching-strategy can also help.

You don't see anything in the windrose graph?

from lovelace-windrose-card.

I was getting results in the windrose, but also tonnes of console errors. I've changed my config, now I'm only getting a handful of errors. I played with the settings a bit, this was the best I could do.

type: custom:windrose-card
title: Wind Direction
max_width: 400
windspeed_bar_full: true
wind_direction_entity: sensor.wind_bearing
wind_direction_unit: degrees
windspeed_entities:
  - entity: sensor.wind_speed
    name: Average
input_speed_unit: kph
output_speed_unit: kph
direction_speed_time_diff: 10
matching_strategy: speed-first

Very calm right now, so this looks right.

from lovelace-windrose-card.

Got the same issue as @jazzyisj but the changes suggested doesn't work for me.
Is there anywhere in HA I can check what's going on?

type: custom:windrose-card
hours_to_show: 12
max_width: 400
refresh_interval: 60
windspeed_bar_location: bottom
windspeed_bar_full: false
wind_direction_entity: sensor.ws3500_wind_direction
windspeed_entities:
  - entity: sensor.ws3500_wind_speed
    name: Medelvind
  - entity: sensor.easyweatherpro_v5_1_1_max_daily_gust
    name: Byvind
wind_direction_unit: degrees
input_speed_unit: mps
output_speed_unit: mps
speed_range_step: 5
speed_range_max: 25
direction_compensation: 0
windrose_draw_north_offset: 0
cardinal_direction_letters: NESW
matching_strategy: speed-first
direction_speed_time_diff: 180
speed_ranges:
  - from_value: 0
    color: rgb(0,255,0)
  - from_value: 8
    color: yellow
  - from_value: 16
    color: hsl(200, 100%, 60%)
  - from_value: 20
    color: orange
  - from_value: 24
    color: red

from lovelace-windrose-card.

@tangix Fooling around with the parameters I was able to greatly reduce the amount of errors in the console, but not eliminate them all together.

from lovelace-windrose-card.

Hi. I'm working on a new version with breaking changes. It support statistics data and I think it should fix these matching problems you have.
I also changed the logging, showing only one log entry about the matching results.

I'm planning to release somewhere next week.

You understand why you get these errors?

from lovelace-windrose-card.

You understand why you get these errors?

No. I get local weather data from a WS-3500 station that sends to Home Assistant. It looks like the data is not sent at the same time as shown:

The direction is sent much more often than wind speed:

from lovelace-windrose-card.

Resolved with v1.0.0. Thank you!

from lovelace-windrose-card.