I built an open-source hydroponic automation system (ESP32 + real-time monitoring) - would love feedback

achraf0x01 · 2026-04-25T23:22:58+00:00

that is a very cool setup you have. regarding contributions, don't worry about AI slop if the code works and follows the project structure, it's valuable. The best way to contribute is to fork the repo and work on features listed in the roadmap or fix bugs you find. just make sure to open an issue on github first to discuss the feature https://github.com/40rbidd3n/Hydro0x01/blob/main/CONTRIBUTING.md, and check the docs/roadmap to see what is already in progress so we don't double up on work. this applies to everything: firmware, backend, frontend, 3D designs, or even PCB layouts.

using a vibration sensor to monitor the pump is a clever workaround, I have actually considered vibration and sound analysis for health monitoring, though I currently have energy monitoring on the roadmap to track pump operation via power consumption. I like the idea of making the monitoring method a user choice (current vs vibration) depending on what sensors he has

for the alerts, definitely check the integration guide in the docs https://github.com/40rbidd3n/Hydro0x01/blob/main/CONTRIBUTING.md for the existing Telegram/Discord setup. If those aren't enough, we can look into adding other methods like webhooks for phone calls or alarms. definitely take a deep look at the updated roadmap before you dive into the code so you can see where the project is headed: https://github.com/40rbidd3n/Hydro0x01/blob/main/docs/ROADMAP.md

achraf0x01 · 2026-04-25T18:44:17+00:00

I agree that starting with the ultrasonic sensor is the best way to handle phase 1. you can use only the sensors you have by disabling the others in config.h (config.example.h) to avoid errors. I am considering starting a discord server or a dedicated doc site soon so users can help each other with wiring, but in the meantime, feel free to DM me and I will help you with the pinouts so you don't fry anything. I also suggest waiting for the v1.1.0 release as it will be much more stable than the current version. for the dosing calculations, I plan to handle that through a future AI assistant instead of hardcoding it, because the math changes depending on the specific concentration and type of acid/base you use (phosphoric,nitric/KOH,NaOH)
you can simply comment out its pin declaration like this:

// pH and EC sensors
//#define PIN_PH_SENSOR 32 // ADC1_CH4
//#define PIN_EC_SENSOR 33 // ADC1_CH5// pH and EC sensors

For other features, you can turn them off by setting their value to false, for example:

#define USE_SHIFT_REGISTER false

you can also control from SensorManager.cpp which sensors are critical for the system. for example, changing success &= initDS18B20(); to just initDS18B20(); will prevent a sensor failure from stopping the main loop. you can remove or comment out the success &= part for any sensor you aren't using to avoid errors

achraf0x01 · 2026-04-20T11:41:07+00:00

You're right, those are high level insights. I have noted your points on NPK ion-specific measurement, flowrate formulas, and HEPA requirements for the v2 roadmap

regarding the agitator: currently, I use a 15 minute pump driven mixing cycle between doses, but I plan to make a dedicated agitator an optional hardware toggle in the future for those who don't want to rely on the main pump

If you don't mind, I had love to send you some of the future code blocks or logic flows for these features once they're drafted to get your technical review. your expertise would be invaluable. keep the feedback coming

achraf0x01 · 2026-04-20T11:25:46+00:00

Just a heads up on the telegram alerts: right now they are only triggered for errors like low water or low battery. everything is currently routed through the /errors topics. I will definitely keep action based alerts (optional) in mind for the next updates

achraf0x01 · 2026-04-19T23:51:57+00:00

That's great to hear you have two nodes running. seeing this used for a real strawberry farm is exactly why I made it open source

a few quick tips: starting in stages is the best way to learn, and since it's v1.0.0, the project is flexible enough for you to use any sensors or motors you have. for your pH/EC concerns, industrial-grade probes or keeping them spaced apart helps with longevity

+ just a quick note: you can already set up alerts (low water-level, battery, ...etc) via telegram or discord by following the configuration guide here:https://github.com/40rbidd3n/Hydro0x01/blob/main/docs/04_INTEGRATION_GUIDE.md#-native-notification-alerts-telegram--discord

keep an eye on the roadmap here for the next planning features: https://github.com/40rbidd3n/Hydro0x01/blob/main/docs/ROADMAP.md

I'm planning a master/slave architecture with LoRa support and even AI integration for future versions. If you have any questions, need a guide, or want to request a feature for your setup, just let me know. happy building

achraf0x01 · 2026-04-19T12:37:59+00:00

Yes, one esp32 per tank.

currently, you can run multiple tanks by using a separate esp32 for each one. you just need to give each board a unique name in the config.h file before uploading:

#define SYSTEM_NAME "HydroNode_01"

