How it works

AquasManager is made of four building blocks that run on your local network.

Block	Role
Interface	Installable web app (PWA) for phone, tablet or computer. Also works offline.
Server (API)	Stores the data, computes alerts and trends, sends notifications and generates the controllers’ firmware.
MQTT broker	Real-time messaging between the server and the controllers (Mosquitto).
ESP32 controllers	Drive relays, probes and LED fixtures. Their firmware is generated by AquasManager with ESPHome.

The server describes, the ESP executes

You describe your hardware in the interface: pins, relays, probes, LED fixtures, rules. AquasManager generates the matching ESPHome firmware and flashes it to the controller.

Critical automations are stored on the controller:

• lighting curves;
• rules (thresholds, sensor states, time windows) and their safety locks;
• the time, thanks to a battery-backed RTC clock if you fit one.

If the server restarts or fails, the aquarium keeps running. The server takes over again when it comes back.

Remember

Every change to a controller’s configuration (new rule, new probe, new lighting schedule) needs a new flash before the ESP applies it. The interface flags the controllers that need reflashing.

Data and privacy

Everything stays at home: the database and photos live on your server. Only the services you turn on see any data: notifications (Telegram, ntfy, push) and, if you connect it to an external service rather than a local model, the AI assistant.