openuv integration displays UV and Ozone data from openuv.io.
To generate an API key, simply log in to the OpenUV website.
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
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
To retrieve data from OpenUV, add the following to your
openuv: api_key: YOUR_OPENUV_API_KEY
The OpenUV API key.
The binary sensor-related configuration options.
The sensor-related configuration options.
The conditions to create sensors from.
The current ozone level in du (Dobson Units).
The current UV index.
The level of current UV index, which is calculated based on UV Index Levels & Colors.
The maximum UV index that will be encountered that day (at solar noon).
The approximate exposure time for skin type I.
The approximate exposure time for skin type II.
The approximate exposure time for skin type III.
The approximate exposure time for skin type IV.
The approximate exposure time for skin type V.
The approximate exposure time for skin type VI.
The approximate number of minutes of a particular skin type can be exposed to the sun before burning/tanning starts is based on the Fitzpatrick scale.
To configure additional functionality, add configuration options beneath a
sensor key within the
openuv section of the
configuration.yaml file as below:
openuv: api_key: YOUR_OPENUV_API_KEY binary_sensors: monitored_conditions: - uv_protection_window sensors: monitored_conditions: - current_ozone_level - current_uv_index - current_uv_level - max_uv_index - safe_exposure_time_type_1 - safe_exposure_time_type_2 - safe_exposure_time_type_3 - safe_exposure_time_type_4 - safe_exposure_time_type_5 - safe_exposure_time_type_6
Perform an on-demand update of OpenUV data.
One method to retrieve data every 30 minutes and still leave plenty of API key usage is to only retrieve data during the daytime:
automation: - alias: Update OpenUV every 30 minutes during the daytime trigger: platform: time_pattern minutes: '/30' condition: condition: and conditions: - condition: sun after: sunrise - condition: sun before: sunset action: service: openuv.update_data
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:
automation: - alias: Update OpenUV every hour (24 of 50 calls per day) trigger: platform: time_pattern minutes: '/60' action: service: openuv.update_data