Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/diarpicu2022-commits/frontend-AgroPulse/llms.txt

Use this file to discover all available pages before exploring further.

Sensors are the data sources for AgroPulse. Each sensor belongs to a greenhouse and reports readings that the Dashboard, crop profiles, and automation rules act on. Actuators are output devices—pumps, fans, LEDs, and similar—that automation rules can activate or deactivate in response to sensor conditions. The Sensors page polls the backend every 15 seconds and pauses polling when the browser tab is hidden.

Sensor types

TypeUnitDescription
TEMPERATURE°CGeneral air temperature
TEMPERATURE_INTERNAL°CInterior air temperature (inside the greenhouse)
TEMPERATURE_EXTERNAL°CExterior air temperature (outside the greenhouse)
HUMIDITY%Interior relative humidity
HUMIDITY_EXTERNAL%Exterior relative humidity
SOIL_MOISTURE%Volumetric soil moisture
LIGHTlxIlluminance
CO2ppmCarbon dioxide concentration
PRESSUREhPaAtmospheric pressure

Supported protocols

ProtocolTypical hardware
DHT22DHT22 temperature/humidity module
DHT11DHT11 temperature/humidity module
ADCAnalog-to-digital converter (ESP32 internal)
ANALOGGeneric analog signal
I2CI²C bus devices (BMP280, SHT31, etc.)
DIGITALDigital GPIO input
ONE_WIRE1-Wire bus devices (DS18B20, etc.)

Adding a sensor

1

Open the Sensors page

Navigate to Sensores in the sidebar and click Nuevo.
2

Fill in the sensor details

FieldRequiredNotes
NameYesDescriptive label shown on sensor cards
TypeYesSelect from the sensor types above
ProtocolYesCommunication protocol used by the hardware
GPIO pinNoThe ESP32 GPIO number the sensor is wired to
GreenhouseNoAssigns the sensor to a specific greenhouse
LocationNoOptional free-text location within the greenhouse
3

Save

Click Guardar sensor. The sensor appears in the list and the Dashboard will include it in the next poll.
Sensors can also be added directly from the Device tab of a greenhouse card. That flow pre-selects the correct greenhouse and shows only the GPIO pins not already in use.

Alert thresholds

Each sensor has an optional threshold configuration that controls when the backend raises an alert for anomalous readings.
FieldDefaultDescription
Min valueAlert when the reading falls below this value
Max valueAlert when the reading exceeds this value
No-data minutes10Alert when no reading has arrived for this many minutes
Stuck minutes30Alert when the reading has not changed for this many minutes
Spike percent50Alert when a reading jumps by more than this percentage from the previous value
Expand the threshold panel on any sensor card and click Guardar umbrales to save. A green badge on the card confirms that thresholds are configured.

Deduplication

When multiple sensor records exist with the same type, GPIO pin, and greenhouse (a common side-effect of ESP32 reconnections), admin users can remove the duplicates automatically. Click the Dedup button in the page header. The newest record for each combination is kept; older duplicates are deleted. A toast notification reports how many were removed.
The Dedup button is only available to admin accounts. Operator accounts see only the sensors assigned to their greenhouses and cannot run deduplication.

Build docs developers (and LLMs) love