Skip to content
Nur Amin
← All projects
P-06FertiCore / Alburdat Presisi2026

Precision Fertiliser System

A complete precision-fertilising rig: ESP32 firmware driving a dosing motor, an MQTT link, and a Flutter dashboard that runs on phone, desktop and web.

My role
Firmware, MQTT contract, and Flutter dashboard.
Field
IoT & Embedded, Mobile Apps
Stack
  • ESP32
  • C++
  • MQTT
  • Flutter
  • Provider
  • EEPROM

Overview

Fertiliser is expensive and easy to waste. The rig meters it out by commodity instead of by habit: the operator picks what is being grown, the app works out a dose per plant, and the device dispenses exactly that at every point.

The architecture is still deliberately server-less. The Flutter app and the ESP32 talk to each other through an MQTT broker as two peers — no back end to keep alive, no database bill, and operating statistics stay in the device’s own EEPROM. What changed in version 2 is that the door is no longer open. The first version used a public broker with fixed topics shared by every unit, so anyone who knew the topic could change the dose. Now the broker is configurable, TLS is on by default, credentials sit in the phone’s Keystore or Keychain, and each device lives under its own topic.

The second change is that a command is not finished when the broker accepts it. Every command carries a random id and a timestamp; the app shows a summary first, publishes, then waits for a status message that echoes the id back. If none arrives within eight seconds the operator is told the command was sent but not confirmed — instead of assuming it worked. The old JSON keys were kept, so the firmware only has to move topics and start acknowledging.

In pictures

FertiCore title with the v2 dashboard on a phone and in a desktop browser: a 15.0 g active dose, device status tiles and a secured broker.
FIG. 01One Flutter codebase on phone, web and desktop. Mockups redrawn from the app with sample values; the app UI is in Indonesian.
The recommendation screen for dragon fruit, NPK, 900 m² and 120 days after planting, next to four steps ending in a device range check, the MQTT command, and a blocked 1,325 g avocado dose.
FIG. 02From crop and age to grams per plant — and a dose the device cannot dispense is blocked, not sent.
Table of 13 crops with planting spacing and dose bands by days after planting; bands within the device’s 5–50 g range are highlighted green.
FIG. 03The full knowledge base: one row per crop, one band per growth stage, with no gaps between stages.
Diagram: Flutter app, TLS-secured MQTT broker and ESP32 as peers, with per-device topics, the status payload with ack, the three commands with id and timestamp, four connection states, and the command lifecycle.
FIG. 04Still no server in the middle — now with TLS, broker credentials, per-device topics and commands the device confirms.
Three phone screens: manual dosing with a confirmation sheet, statistics with a live chart, and the searchable in-app guide.
FIG. 05Review a dose before it is sent, watch usage build up, and find help on every screen.

Function

Device
ESP32 with DC dosing motor and OLED display
Transport
MQTT + JSON over TCP/WebSocket, no server in between
Client
Flutter dashboard for Android, iOS, web and desktop

What it does

  1. 01Rule-based dose recommendation for 13 crops by days after planting, for NPK or Urea, with the plant count estimated from field area and spacing.
  2. 02Doses outside what the dispenser can deliver (5–50 g per point) are blocked with an explanation instead of being sent.
  3. 03Every command is reviewed in a summary sheet and confirmed by the device, with a clear “sent, not confirmed yet” state.
  4. 04Configurable broker with TLS and credentials; the password is kept in Keystore/Keychain and never shown again.
  5. 05Live device status — online, offline, disconnected or not set up — with automatic reconnect that backs off but never gives up.
  6. 06Usage statistics from the device with a live chart, plus manual dosing for when the operator overrules the recommendation.
  7. 07Onboarding, a searchable in-app guide and FAQ, and a help button on every screen that opens its own section.
  8. 08One Flutter codebase serving Android, iOS, web and desktop.

Technical notes

Broker
Configurable; TLS on 8883 (WSS 8084 on web), username/password
Topics
ferticore/<device-id>/status and /command, one device per topic
Commands
Random id + timestamp, acknowledged by the device within 8 s
State
Provider for app state; EEPROM for device statistics
Back end
None — app and device are MQTT peers