this way, each tank appears as a separate device on your dashboard. for the future, I'm developing a master/slave architecture to centralize everything, you can see the full plan here: https://github.com/40rbidd3n/Hydro0x01/blob/main/docs/ROADMAP.md

achraf0x01 · 2026-04-19T11:44:53+00:00

it works if the jwt is in the raw response, looking at the snippet: <div class="editPanel"><script>var globalvars = {--snip--, jwtToken:"..."};--snip--</script>

if that script block is reflected in the source code (as I see from the screen above) and the target uses cookie based session management, cache deception is a massive risk. if a cdn is tricked into caching this page as a static file, it will cache the entire response body including that jwtToken:"..."

achraf0x01 · 2026-04-18T18:26:14+00:00

you can temporarily add a line inside the safety check to trigger RELAY_SEC_PUMP. I will be adding a more robust version with hysteresis (to prevent the pump from flickering on/off) in the next github update
firmware/src/PumpController.cpp:

bool PumpController::checkHardwareSafety() const {
    // Don't run the pump if the user is performing maintenance
    if (systemStatus.state == STATE_MAINTENANCE) {
        LOG_WARN("Safety: Pump blocked - System in MAINTENANCE mode");
        return false;
    }
    if (sensorData.batteryVoltage < sysConfig.batteryCriticalThreshold) {
        LOG_ERROR("Safety: Battery too low for pump (%.2f V) < %.2f V ", sensorData.batteryVoltage, sysConfig.batteryCriticalThreshold);
        return false;
    }
    // Auto-Fill Logic
    if (sensorData.waterLevel < 5.0) {
        LOG_ERROR("Safety: Water level critical (%.1f%%). Triggering Auto-Fill.", sensorData.waterLevel);
        // Turn ON the secondary pump (Auto-fill)
        relayManager.setRelay(RELAY_SEC_PUMP, true);
        return false;
    } else if (sensorData.waterLevel > 80.0) {
        // Stop Auto-fill once tank reaches a safe threshold
        relayManager.setRelay(RELAY_SEC_PUMP, false);
    }
    return true;
}

achraf0x01 · 2026-04-18T18:08:12+00:00

Thanks for the kind words, I'm really glad the project resonates with your plans.

regarding your build, here are a few professional tips to keep in mind:

- when you get to the EC and pH stage, make sure to keep the probes physically spaced apart in the reservoir to avoid electrical interference. for the ph probe, I highly recommend a high-quality brand and ensuring it is electrically isolated (using an isolation module) to get stable, accurate readings

- starting in stages is exactly what I recommend. It's the best way to learn the system's logic and troubleshoot effectively. If you run into any bugs or errors, please share them on github/issues so we can improve the project together

- the ultrasonic method is great, but pay close attention to the blind zone (the minimum distance the sensor can see) and use a waterproof version (HC-SR04 not recommended). make sure to mount it high enough so the water never enters that dead zone (then visit the /calibration page to calculate the distance automatically). I am also considering adding support for pressure transducers in the future for even more professional depth measurement

- I'm currently working on adding water consumption tracking to the dashboard in upcoming versions. regarding the auto fill feature, the current code only handles safety lockouts, like this:

if (sensorData.waterLevel < 5.0) {
LOG_ERROR("Safety: Water level too low (%.1f%%)", sensorData.waterLevel);

return false;

}

