-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Comments
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 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 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. :) |
Hello,
As you can see I have only two entities: |
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. |
Checklist:
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:
I tried to add it manually to YAML
entity_wind_gust: weather.home
but with no success.The text was updated successfully, but these errors were encountered: