dontinelli 2a96ef1e02
Add documentation for new extra attributes for fyta (#40410)
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
2025-08-18 09:15:59 +00:00

125 lines
4.6 KiB
Markdown

---
title: FYTA
description: Instructions on how to integrate FYTA sensors within Home Assistant.
ha_category:
- Binary sensor
- Sensor
ha_release: 2024.4
ha_iot_class: Cloud Polling
ha_config_flow: true
ha_codeowners:
- '@dontinelli'
ha_domain: fyta
ha_platforms:
- binary_sensor
- diagnostics
- image
- sensor
ha_integration_type: hub
ha_quality_scale: platinum
ha_dhcp: true
---
The **FYTA** {% term integration %} uses the open API of [FYTA](https://www.fyta.de) to obtain the data from your plant sensors and integrate these into Home Assistant.
## Supported devices
The integration should work with any [FYTA Beam](https://fyta.de/collections/all/products/single-beam).
## Prerequisites
For the integration to work you need a [FYTA Beam](https://fyta.de/collections/all/products/single-beam) and a FYTA account.
{% include integrations/config_flow.md %}
To setup the integration you need the following information:
{% configuration_basic %}
Email:
description: "The email address used to access the FYTA account."
Password:
description: "The password used to access the FYTA account."
{% endconfiguration_basic %}
## Configuration
The integration has no additional configuration options.
## Supported functionality
### Binary sensors
The following binary sensors are currently available per plant:
- Low battery
- Light notification
- Nutrition notification
- Temperature notification
- Water notification
- Productive plant
- Repotted
- Sensor update available
### Image
An image entity for both the generic plant image and the user image is added. You may use those for your dashboard.
### Sensors
The following sensors are currently available per plant:
| name | Unit | Description |
|-----------------------|--------|:-------------------------------------------|
| scientific_name | | Scientific name of the plant |
| plant_status | | FYTA-Status (cf. scale below) |
| temperature_status | | FYTA-Status (cf. scale below) |
| light_status | | FYTA-Status (cf. scale below) |
| moisture_status | | FYTA-Status (cf. scale below) |
| nutrients_status | | FYTA-Status (cf. scale below) |
| salinity_status | | FYTA-Status (cf. scale below) |
| temperature | °C | Temperature measured by sensor |
| light | μmol/h | Light measured by sensor (hourly photosynthetically active radiation PAR)|
| moisture | % | Moisture measured by sensor |
| salinity | mS/cm | Salinity measured by sensor (measured as conductivity)|
| fertilise_last | date | Date when plant has last been fertilized |
| fertilise_next | date | Date when plant should be fertilized |
| battery_level | % | Battery level of the sensor |
The plant status may have one of the following states:
- Plant deleted
- Plant good status
- Plant bad status
- Plant no sensor
For plant measurements, the following status scale is applied:
- No Data
- Too Low
- Low
- Perfect
- High
- Too High
For the measurement sensors (light, moisture, salinity, and temperature), the maximal/minimal values that define the ranges of what is considered acceptable and good for the plant are saved as an extra attribute of the sensor. For example: Below 10 it's too cold, that could be the minimum acceptable. 15 could be the minimum of the good range. Between 15 and 30 is perfect. 30 would be maximum good and 35 would be the maximum acceptable. Above 35 it's too hot. These values can be used for automations or visualizations on the dashboard.
## Data updates
The integration fetches data from the device every 4 minutes.
## Actions
The integration provides no additional actions.
## Known limitations
The integration provides the data exposed by means of the plant API. The light measurement as current daily light integral (DLI) is not yet available (currently only the PAR value is provided).
Please note that in order to be able to access your plant data over the API, you need a [FYTA hub](https://fyta.de/collections/all/products/single-hub) that uploads the data from the Beam sensor to the FYTA server. Alternatively, the mobile app can serve as a gateway to upload the data from the Beam to the server. No direct connection to the FYTA Beam is supported (as the Beam only provides raw data, that needs to be processed on the FYTA server).
## Removing the integration
For this integration the general process to remove integrations applies:
{% include integrations/remove_device_service.md %}