OpenUV

Generating an API Key

Beginning February 1, 2019, the “Limited” plan (which is what new users are
given by default) is limited to 50 API requests per day. Because different
API plans and locations will have different requirements, the openuv
component does not automatically query the API for new data after it initially
loads. To request new data, the update_data service may be used.

Each use of the update_data service will consume 1 or 2 API calls, depending
on which monitored conditions are configured.

If the OpenUV integration is configured through the Home Assistant UI (via the
Configuration >> Integrations panel), each service call will consume 2 API
calls from the daily quota.

If the OpenUV integration is configured via configuration.yaml, service calls
will consume 2 API calls if monitored_conditions contains both
uv_protection_window and any other condition; any other scenarios will only
consume 1 API call.

Ensure that you understand these specifications when calling the update_data
service.

Configuration

To retrieve data from OpenUV, add the following to your configuration.yaml
file:

openuv:
api_key: YOUR_OPENUV_API_KEY

Configuration Variables

api_key

(string)(Required)

The OpenUV API key.

binary_sensors

(map)(Optional)

The binary sensor-related configuration options.

monitored_conditions

(list)(Optional)

The conditions to create sensors from.

Default value:

all

uv_protection_window

Displays if UV protection (sunscreen, etc.) is recommended at the current date and time.

Another method (useful when monitoring locations other than the HASS latitude
and longitude, in locations where there is a large amount of sunlight per day,
etc.) might be to simply query the API less often: