jaydeethree/home-assistant-weatherdotcom

Home Assistant custom component/integration for Weather.com

Home-Assistant-Weather.com

Home Assistant custom integration for Weather.com. Includes a native Home Assistant Weather Entity and a variety of weather sensors.

This is a fork of the excellent wundergroundpws integration by @cytech - if you find this software useful, feel free to make a donation to them.

---

Installation Prerequisites

Please review the minimum requirements below to determine whether you will be able to install and use the software.

• This integration requires Home Assistant Version 2023.9 or greater
• A Weather.com API Key is required (see below for how to get this)

Back to top

Weather.com API Key

1. Open https://www.wunderground.com (Wunderground is owned by Weather.com and uses some of the Weather.com APIs)
2. View the page source in your browser.
3. In the source, search for "apiKey" and copy/paste that into the integration

Important notes:

• It seems like Wunderground may provide different API keys depending on which country you are located in, and that the API keys for some countries may not be compatible with this integration. This integration has only been tested with the US API key which ends in 96f525 - if your API key isn't working, you may need to connect to a US VPN to retrieve the US API key.
• It also seems like Weather.com blocks traffic from certain countries. If this integration does not work for you, make sure that you can access Weather.com in your browser.
• Wunderground PWS (Personal Weather Station) API Keys will not work for this integration, as they do not have access to the Weather.com APIs that this integration uses.
• While there have been no reports of API keys being blocked or changing over time, it's always possible that Weather.com will eventually block them. If that happens you will need to find an API key from another source.

Back to top

Installation

This integration is available in HACS, so just install it from there and then:

1. In Home Assistant Settings, select DEVICES & SERVICES, then ADD INTEGRATION.
2. Select the "Weather.com" integration.
3. Enter your Weather.com API key and submit.

Back to top

Sensors Created By This Integration

The following Weather.com data is available in the weather.<LOCATION_NAME> entity:

Current conditions:

• Condition (icon)
• Temperature
• Barometric pressure
• Wind speed
• Wind bearing (cardinal direction)
• Visibility

Forecast (daily and hourly):

• Date/time of forecast
• Temperature (high)
• Temperature (low)
• Condition (icon)
• Precipitation quantity
• Precipitation probability
• Wind speed
• Wind bearing (cardinal direction)

To access these values in automations, scripts, etc. you will need to create triggered template sensors for them. This post on the Home Assistant forums provides details about how to do that.

In addition to the Weather entity, these additional sensors will be created by this integration:

• sensor.<LOCATION_NAME>_cloud_ceiling - distance to the lowest cloud layer, or 0 if there are no clouds
• sensor.<LOCATION_NAME>_cloud_cover_phrase - a description of the current cloud cover, e.g. "Clear" or "Mostly Cloudy"
• sensor.<LOCATION_NAME>_dewpoint - the current dew point
• sensor.<LOCATION_NAME>_heat_index - the current heat index, which is what the current temperature "feels like" when combined with the current humidity
• sensor.<LOCATION_NAME>_latitude - the latitude that is configured for this location
• sensor.<LOCATION_NAME>_local_observation_time - the time that the Weather.com data was generated
• sensor.<LOCATION_NAME>_longitude - the longitude that is configured for this location
• sensor.<LOCATION_NAME>_precipitation_last_hour - the quantity of precipitation in the last hour
• sensor.<LOCATION_NAME>_precipitation_last_6_hours - the quantity of precipitation in the last 6 hours
• sensor.<LOCATION_NAME>_precipitation_last_24_hours - the quantity of precipitation in the last 24 hours
• sensor.<LOCATION_NAME>_pressure - the current barometric pressure
• sensor.<LOCATION_NAME>_pressure_tendency_trend - the current trend for barometric pressure, e.g. "Rising" or "Falling"
• sensor.<LOCATION_NAME>_relative_humidity - the current relative humidity
• sensor.<LOCATION_NAME>_temperature - the current temperature
• sensor.<LOCATION_NAME>_temperature_feels_like - what the current temperature "feels like" when combined with the current heat index and wind chill
• sensor.<LOCATION_NAME>_uv_index - the current UV index, ranging from 0 (very low) to 10 (very high)
• sensor.<LOCATION_NAME>_weather_description - the current weather description, e.g. "Freezing Rain" or "Scattered Showers"
• sensor.<LOCATION_NAME>_wind_chill - the current wind chill, which is what the current temperature "feels like" when combined with the current wind
• sensor.<LOCATION_NAME>_wind_direction_cardinal - the current cardinal wind direction - for example: North
• sensor.<LOCATION_NAME>_wind_direction_degrees - the current cardinal wind direction in degrees
• sensor.<LOCATION_NAME>_wind_gust - the current wind gust speed
• sensor.<LOCATION_NAME>_wind_speed - the current wind speed

All of the data listed above will be updated every 20 minutes.

Additional details about the API are available here.

Back to top

Localization

Sensor "friendly names" are set via translation files.
Weather.com translation files are located in the 'weatherdotcom/weather_translations' directory. Files were translated, using 'en.json' as the base, via https://translate.i18next.com.
Translations only use the base language code and not the variant (i.e. zh-CN/zh-HK/zh-TW uses zh).
The default is en-US (translations/en.json) if the lang: option is not set in the Weather.com config.
If lang: is set (i.e. lang: de-DE), then the translations/de.json file is loaded, and the Weather.com API is queried with de-DE.
The translation file applies to all sensor friendly names.
Available lang: options are:

'am-ET', 'ar-AE', 'az-AZ', 'bg-BG', 'bn-BD', 'bn-IN', 'bs-BA', 'ca-ES', 'cs-CZ', 'da-DK', 'de-DE', 'el-GR', 'en-GB',
'en-IN', 'en-US', 'es-AR', 'es-ES', 'es-LA', 'es-MX', 'es-UN', 'es-US', 'et-EE', 'fa-IR', 'fi-FI', 'fr-CA', 'fr-FR',
'gu-IN', 'he-IL', 'hi-IN', 'hr-HR', 'hu-HU', 'in-ID', 'is-IS', 'it-IT', 'iw-IL', 'ja-JP', 'jv-ID', 'ka-GE', 'kk-KZ',
'km-KH', 'kn-IN', 'ko-KR', 'lo-LA', 'lt-LT', 'lv-LV', 'mk-MK', 'mn-MN', 'mr-IN', 'ms-MY', 'my-MM', 'ne-IN', 'ne-NP',
'nl-NL', 'no-NO', 'om-ET', 'pa-IN', 'pa-PK', 'pl-PL', 'pt-BR', 'pt-PT', 'ro-RO', 'ru-RU', 'si-LK', 'sk-SK', 'sl-SI',
'sq-AL', 'sr-BA', 'sr-ME', 'sr-RS', 'sv-SE', 'sw-KE', 'ta-IN', 'ta-LK', 'te-IN', 'ti-ER', 'ti-ET', 'tg-TJ', 'th-TH',
'tk-TM', 'tl-PH', 'tr-TR', 'uk-UA', 'ur-PK', 'uz-UZ', 'vi-VN', 'zh-CN', 'zh-HK', 'zh-TW'

Weather Entity translations are handled by Home Assistant and configured under the User -> Language setting.

Back to top

home-assistant-weatherdotcom's Issues

[BUG] Entity sensor.home_cloud_ceiling (<class 'custom_components.weatherdotcom.sensor.WeatherSensor'>) is using native unit of measurement '' which is not a valid unit for the device class ('distance') it is using

When starting home assistant, the following message is logged:

2023-10-31 16:50:04.489 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.home_cloud_ceiling (<class 'custom_components.weatherdotcom.sensor.WeatherSensor'>) is using native unit of measurement '' which is not a valid unit for the device class ('distance') it is using; expected one of ['yd', 'km', 'in', 'cm', 'mm', 'm', 'mi', 'ft']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/jaydeethree/Home-Assistant-weatherdotcom/issues/

[Feature Request] Add additional sensors from the API

I am requesting a few sensors be added to this integration that are part of the weather.com API:
Current Condition
pressureTendencyTrend: Pressure Tendency
cloudCeiling: Cloud Ceiling
Forecast
narrative: I suggest this be implemented similar to the official AccuWeather entity in which there are sensors named "Weather Description 0d day" "Weather Description 0d night" "Weather Description 1d day" and so on.
thunderCategory: Chance of Thunderstorms, could be enumerated like Weather Description

Forecast API is no longer working

Creating a bug to track this - about 9 hours ago the forecast API used by this integration stopped working. From quickly looking at this I believe it's a MIME type issue, as the forecast API now returns a content type of application/octet-stream instead of application/json; charset=UTF-8. It's unclear if this change is intentional or not, but my guess is that it was done on accident and will be fixed eventually.

Air quaility entity + local alerts

would it possibile to add an entity for air quality indexes and/or local alerts?

[FR] Service to change latitude/longitude

I would like to be able to change the latitude/longitude of the weather entity through some service or even by hand. Currently, it is only possible to delete and then recreate an integration instance.

The use case is the following: I would like to have a second weather entity (in addition to my home one) which would get the forecast/conditions for the location where I happen to be e.g. on holiday. I would swap out the source for the forecast from my dashboard and I would be able to see the weather where I happen to be rather than at home.

As a secondary thing -- it would be great if the weather entity, or some other sensor, contained the current latitude/longitude of the current location, so that I could look up the city name programmatically using some reverse geo-location..

This is probably a bit against the philosophy of HA, since history of these sensors would be a splicing of multiple locations, but I think it would be a useful feature.

'Unknown Error' during integration setup

I'm trying to install this integration but am getting an error when trying to submit the settings (i.e. API key, location etc.).

This is what is displayed:

I am following the instructions to grab the API key from the wunderground.com page.

The log contains the following:

This error originated from a custom integration.

Logger: custom_components.weatherdotcom.config_flow
Source: custom_components/weatherdotcom/config_flow.py:68
Integration: Weather.com (documentation, issues)
First occurred: 08:42:15 (4 occurrences)
Last logged: 08:54:15

Weather.com config responded with HTTP error 400: Bad Request

I have also tried truncating the location coordinates (to just 2 decimal places) but still get the same error.

Running Home Assistant Container 2023.5.4

Error doing job: Task exception was never retrieved

I have been getting this error in HA log since I have updated to the latest version.

Appreciate if anyone can advise the issue.

Logger: homeassistant
Source: custom_components/weatherdotcom/sensor.py:126
Integration: Weather.com (documentation, issues)
First occurred: 12:04:27 AM (57 occurrences)
Last logged: 6:44:42 PM

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 243, in _handle_refresh_interval
await self._async_refresh(log_failures=True, scheduled=True)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 399, in _async_refresh
self.async_update_listeners()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 182, in async_update_listeners
update_callback()
File "/config/custom_components/weatherdotcom/sensor.py", line 110, in _handle_coordinator_update
self._sensor_data = _get_sensor_data(
^^^^^^^^^^^^^^^^^
File "/config/custom_components/weatherdotcom/sensor.py", line 126, in _get_sensor_data
return sensors[RESULTS_CURRENT][kind]
~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
KeyError: 'latitude'

Unknown Error after inserting the apiKey

Hi,
I get this error:

[Feature Request] Add additional Air Quality sensor

Hello,
Can you add one more sensor - Air Quality (AQI)?

No current cloud coverage (only in forecast)

I switched over to this integration from AccuWeather and it's really nice. The only entity I still use from AccuWeather is cloud coverage.

It looks like this integration only provides cloud coverage in the forecast. Would it be possible to have an entity that provides the current cloud coverage? Or have it as an attribute on the weather entity?

Thanks again for your work on this integration :)

Blocking Call to Open inside Event Loop

A blocking call to open was detected inside the event loop by the custom integration 'weatherdotcom'. This issue occurs in the file coordinator.py at line 232 within the custom component 'weatherdotcom'. The problem arises when attempting to load JSON data from a file, which results in the event loop being blocked.

Steps to Reproduce:

Install and configure the 'weatherdotcom' custom integration.
Start the Home Assistant service.
Observe the log for errors related to blocking calls within the event loop.

Expected Behavior:
The custom integration should handle file operations asynchronously to avoid blocking the event loop, ensuring smooth and responsive operation.

Actual Behavior:
The integration attempts to open and read a JSON file synchronously, which blocks the event loop and causes potential delays or disruptions in the Home Assistant's performance.

Error Log:

Logger: homeassistant.util.loop
Source: util/loop.py:84
First occurred: 14:24:55 (1 occurrences)
Last logged: 14:24:55

Detected blocking call to open inside the event loop by custom integration 'weatherdotcom' at custom_components/weatherdotcom/coordinator.py, line 232: tfiledata = json.load_json(f'{tfiledir}{tfilename}.json') (offender: /usr/src/homeassistant/homeassistant/util/json.py, line 78: with open(filename, mode="rb") as fdesc:), please create a bug report at https://github.com/jaydeethree/Home-Assistant-weatherdotcom/issues/
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component
    result = await _async_setup_component(hass, domain, config)
  File "/usr/src/homeassistant/homeassistant/setup.py", line 447, in _async_setup_component
    await asyncio.gather(
  File "/usr/src/homeassistant/homeassistant/setup.py", line 449, in <genexpr>
    create_eager_task(
  File "/usr/src/homeassistant/homeassistant/util/async_.py", line 37, in create_eager_task
    return Task(coro, loop=loop, name=name, eager_start=True)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 742, in async_setup_locked
    await self.async_setup(hass, integration=integration)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/config/custom_components/weatherdotcom/__init__.py", line 48, in async_setup_entry
    weathercoordinator = WeatherUpdateCoordinator(hass, config)
  File "/config/custom_components/weatherdotcom/coordinator.py", line 84, in __init__
    self._tranfile = self.get_tran_file()
  File "/config/custom_components/weatherdotcom/coordinator.py", line 232, in get_tran_file
    tfiledata = json.load_json(f'{tfiledir}{tfilename}.json')

Possible Solution:
Refactor the code to use asynchronous file I/O operations to load the JSON data, thereby preventing the event loop from being blocked.

Environment:

Core: 2024.6.2
Supervisor: 2024.06.0
Operating System: 12.3
Frontend: 20240610.0
Integration Version: 1.1.6

Additional Information:
This issue impacts the performance of the Home Assistant due to the synchronous nature of the file operation within the event loop. Addressing this will improve the responsiveness and reliability of the integration.

Please let me know if further information is required to resolve this issue.

APIkey from Weather.com is required instead of Weatherunderground

If you use the APIkey from weatherunderground.com the integration states that the APIkey is invalid. You should use the APIkey from weather.com

Fix install docs now that it's a HACS default integration

Looks like this was added as a default to HACS so the README shouldn't say it needs to be installed as a custom repo.

Excited to try this out! Weather.com has the most accurate and detailed forecasts from what I've seen.

some weather descriptions are too long

Hi,
this is more of a suggestion than an issue in that some of the weather descriptions are quite long.
e.g. "Showers in the Vicinity" could be "Local Showers"

API key

Hi
I am from POLAND and i have a problem with API Key. Still get info Invalid API Key. Also generate this api by connect by Free VPN to USA and then go to https://www.wunderground.com/ and generate and still is invalid. Can you help me please?

Error during weather."location" entity setup

Hi, not sure if it is related to home assistant upgrade from 2023.08.3 to 2023.9.0 I just did, but the following error is now occurring at startup. The 2 weather."location" and weather."location"_hourly are missing. Other sensor entities are available.

There are 4 occurrences in my log since I tried to restart the integration once.

Thanks anyway for this integration!

Logger: homeassistant.components.weather
Source: custom_components/weatherdotcom/weather.py:125
Integration: Météo (documentation, issues)
First occurred: 00:20:59 (4 occurrences)
Last logged: 06:49:33

Error adding entities for domain weather with platform weatherdotcom
Error while setting up weatherdotcom platform for weather
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 507, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 752, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1002, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 730, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 830, in _async_write_ha_state
state, attr = self._async_generate_attributes()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 773, in _async_generate_attributes
attr.update(self.state_attributes or {})
^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/weather/init.py", line 723, in state_attributes
from_unit = self.native_visibility_unit or self._default_visibility_unit
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/weatherdotcom/weather.py", line 125, in native_visibility_unit
return self._attr_visibility_unit
^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'WeatherDotComDaily' object has no attribute '_attr_visibility_unit'

Weather description

Hello,

In case of Sunny weather, the sensor weather_description in the Netherlands displays "beautiful" ("mooi" in Dutch), where "Sunny" ("Zonnig"in Dutch) seems more appropriate. Is this configurable somewhere?

Regards,

Ronald

Implement AirQuality

It should be possible to implement air quality sensors within this documentation? (not tested)
https://docs.google.com/document/d/1rcYHmIaGKtiINuEPJXGMWU5OEntPf2i0U8BBO8clmtQ/edit

Data loss after HA upgrade

Hi, with the latest HA update I lose the forecast, for now I solved it by creating an automation that reloads the service every 10 minutes.

[FR] Add support for zone or device_tracker entity

Allow the option to provide a device_tracker or zone entity instead of lat long at setup. The latitude and longitude of the device/zone will be used instead of it being hardcoded into the integration settings, allowing for the location of the weather to change with a zone or device. Similar to the nws_alerts integration

UV index and a few other conditons in the forecast

Hi,

In 1.1.5 you filled out all the possible fields in the current conditions weather entity.

Would it be possible for you to do the same for the forecasts? The TWC forecast API seems to provide data for all the possible HA forecast attributes. The missing ones are:

• humidity: relativeHumidity
• native_apparent_temperature: temperatureFeelsLike
• native_dew_point: temperatureDewPoint
• native_pressure: pressureMeanSeaLevel
• native_wind_gust_speed: windGust
• uv_index: uvIndex

The only comment/complication is that the pressure in the forecast is only at sea level, while in the current conditions you pick up the pressureAltimeter key which is actually observed at ground level. If you wanted to get technical, this is a simple conversion for any realistic situation, which is given by the formula for P from here

The problem then would be getting the elevation of the location, but in principle it is possible from somewhere like open-elevation

Anyway, thanks for creating this. The richness of the data has really made many things possible that until now I've been kludging from multiple sources.

License

Which license is this work licensed under?
I'd wish to create a fork for another weather provider, but without a license I cannot proceed. You can choose one here: https://choosealicense.com/

Check Weather.com API ('unexpected character: line 1 column 1 (char 0)',)

Might not be related, but stopped working after some HA component upgrade. Currently I have:

Core 2023.12.0
Supervisor 2023.11.6

Error message in the log:

This error originated from a custom integration.

Logger: custom_components.weatherdotcom.coordinator
Source: custom_components/weatherdotcom/coordinator.py:161
Integration: Weather.com (documentation, issues)
First occurred: 09:12:23 (628 occurrences)
Last logged: 23:27:33

Check Weather.com API ('unexpected character: line 1 column 1 (char 0)',)

Use service get_forecasts for forecasts

Hello,

Since I updated HA to 2023.12, I get the following message:

Detected use of deprecated service weather.get_forecast
Use weather.get_forecasts instead which supports multiple entities.

Please replace this service and adjust your automations and scripts and select submit to close this issue.

Woul it be possible to adapt his integration to use the new HA service?

Regards, Ronald

Integration failed to load after core 2024.2.0 update

Hi,
Any ideea why the integration is broken after HA core 2024.2.0 update? Can’t seem to make it work no matter what i do. And I’ve pretty much tried everything. It worked fine until last night when i updated the core.
Logs below:

Logger: homeassistant.setup
Source: setup.py:251
First occurred: 17:31:22 (1 occurrences)
Last logged: 17:31:22

Setup failed for custom integration 'weatherdotcom': Unable to import component: No module named 'custom_components.weatherdotcom.coordinator'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 251, in _async_setup_component
    component = integration.get_component()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 827, in get_component
    ComponentProtocol, importlib.import_module(self.pkg_path)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 994, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/config/custom_components/weatherdotcom/__init__.py", line 11, in <module>
    from .coordinator import WeatherUpdateCoordinator, WeatherUpdateCoordinatorConfig
ModuleNotFoundError: No module named 'custom_components.weatherdotcom.coordinator'

Documentation refers to deprecated hourly weather sensor

The documentation includes the following statement:

Additionally, a weather.<LOCATION_NAME>_hourly entity will be created that contains hourly forecast data.

Presumably this is no longer the case since both the daily and hourly forecasts are encapsulated in the main weather.<LOCATION_NAME> sensor (to accommodate the new weather forecast structure in HA 2023.09+).

Caused a bit of confusion trying to use the hourly forecast with the Hourly Weather Card since the old 'xxx_hourly' sensor was no longer available. Changed it to use the main sensor and everything is good.

Combine daily and hourly weather entities

New in Home Assistant 2023.9, weather entities' forecast data can now be accessed via a service, allowing for one entity to have multiple types of forecasts (daily and hourly). The forecast attribute (which this integration is currently using) is now depreciated and will be removed in version 2024.3.

Could you please update this integration to remove the need for two entities and for future proofing?

"feels like

add a sensor for cloud coverage

would it be possible to all scrape the information of cloud coverage (in %) and get that into a sensor? I see in wunderground that the info is available when I click the HOURLY tab

thanks