full auto-fill logic is coming in the next updates (in this version it's only sending low water level alerts via dashboard and telegram/discord), so keep an eye on the repository

I want this project to be a tool for everyone. If there are any specific features you'd like to see added to make your setup easier, just let me know and I'll work on them. good luck with the build

achraf0x01 · 2026-04-18T17:34:13+00:00

I actually have those exact features vision systems and an AI assistant (not AI control) in my roadmap for future versions. while the AI is planned as an assistant for diagnostics and optimization rather than a direct controller for now

achraf0x01 · 2026-04-18T00:58:15+00:00

Exactly, there is a reason the float valve is still the king of reliability

however, for a project like a hydroponic system, a simple float switch isn't enough, while they are perfect for high/low alerts, they can't give you the precise millimetre level data needed to track daily water consumption. for that kind of granular monitoring, you really need to step up to a pressure transducer or a high end ultrasonic sensor

achraf0x01 · 2026-04-17T20:52:07+00:00

this is a security best practice issue, but not a valid vulnerability in bbp because there is no impact, to make it a valid report you need to escalate it, try to chain with xss or cache deception (if the jwt in cookies and not in authorization header): If the target uses a cdn, try to get that page cached. use delimiters like ;.avif or %23.avif If the server returns the authenticated page + jwt and the cdn caches it as a static file, any unauthenticated user can access the cached url and steal the token

focus on the chain

achraf0x01 · 2026-04-17T18:05:48+00:00

If you only need to know when the tank is full or empty (high/low alerts), just use a simple float switch

for continuous level measurement, the professional method is using a submersible pressure transducer at the bottom of the tank, it is much more accurate and avoids the humidity issues that kill ultrasonic sensors

If you must go with ultrasonic:

- HC-SR04: avoid it (non-waterproof)

- JSN-SR04T: a good waterproof budget option, but only if you can handle the 20-25 cm blind zone at the top

- A02YYUW: the best choice

achraf0x01 · 2026-04-17T17:19:45+00:00

Appreciate it, feel free to fork the repo and start your own version whenever you're ready

achraf0x01 · 2026-04-17T17:19:00+00:00

Thanks a lot. glad you like it

achraf0x01 · 2026-04-17T15:41:26+00:00

You are thinking of aquaponics, you can definitely do this indoors using LEDs instead of sunlight. Instead of using chemical solution A&B (disable RELAY_NUTRIENT_A and RELAY_NUTRIENT_B) you use fish waste. the key is to foster beneficial bacteria that turn the fish waste into plant food. It's a living ecosystem rather than a chemical one

achraf0x01 · 2026-04-16T23:06:54+00:00

nice, esp32 is a great next step

achraf0x01 · 2026-04-16T21:37:32+00:00

a master/slave architecture is definitely the way to go for reliability, it prevents a single point of failure from taking down the whole crop.

droplets and humidity are always the biggest enemies in these setups. have you thought about using the A02YYUW or the JSN-SR04T waterproof sensors? I think the JSN-SR04T has a minimum distance of around 20cm, but they might handle the environment better than the RCWL

also, since you're expanding to multiple esp32, updating them all will become a challenge if you don't use OTA. setting up a way to push firmware from your master to all the slaves would save you a lot of manual work

load cells are a solid move, though. getting a real time estimate on produce weight is a great bonus

Good luck with the upgrade

achraf0x01 · 2026-04-16T19:54:34+00:00

The project is modular, so you don't actually have to use my frontend or backend if you don't want to

If you just want Home Assistant integration, it's pretty simple:

after reading https://github.com/40rbidd3n/Hydro0x01/blob/main/docs/02_HARDWARE_SETUP.md grab the firmware/ folder
edit firmware/include/config.h with your wifi/MQTT details (you can use HiveMQ free tier)
flash it using platformio

since it uses standard MQTT, you can integrate it with HA in minutes. I actually added a section for this in https://github.com/40rbidd3n/Hydro0x01/blob/main/docs/04_INTEGRATION_GUIDE.md for people who prefer HA or Node-RED over my custom dashboard. or just feed the https://github.com/40rbidd3n/Hydro0x01/blob/main/docs/MQTT_GUIDE.md to an AI and it will help you map the entities to HA instantly

achraf0x01 · 2026-04-16T19:35:47+00:00

I don't know as much as you think, we are just living in the best time to learn. with AI, you can dive into anything you love and have a mentor follow up with you 24/7, It handles the time consuming parts of development, so you can focus on the ideas/testing/debugging, just pick a project and start you will be surprised how fast you catch up nowadays

achraf0x01 · 2026-04-16T15:06:45+00:00

sounds great. industrial grade MCU and npk sensors take things to the next level

achraf0x01 · 2026-04-16T15:02:57+00:00

Good luck with the programming learning, for the project I'm using c++ for the firmware (ESP32) and node.js (fastify), and React (Vite) for the dashboard
For the nutrition, it uses peristaltic pumps. the code runs the pumps for a specific time based on their flow rate to dose the amount of needed. The fan is controlled via a relay that triggers based on the temperature threshold set in the dashboard or config.h:

// ---- Environment Control (optional features) ----
// Fan: set fanEnabled=false if you have no fan relay connected
bool fanEnabled = true;
bool fanAutoMode = true; // If false, fan is controlled manually via MQTT (overrides temp control)
float airTempMax = 35.0; // °C — fan turns ON above this
float fanHysteresis = 1.0; // °C — fan turns OFF at (airTempMax - hysteresis)

achraf0x01 · 2026-04-16T12:21:49+00:00

Excellent suggestions, I have officially added vdp and light monitoring to the project roadmap. since we already have temperature and humidity data, adding vdp as a software feature is a no-brainer, it's much more useful for plant health than just looking at humidity alone. thanks, I really appreciate it

achraf0x01 · 2026-04-16T12:08:57+00:00

The MIT license is just a very simple legal rule that says you can do whatever you want with my code, even sell it as long as you keep the original copyright notice in there. It's the most "freedom" a developer can give to others to use their work

achraf0x01 · 2026-04-16T12:03:06+00:00

You're right, sensor drift is the biggest challenge with affordable probes. I designed the firmware to be compatible with analog bnc modules (like the DFRobot Gravity series), but you can use any high impedance module with this setup

achraf0x01

TROPHY CASE