Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wind gust no entity can be selected #94

Open
2 tasks done
ZTHawk opened this issue Jul 11, 2023 · 3 comments
Open
2 tasks done

Wind gust no entity can be selected #94

ZTHawk opened this issue Jul 11, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@ZTHawk
Copy link

ZTHawk commented Jul 11, 2023

Checklist:

  • I updated to the latest version available
  • I cleared the cache of my browser

Release with the issue:
1.0.5

Browser and Operating System:
Windows 10
Firefox (latest)

Description of problem:

Wind gust is not displayed and no weather entity can be used from the dropdown list.
I use the Weather forecast from met.no.
The wind gust is available:
grafik
I tried to add it manually to YAML
entity_wind_gust: weather.home but with no success.
grafik

@ZTHawk ZTHawk added the bug Something isn't working label Jul 11, 2023
@alexdelprete
Copy link

alexdelprete commented Sep 14, 2023

The wind gust is available

From the screenshot you posted, it's available as an attribute of an entity, not as an entity. That's why you can't pick it.

But you can easily create a template sensor in HA, something like this (replace sensor.metno with the name of the real sensor you're using):

template:
  - sensor:
    - name: "metno wind gust speed"
      unique_id: metno_wind_gust_speed
      device_class: wind_speed
      state_class: measurement
      unit_of_measurement: km/h
      state: '{{ state_attr('sensor.metno', 'wind_gust_speed') }}'

Once you reload the template sensors (or restart HA), you'll have a sensor.metno_wind_gust_speed that you can pick from the listbox of the card.

You can use the same approach for all the attributes shown in the screenshot of your OP (wind_bearing, etc.). It would be cool if the dev would let users pick entity AND attribute, so there would be no need to create template sensors.

Hope it helps. :)

@ZTHawk
Copy link
Author

ZTHawk commented Sep 14, 2023

Hello,
yes it is available as an attribute, but the same goes to all the other properties. They are only available as attributes and are used correctly.

entity_forecast_icon: weather.home
entity_forecast_icon_1: weather.home
entity_forecast_max: weather.home
entity_forecast_max_1: weather.home
entity_forecast_min: weather.home
entity_forecast_min_1: weather.home
entity_humidity: weather.home
entity_pop: weather.home
entity_pop_1: weather.home
entity_pos: weather.home
entity_pos_1: weather.home
entity_pressure: weather.home
entity_summary_1: weather.home
entity_sun: sun.sun
entity_temperature: weather.home
entity_visibility: weather.home
entity_wind_bearing: weather.home
entity_wind_gust: weather.home
entity_wind_speed: weather.home

As you can see I have only two entities: weather.home and sun.sun. All required info is extracted from the attributes except wind gust.
So I prefeer this to be fixed instead of creating a new sensor.

@alexdelprete
Copy link

That's interesting: I fed specific sensors from my weather stations, I used the weather entity only for forecast ones.

I agree, it would be better if it looked in the attributes automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants