-
-
Notifications
You must be signed in to change notification settings - Fork 13
Description
System Health details
System Information
version | core-2024.12.3 |
---|---|
installation_type | Home Assistant OS |
dev | false |
hassio | true |
docker | true |
user | root |
virtualenv | false |
python_version | 3.13.0 |
os_name | Linux |
os_version | 6.6.63-haos |
arch | x86_64 |
timezone | Europe/Berlin |
config_dir | /config |
Home Assistant Community Store
GitHub API | ok |
---|---|
GitHub Content | ok |
GitHub Web | ok |
HACS Data | ok |
GitHub API Calls Remaining | 4975 |
Installed Version | 2.0.1 |
Stage | running |
Available Repositories | 1486 |
Downloaded Repositories | 3 |
Home Assistant Cloud
logged_in | false |
---|---|
can_reach_cert_server | ok |
can_reach_cloud_auth | ok |
can_reach_cloud | ok |
Home Assistant Supervisor
host_os | Home Assistant OS 14.0 |
---|---|
update_channel | stable |
supervisor_version | supervisor-2024.11.4 |
agent_version | 1.6.0 |
docker_version | 27.2.0 |
disk_total | 30.8 GB |
disk_used | 10.0 GB |
healthy | true |
supported | true |
host_connectivity | true |
supervisor_connectivity | true |
ntp_synchronized | true |
virtualization | kvm |
board | ova |
supervisor_api | ok |
version_api | ok |
installed_addons | Matter Server (6.6.1), MariaDB (2.7.1), File editor (5.8.0), Advanced SSH & Web Terminal (19.0.0), Music Assistant Server (2.3.3), OpenThread Border Router (2.12.2), Get HACS (1.3.1), Samba share (12.3.2), InfluxDB (5.0.1), Grafana (10.2.2) |
Dashboards
dashboards | 2 |
---|---|
resources | 1 |
views | 1 |
mode | storage |
Recorder
oldest_recorder_run | 12. Dezember 2024 um 07:46 |
---|---|
current_recorder_run | 15. Dezember 2024 um 11:50 |
estimated_db_size | 2.64 MiB |
database_engine | sqlite |
database_version | 3.45.3 |
Checklist
- I have enabled debug logging for my installation.
- I have filled out the issue template to the best of my ability.
- This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
- This issue is not a duplicate issue of any previous issues..
Describe the issue
There seems to be conflicting instructions for setting up the Apparent Temperature integration. After installation via HACS, the following occurs:
-
When I try to add the integration via the Home Assistant UI (Settings > Devices & Services > Add Integration), I receive an error stating:
"This integration must be configured in the configuration.yaml file." -
Based on this message, I added the configuration manually to configuration.yaml (example below) and restarted Home Assistant. However, this results in a new error stating:
"The apparent_temperature integration does not support YAML setup, please remove it from your configuration."
Example YAML Configuration
apparent_temperature:
sensors:
- name: "Living Room Feels Like Temperature"
unique_id: "sensor.living_room_feels_like_temperature"
temperature: sensor.ilmist_living_room_aqara_temperature_sensor_temp
humidity: sensor.ilmist_living_room_aqara_temperature_sensor_humidity
pressure: sensor.ilmist_living_room_aqara_temperature_sensor_pressure
Reproduction steps
- Install the Apparent Temperature integration via HACS.
- Restart Home Assistant.
- Attempt to add the integration via Settings > Devices & Services > Add Integration.
- Receive an error instructing you to use configuration.yaml.
- Remove the UI attempt and add the configuration manually to configuration.yaml as shown below.
- Restart Home Assistant.
- Encounter an error stating YAML setup is not supported.
Debug logs
Logger: homeassistant.setup
Source: setup.py:363
First occurred: 11:45:57 (1 occurrences)
Last logged: 11:45:57
The `apparent_temperature` integration does not support YAML setup, please remove it from your configuration.
Logger: homeassistant.setup
Source: setup.py:269
First occurred: 11:50:23 (1 occurrences)
Last logged: 11:50:23
Setup failed for custom integration `apparent_temperature`: No setup or config entry setup function defined.
Diagnostics dump
As the integration cannot be added, no diagnostic dump is available.
This issue might indicate a bug or a mismatch between the documentation and the actual behavior of the integration. A resolution or updated guidance would be appreciated.
Thank you!