Please ⭐ this repo if you find it useful

1. Have HACS installed, this will allow you to easily manage and track updates.
2. Search in HACS for "Apparent Temperature" integration or just press the button below:
   
3. Click Install below the found integration.

... then if you want to use configuration.yaml to configure sensor...

1. Add apparent_temperature sensor to your configuration.yaml file. See configuration examples below.
2. Restart Home Assistant

1. Using the tool of choice open the directory (folder) for your HA configuration (where you find configuration.yaml).
2. If you do not have a custom_components directory (folder) there, you need to create it.
3. In the custom_components directory (folder) create a new folder called apparent_temperature.
4. Download file apparent_temperature.zip from the latest release section in this repository.
5. Extract all files from this archive you downloaded in the directory (folder) you created.
6. Restart Home Assistant

... then if you want to use configuration.yaml to configure sensor...

1. Add apparent_temperature sensor to your configuration.yaml file. See configuration examples below.
2. Restart Home Assistant

# Example configuration.yaml entry
sensor:
  - platform: apparent_temperature
    source: weather.home

# Example configuration.yaml entry
sensor:
  - platform: apparent_temperature
    name: 'Basement Feels Like Temperature'
    source:
      - sensor.basement_temperature
      - sensor.basement_humidity

* * *

or support via Bitcoin or Etherium:

16yfCfz9dZ8y8yuSwBFVfiAa3CNYdMh7Ts

source:
(string | list of strings) (Required)
Weather provider entity ID or climate entity ID or list of sensors entity IDs.
For calculations sensor uses temperature, humidity and wind speed values. Temperature and humidity values is required. Wind speed value is optional.
Weather provider provide all values. Climate object provide only temperature and humidity.

Note:
You can use groups of entities as a data source. These groups will be automatically expanded to individual entities.

Note:
If you specify several sources of the same type of data (for example, a weather provider and a separate temperature sensor), the sensor uses only one of them as a source (the one that will be the last in the list). Therefore, the result of calculations can be unpredictable.

name:
(string) (Optional) (Default value: name of first source + " Apparent Temperature")
Name to use in the frontend.

unique_id
(string) (Optional)
An ID that uniquely identifies this sensor. Set this to a unique value to allow customization through the UI.

You can automatically track new versions of this component and update it by HACS.

To enable debug logs use this configuration:

# Example configuration.yaml entry
logger:
  default: info
  logs:
    custom_components.apparent_temperature: debug

... then restart HA.

This is an active open-source project. We are always open to people who want to use the code or contribute to it.

We have set up a separate document containing our contribution guidelines.

Thank you for being involved! 😍

The original setup of this component is by Andrey "Limych" Khrolenok.

For a full list of all authors and contributors, check the contributor's page.

This Home Assistant custom component was created and is updated using the HA-Blueprint template. You can use this template to maintain your own Home Assistant custom components.

creative commons Attribution-NonCommercial-ShareAlike 4.0 International License

See separate license file for full text.