AgroPulse surfaces operational events through two complementary tools. The Alerts feed aggregates every notification generated by the system — whether raised automatically when a sensor crosses a crop threshold or created manually by an operator. The Map renders the physical locations of your greenhouses on an interactive globe, with live sensor pop-ups and optional weather overlay layers.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.
- Alerts
- Map
Alert levels
Every alert carries one of three severity levels.INFO
Informational notifications. No immediate action required. Displayed with a blue indicator and reduced visual weight.
WARNING
Conditions that may affect crop health if left unaddressed. Displayed with an amber indicator. Review and respond within a reasonable timeframe.
CRITICAL
Conditions that require immediate action — sensor values are outside safe crop ranges or a device has stopped responding. Displayed with a red indicator and an animated pulse dot.
Alert data model
Each alert (AlertDto) contains:| Field | Type | Description |
|---|---|---|
id | number | Unique alert identifier |
type | SensorType | string | The sensor type that triggered the alert, or "MANUAL" for operator-created alerts |
level | "INFO" | "WARNING" | "CRITICAL" | Severity |
title | string (optional) | Short headline |
message | string | Full alert text |
timestamp | string (optional) | ISO 8601 timestamp |
read | boolean | Whether the alert has been acknowledged |
greenhouseId | number (optional) | The greenhouse this alert belongs to, or absent for global alerts |
Alert sources
Automatic alerts from the dashboard
The Dashboard continuously compares live sensor readings against the active crop’s threshold ranges. When a reading crosses atemp_min, temp_max, humidity_min, humidity_max, soil_moisture_min, soil_moisture_max, light_min, light_max, co2_min, or co2_max boundary, an AutoAlert is generated with the appropriate level and a descriptive message. These alerts appear in the feed automatically — no configuration is needed beyond defining a crop profile.Manual alerts from operators
Any user can create a manual alert by clicking Nueva on the Alerts page and filling in:- Invernadero — target greenhouse, or global (all greenhouses)
- Mensaje — free-form description of the situation
- Nivel —
INFO,WARNING, orCRITICAL
type: "MANUAL" and are visible in the same feed as automatic alerts.Rule-engine alerts
Automation rules (configured in Crops & Automation) can have an action type ofALERT. When a rule’s condition is met — for example, CO₂ GREATER_THAN 1200 ppm — the rules engine creates an alert with the matching level and sensor context.Reading and filtering alerts
The stats bar at the top of the feed shows live counts of CRITICAL, WARNING, and INFO alerts. Click any stat chip to filter the list to that level; click it again to clear the filter. A greenhouse chip row lets you narrow the view to a single location.Unread alerts show a colored animated pulse dot next to their badge. Read alerts are displayed at reduced opacity.The list renders up to 50 alerts at a time. Click Ver más to load the next 50.Marking alerts as read
- Single alert — Click the checkmark icon on the alert card to mark it as read. The card fades to indicate its acknowledged state.
- All at once — Click Marcar todas leídas (visible in the header when unread alerts exist) to acknowledge the entire feed in one action.
alertRepository.markRead(id) and cached in localStorage under agropulse_alerts_v1.Alert state is cached locally so the feed loads instantly on page revisit. The cache is refreshed each time the page mounts or an alert is created or deleted.