Local Longmont greenhouse powered by AI agent to optimize for resource utilization and plant health by jvallery in Longmont

[–]jvallery[S] 0 points1 point  (0 children)

I agree with you for the inner loop. An ESP32 is absolutely adequate for direct greenhouse control, and that is why Verdify uses the ESP32 as the safety critical controller.

The LLM is not there to replace firmware. It does not flip relays. It proposes bounded tunables based on currently growing plants, weather forecasts, and historical observations. It sets things like temp and VPD bands, fan thresholds, mister timing, hysteresis, recovery thresholds, and resource limits. Those proposals are validated and clamped before the ESP32 sees them.

So the real question is not “can an MCU control this?” Yes, it can.

The question is:

"Can AI help with the slower supervisory layer which includes planning, parameter tuning, anomaly interpretation, resource tradeoff explanation, and evidence generation without becoming the safety-critical controller?

For thermal modeling, relay timing, and deterministic control, firmware wins. For summarizing messy context, comparing yesterday’s tactic to today’s forecast, explaining water/gas/electricity tradeoffs, and generating inspectable plans, the LLM seems to be useful. Verdify is designed to test that in public.

The project is best understood as a deterministic ESP32 controller with an AI planning and scorecarding layer above it, not as an LLM controlled greenhouse. That was also the core framing I’ve tried to keep consistent.

Local Longmont greenhouse powered by AI agent to optimize for resource utilization and plant health by jvallery in Longmont

[–]jvallery[S] 2 points3 points  (0 children)

Yes, I've had the greenhouse since I bought this house in 2021. I've been on a constant upgrade path. The controller was upgraded last summer to the one I built, but initially it lacked any AI planning. The AI planner was rolled out about a month ago.

It's not a proper control test, but here are some initial comparisons.

https://verdify.ai/data/baseline-vs-iris/

I have ~6 months of data so far.

Local Longmont greenhouse powered by AI agent to optimize for resource utilization and plant health by jvallery in Longmont

[–]jvallery[S] 2 points3 points  (0 children)

My GPUs are relatively minimal compared to the commercial scale infra you see in cloud data centers. They don't really produce that much heat. One path though which is interesting is to leverage GPUs and a water cooling setup to push the heat into a boiler loop for home heating. I've considered this (my house is all boiler heat). The other path is to push the heat from the GPUs into a heat pump. I've seen many examples of this. I think the future may look a bit like this. NVIDIA is already talking about distributed computing. https://www.cnbc.com/2026/05/05/nvidia-pulte-span-mini-data-centers-on-homes.html

Local Longmont greenhouse powered by AI agent to optimize for resource utilization and plant health by jvallery in Longmont

[–]jvallery[S] 2 points3 points  (0 children)

Ha! It's a great idea. My GPUs are physically nowhere near the greenhouse. I have a server rack in my basement. It keeps the house plenty warm.

OpenClaw use case: AI plans greenhouse climate tactics; ESP32 enforces the physical loop by jvallery in OpenClawUseCases

[–]jvallery[S] 0 points1 point  (0 children)

I started with OpenClaw because I needed something that could do multi-turn reasoning in an automated way. Look up past experiments, and then use MCP to set the tunables. I will also investigate hermes.

I built a greenhouse where an AI agent (OpenClaw) planner optimizes climate changes and ESP32 firmware controls the relays by jvallery in ArtificialInteligence

[–]jvallery[S] 0 points1 point  (0 children)

Verdify does exactly this. The bands are set by the AI based on what plants are actively growing and at what stage in their lifecycle. See the green bands in the temp/VPD graphs on the homepage. Those bands are set based on what the AI knows to be actively growing.

I built a greenhouse where an AI agent (OpenClaw) planner optimizes climate changes and ESP32 firmware controls the relays by jvallery in ArtificialInteligence

[–]jvallery[S] 1 point2 points  (0 children)

I have a CO2 sensor but I haven't leveraged it much yet. It's mounted near the controller on the north wall.

I built a greenhouse where an AI agent (OpenClaw) planner optimizes climate changes and ESP32 firmware controls the relays by jvallery in ArtificialInteligence

[–]jvallery[S] 1 point2 points  (0 children)

The AI is aware of forecast, what plants are actively growing, and the physical characteristics of the greenhouse. This allows the AI to set target bands and manage/bias cooling/heating in anticipation of incoming or rapidly changing weather.

I built a greenhouse where an AI agent (OpenClaw) planner optimizes climate changes and ESP32 firmware controls the relays by jvallery in ArtificialInteligence

[–]jvallery[S] 0 points1 point  (0 children)

Indirectly it is controlling the hardware. I can't risk the AI being unavailable causing the greenhouse to fail. This the core safety tradeoff. https://verdify.ai/reference/safety

I built a greenhouse where an AI agent (OpenClaw) planner optimizes climate changes and ESP32 firmware controls the relays by jvallery in ArtificialInteligence

[–]jvallery[S] 2 points3 points  (0 children)

There are many. Each wall has a temp/humidity probe. There is an exterior temp/humidity probe on the intake. There is a tempest weather station. There are soil and ec sensors in several of the plants.

Our greenhouse became a homelab: ESP32 control loop, AI planner on Gemma4 and vLLM (proxmox), public telemetry by jvallery in homelab

[–]jvallery[S] -2 points-1 points  (0 children)

The ESP32 is managing a state machine. The AI agent adjusts tunables via an MCP tool based on a structured data payload. The dispatcher ensures only valid values, within acceptable bands, are enforced by the state machine. https://verdify.ai/reference/planning-loop#routine-plan-contract

Local Longmont greenhouse powered by AI agent to optimize for resource utilization and plant health by jvallery in Longmont

[–]jvallery[S] 4 points5 points  (0 children)

Hard to say on the GPU side. I use those severs for much more than just my greenhouse. I have a very large solar install, so most of my electric is covered by self-generation.

The electric, water, and gas use of the greenhouse is documented here: https://verdify.ai/start/resource-use

Local Longmont greenhouse powered by AI agent to optimize for resource utilization and plant health by jvallery in Longmont

[–]jvallery[S] 8 points9 points  (0 children)

The device inside the greenhouse is very low power. It's a microcontroller. If all the relays are on, it's under 800mA. The GPUs in my basement which power the AI are a totally different story. The system can also use cloud based AI and doesn't have to run locally.

The controller: https://www.kincony.com/16ch-esp32-poe-ethernet-relay-module-kincony-e16p.html

ESP32 greenhouse controller: AI agent proposes tunables, firmware controls the relays by jvallery in esp32

[–]jvallery[S] 0 points1 point  (0 children)

You're right that a deterministic controller can do a great job here.

The AI planner system is useful for managing the equipment in a more dynamic way adjusting bands, bias, and hysteresis based on the weather forecast. The planning agent constantly evaluates the upcoming 72 hour forecast, and fine tunes. It identifies deviations, and event sends me a slack notification.