Enter the admin password.
Manual doses use their own daily cap and don't use up the AI's water budget.
Captures and uploads to the gallery (also refreshes the AI's latest image).
Stable /dev/v4l/by-id/… paths survive replugging. Run python diagnose_cameras.py on the Pi if a camera is missing.
Overrides on top of config.yaml. Safest place for changes: it survives code updates.
Saved files are checked first (YAML, dates, number ranges) and backed up. If the grower crashes after the restart, the supervisor puts the old file back. Water-budget values can't go above the limits built into the code (--).
Placeholders like {day} are filled in each check-in: --. The hard water-budget limits are always appended by the code.
Starting a new grow sets day 0 to today, moves the AI's history and the Pi's photos to data/archive/<date>/, and the website then shows only the new grow's photos, decisions and trends. Nothing is deleted: older grows stay in Firestore. The water budget is kept.
The Pi pulls, checks the code compiles, restarts, then watches it for 60 s. If the new code crashes, the supervisor rolls back to the previous commit automatically.
The Pi emails when the AI raises an alarm, when a problem shows in the red banner for over a minute (and when it clears), and when the grower crashes. The same problem is repeated at most every 6 h.
Open this tab to load logs…