A single diagnosis tells you what's wrong now. A history of them tells you whether you're getting better.

That's the gap PlantLab's new /history endpoint closes.

When you call /diagnose with a photo, you get back a single answer about a single plant at a single moment. Useful, and also limited. You can't tell whether the answer you got today is consistent with the answer you got last week. You can't tell whether the intervention you ran four days ago made things better or worse. You can't see a pattern across photos because the API forgets each call the moment it returns.

That's the gap /history closes.

What changed

Pro and Business accounts now have an opt-in setting that, when turned on, retains diagnosis history. The photo, the answer, the timestamp, the engine version, all queryable through a new /history endpoint. Pro keeps the last 90 days. Business keeps the last 365. Off means nothing is stored. The default is off.

There's also a Home Assistant sensor exposed for the count if you want it on a dashboard. The endpoint supports cursor-based pagination, which matters more than it sounds once you've been growing for a few months and your history grows past a screen.

What you can do with it today

Three things, on day one.

You can see trajectory. Whether a plant is improving or sliding. The leaf that read nitrogen-deficient last Sunday: is it still showing the same signal this Sunday, or has it moved? A single diagnosis can't tell you.

You can spot patterns across plants. If three different plants in the same tent keep coming back as overwatering, the watering schedule is the variable, not the plants. The room is the constant.

You can audit the API itself. Whether the model is consistent shot-to-shot on the same plant under the same conditions. Two photos two minutes apart, same lighting, same angle, should produce broadly the same answer. /history makes that an inspectable claim instead of a vibe.

What I want to build on top of it

The endpoint is the substrate, not the analysis. The reason it has the shape it does, opt-in, retention-bounded, paginated, machine-readable, is that I want certain things to be possible later. None of them exist today. I'm being deliberate about not promising them on a date.

A simple “this plant has been declining for X days” flag, computed from the history rather than the latest photo alone.

Intervention tagging. Mark a diagnosis with “I tried foliar Cal-Mag” and see whether the next photo improves. That requires a feedback loop the current API doesn't have. /history is one half of it.

Anomaly detection that respects time. A plant that's been healthy for six weeks suddenly returning a confident pest signal is a different event from a plant that's been borderline for six weeks. Without history the API has no way to tell those two apart.

All of those features need the data to exist in queryable form before they can be built. That's what /history is for.

The privacy posture

A stateless diagnosis API is genuinely stateless. You send a photo, you get an answer, the photo is gone. That posture is impossible the moment you start retaining anything, so the bar moves: if you're going to store, you store as little as possible, you make it opt-in, you delete on a known schedule, and you never share with a second party.

That's what /history does. Off by default. The toggle is in your dashboard and on the API. Tier-bounded retention. Rolling deletion.

It also slots into a wider set of changes this month that all point in the same direction. Analytics moved to Umami, EU-hosted, cookieless, no consent banner. The CDN moved to Bunny.net in Slovenia. The signup CAPTCHA moved to self-hosted Altcha. Each one of those moves cuts a third party out of the data path between you and PlantLab. Together they shrink the surface area of who sees what.

The point of all of that is straightforward. Your grow data is yours. The job of an API like this isn't to accumulate it, it's to give you an answer and stay out of the way.

How to use it

If you're on Pro or Business, the toggle is in your dashboard under Account settings. The API exposes the same setting. Once it's on, /history returns your diagnoses in reverse chronological order, paginated, with the same field shape as /diagnose plus a timestamp and the engine version.

Full docs at plantlab.ai/docs.

If you build automations and you've been waiting for a way to compare today's reading against last week's, this is the piece that was missing.

PlantLab's API now returns a reliability_score field on every diagnosis. A number from 0 to 1 telling you how likely the answer is to be correct on this specific image. It replaces the old diagnostic_confidence and safety_classification fields, which were rule-based guesses that I never trusted. The new score is much better at flagging the diagnoses that turn out to be wrong – especially on the hard cases, which is where you actually need it. Schema bumped from 1.x to 2.0.0. If you're integrating with PlantLab today, the migration is a one-line change.

The problem with “confidence” fields

Most diagnosis APIs return a confidence number along with each answer. PlantLab did too. For every condition the model spotted, the response included a confidence value between 0 and 1. On top of that, the response also carried two derived fields. diagnostic_confidence, a single overall trust number, and safety_classification, a three-way bucket of high, moderate, low.

Those derived fields were a heuristic. A small handful of rules that mostly looked at the top condition's confidence and rolled it up into a number. Heuristics work fine when the problem is simple. They fall apart when the failure modes are subtle.

In real traffic, the cases that matter are the ambiguous ones – photos where the answer isn't obvious from the image alone, and a single rule isn't enough to capture how confident the diagnosis really is. That's the slice where a trust signal earns its keep, and the slice where a rule-based composite tends to break.

A trust signal that works on the easy cases and stops working on the harder ones isn't really a trust signal. It's a confidence display.

What reliability_score does differently

reliability_score is a single number from 0 to 1 that estimates how likely the top diagnosis is to be correct on this specific image. Higher is better. Below 0.3 is a clear “double-check this one.” Above 0.7 is “the system is confident and the confidence holds up.”

It doesn't replace per-class confidence. Those still tell you how strongly the model picked each individual condition. What reliability_score adds is a separate answer to a different question – “is the entire diagnosis trustworthy on this particular image, or is something off?”

The analogy I keep coming back to: a junior diagnostician who always gives an answer, and a supervisor who looks over their shoulder. The supervisor doesn't redo the diagnosis. They judge whether each one looks trustworthy. The old diagnostic_confidence was a checklist the junior filled in themselves. reliability_score is the supervisor.

I held the new score to a higher bar than the old composite. On the ambiguous cases, it does a much better job of flagging the answers you should double-check before acting on them. On the easy cases, both fields agree – which is the only place they were ever going to agree, and not where the score earns its keep.

What changes in the response

If you're integrating with PlantLab today, here's what your code currently sees:

{
  "request_id": "550e8400-e29b-41d4-a716-446655440000",
  "schema_version": "1.2.0",
  "success": true,
  "is_cannabis": true,
  "is_healthy": false,
  "growth_stage": "flowering",
  "conditions": [
    { "class_id": "magnesium_deficiency", "confidence": 0.85 }
  ],
  "diagnostic_confidence": 0.85,
  "safety_classification": "high_confidence"
}

After the upgrade, that same image returns:

{
  "request_id": "550e8400-e29b-41d4-a716-446655440000",
  "schema_version": "2.0.0",
  "success": true,
  "is_cannabis": true,
  "is_healthy": false,
  "growth_stage": "flowering",
  "conditions": [
    { "class_id": "magnesium_deficiency", "confidence": 0.85 }
  ],
  "reliability_score": 0.91
}

Two fields removed. One field added. The rest of the response is identical.

reliability_score is omitted when the API doesn't return a condition diagnosis – for example, when the photo isn't of cannabis, or when the plant is healthy. In those cases, there's no diagnosis to score for reliability, so the field doesn't appear. Treat its absence as “no score available” rather than “low score.”

Migration

The change you make depends on what you were doing with the old fields.

If you were displaying diagnostic_confidence to a user, swap to reliability_score. The semantics are the same direction (higher is better, both 0-1), and the new value is more accurate.

If you were branching on safety_classification strings, pick thresholds on reliability_score instead. A reasonable starting point: above 0.7 is “Confident,” 0.3 to 0.7 is “Uncertain,” below 0.3 is “Low confidence.” Your application can use whatever cutpoints make sense – the score is a number, not a string, so you have full flexibility.

If you were ignoring the old fields entirely, the upgrade is automatic. Remove your code that references diagnostic_confidence or safety_classification (it'll get null going forward) and you're done.

The Home Assistant integration shipped a new release the same day as the API change, so existing HA users get the new sensor automatically. If you're using a custom integration, update it before the next API deploy if you can – sensors that read the removed fields will return null until the integration is updated.

Why a breaking schema, not deprecation

I considered keeping diagnostic_confidence and safety_classification as deprecated fields, returning the old values alongside the new score for a release or two. It would have spared everyone a migration step.

But it forces consumers to choose between two trust signals that can disagree. The old composite says “low confidence” on a photo where the new score says 0.95 – which do you trust? Worse, deprecated fields stick around for months, and integrators keep reading them instead of migrating. That's basically the entire failure mode of deprecation.

Cleaner break, single migration, no ambiguity. Schema bumped to 2.0.0 to make it loud. If your integration was on schema 1.x, you'll start getting 2.0.0 responses the next time you call the API. Field changes are documented above.

What's next

reliability_score ships as v1. The field semantics stay stable: a 0 to 1 trust score, present on diagnoses that returned a condition prediction. Future improvements land behind that contract. Same field, more accurate values, no code changes on your end.

If you migrate now, you're done with the migration.

PlantLab is free to try at plantlab.ai. Three diagnoses a day, results in milliseconds. The full API documentation, including the OpenAPI spec, lives at plantlab.ai/docs.

FAQ

Do I have to migrate immediately?

You'll start receiving schema 2.0.0 responses the next time you call the API. If your code reads diagnostic_confidence or safety_classification, those reads will return null. If your code branches on those fields, your branches will fall through to whatever default path you wrote. So the migration urgency depends on what your code does with null values – some integrations will degrade gracefully, others will break.

Is reliability_score the same as confidence?

No. confidence (still present in conditions[] and pests[]) is the model's per-class probability for one specific class – “how confident am I that this leaf shows magnesium deficiency?” reliability_score is a separate signal that estimates how likely the entire diagnosis is to be correct on this image. The two answer different questions, and you can use both.

What does it mean when reliability_score is missing?

The score is only computed when the API returns a condition diagnosis – that is, when the photo is cannabis and the plant is unhealthy. For non-cannabis photos or healthy plants, there's no condition prediction to score, so the field is omitted. Treat absence as “no score available,” not as a low score.

How is this different from just thresholding on confidence?

Per-class confidence values are the model's individual outputs. They tell you which classes were predicted strongly. They don't tell you whether the diagnosis as a whole holds up on a given image. reliability_score answers that broader question, which is usually the one you actually have.

Can I see PlantLab's diagnosis history for my key?

GET /usage returns daily and monthly counts. For per-request lookup, store request_id from each diagnose response – it's stable, returned in both the JSON body and the X-Request-ID header. Use it for support tickets and feedback submission.

Related reading: – The Work Nobody Sees: How I Ran 47 Experiments to Make PlantLab's AI Better – What goes into making the model more accurate, cycle by cycle – Yellow Leaves, Seven Suspects: How PlantLab Got Specific About Nutrient Deficiencies – The nutrient subclassifier that ships alongside this trust signal – How PlantLab's AI Diagnoses 31 Cannabis Plant Problems in 18 Milliseconds – The full pipeline

Most plant diagnosis tools give you a paragraph to read. PlantLab gives your automation system something to act on.

The model covers 31 cannabis conditions and pests at 99.1% balanced accuracy. Balanced means every class counts equally – a system that nails common deficiencies but misses rare pests does not score well. The output is structured JSON that Home Assistant, Node-RED, or a custom controller can read and act on without a person in the loop.

Why generic AI fails

The first time I tried AI for plant diagnosis, I uploaded a photo to ChatGPT. It told me I had a calcium deficiency. It was light burn. The two look nothing alike if you know what you are looking at, but ChatGPT was never trained specifically on plant images. It is a convincing generalist, and when it does not know, it guesses.

That is what most “AI plant diagnosis” apps actually do. Wrap a general-purpose language model, send your photo with a prompt, return whatever comes back. The output is confident, plausible, and sometimes wrong, and a new grower has no easy way to tell which time is which. It is also something you can do yourself for free, which makes paying for the service hard to justify.

The deeper problem is that even when these tools are right, they hand you prose. Useful for a person reading a screen. Useless for an automation system that needs to decide whether to adjust pH, run a fan, or send you an alert.

What PlantLab detects

The model covers 31 cannabis conditions and pests across four families.

Nutrient issues: nitrogen, phosphorus, potassium, calcium, magnesium, iron, boron, manganese, and zinc deficiencies, plus nitrogen toxicity.

Diseases: powdery mildew, bud rot, root rot, pythium, rust fungi, septoria, and mosaic virus.

Pests: spider mites, thrips, aphids, whiteflies, fungus gnats, caterpillars, leafhoppers, leaf miners, and mealybugs.

Environmental: light burn, light deficiency, heat stress, overwatering, and underwatering.

Every class scores above 95% detection accuracy, including the rarer ones.

What you get back

{
  "request_id": "550e8400-e29b-41d4-a716-446655440000",
  "schema_version": "2.0.0",
  "success": true,
  "is_cannabis": true,
  "is_healthy": false,
  "growth_stage": "flowering",
  "conditions": [
    { "class_id": "bud_rot", "confidence": 0.92 }
  ],
  "pests": [],
  "reliability_score": 0.88
}

Not a paragraph for a person to read and interpret. A machine-readable signal. Your controller sees 92% confidence on bud rot in a flowering plant and can ramp airflow, send an alert, or log the event – keeping you informed without forcing you to step in every time.

reliability_score is a separate trust signal on top of per-class confidence. It estimates whether the entire diagnosis holds up on this specific image, which is most useful on the hard cases – mixed symptoms, lookalike conditions, edge-case growth stages. There is more on it in How PlantLab Knows When It Might Be Wrong.

What's new in this release

The previous version of the model covered 24 conditions. This release brings it to 31. The additions came from what growers actually run into and ask about.

Bud rot is one of the worst things that can happen during flowering. Dense colas plus humid air invite Botrytis, and by the time you can see it with the naked eye, it has often already spread.

Heat stress causes leaf curling, foxtailing, and bleaching that new growers often confuse with nutrient issues. Splitting it into its own class prevents the misdiagnosis.

Fungus gnats are usually the first pest a new indoor grower meets. Caterpillars, leafhoppers, and leaf miners are common outdoor threats. Mealybugs are less common but brutal once they take hold. All five now have dedicated detection.

Boron, manganese, and zinc deficiencies fill out the micronutrient coverage. Less common than the macros, but harder to spot by eye because their symptoms overlap with other conditions.

A diagnosis that surprised me

I sent a sample of recent images through the live service to spot-check it against my own intuition.

One result stood out. The photo was a plant that looked underwatered – drooping, leaves curling, the classic signs. The model called it overwatered. I was ready to write that off as wrong, then I went back through earlier photos. The plant had been chronically overwatered for weeks. That ongoing stress had caused nutrient lockout, which then progressed into something that looked like underwatering. The model caught the underlying cause. Without that, I would have treated the symptom and made the problem worse.

What's next

A few things in the queue.

Multiple concurrent conditions in one image. Plants can have spider mites and a calcium deficiency at the same time. Today the API returns the primary diagnosis. Multi-label output is on the way.

Step-by-step automation guides. Home Assistant, Node-RED, and others – walkthroughs for wiring PlantLab into the stack you already run.

More real-world data. Photos from real tents, at real angles, in real lighting, sharpen the model on the conditions it actually sees – not just the clean reference shots.

PlantLab is free to try at plantlab.ai. The API returns structured JSON for every diagnosis – plug it into your automation stack and let your grow room see for itself.

Related reading: – Why I Built PlantLab – The origin story – How PlantLab Knows When It Might Be Wrong – The reliability_score field and schema 2.0 – Nitrogen Deficiency in Cannabis: A Visual Guide – Detailed guide for the most common deficiency – Yellow Leaves, Seven Suspects – Specific nutrient identification – API Documentation

A Node-RED flow that captures a photo on a schedule, sends it to PlantLab for diagnosis, and takes action based on the result. Push notifications, dashboard updates, MQTT messages to your controller, log lines into InfluxDB, or whatever combination you want. No Python. No YAML. Nodes and wires.

Setup runs about 25 minutes on a Node-RED instance that's already up. The cost is whatever camera you own plus PlantLab's free tier at 3 diagnoses a day. The output is a structured JSON result: 31 possible conditions, a growth stage, nutrient antagonism hypotheses, and confidence scores, all ready to feed into whatever comes next.

Node-RED suits growers who already have their tent wired up with visual flows. If you've got temp sensors piping into an InfluxDB dashboard, MQTT switches on a power strip, or a Telegram bot that announces fan speed changes, you already know the pattern. Plant health diagnosis is just another node in the chain.

Coming from Home Assistant? There's a tutorial for that too. Node-RED gives you more granular flow control and broader protocol support. HA gives you a cleaner device-and-entity model. Both work. Pick whichever one matches the rest of your setup.

Prerequisites

Before we start:

• Node-RED running (Docker, Pi, bare metal, or the Home Assistant add-on – any of them works)
• A camera that can deliver a JPEG – IP camera with snapshot URL, Frigate, ESP32-CAM, Wyze with RTSP bridge, Reolink, anything that responds to an HTTP GET with a JPEG or that you can shell out to ffmpeg for
• A PlantLab account – sign up free at plantlab.ai, copy your API key from the dashboard
• Optional but recommended: node-red-dashboard for a visual panel, node-red-contrib-image-tools if you want to resize photos before sending, an MQTT broker if your grow controllers talk MQTT

Camera tip: shoot the canopy from above or at a slight angle, with neutral light. Blurple grow lights throw the model off because everything comes out tinted purple. Either schedule the check during a lights-off window or use the camera's built-in flash. PlantLab wants to see actual leaf color, not a magenta smear.

Step 1: The Basic Flow

Here's the smallest flow that actually does something useful. Four nodes. Inject on a schedule, pull an image from the camera, POST to PlantLab, debug-log the result.

[inject: cron 08:00] -> [http request: GET camera.jpg] -> [http request: POST plantlab] -> [debug]

Open Node-RED, drag these four nodes in, and wire them together.

The inject node

• Repeat: at a specific time, 08:00:00
• Payload: empty (we only need the trigger)

The camera snapshot node (HTTP request)

• Method: GET
• URL: your camera's snapshot endpoint, e.g. http://192.168.1.50/snapshot.jpg or your Frigate http://frigate:5000/api/grow_tent/latest.jpg
• Return: a binary buffer

If your camera needs auth, add a basic auth header. If it's RTSP-only, use an exec node running ffmpeg -i rtsp://... -frames:v 1 -f image2pipe - and pipe the stdout through.

The PlantLab request node (HTTP request)

• Method: POST
• URL: https://api.plantlab.ai/diagnose
• Return: a parsed JSON object
• Headers: set in the function node below (not in the HTTP request node's UI)

Before this node, drop in a small function node to wrap the binary image as multipart form data and attach the API key header:

const boundary = '----NodeRedBoundary' + Date.now();
const bodyStart = Buffer.from(
    `--${boundary}\r\n` +
    `Content-Disposition: form-data; name="image"; filename="plant.jpg"\r\n` +
    `Content-Type: image/jpeg\r\n\r\n`, 'utf8');
const bodyEnd = Buffer.from(`\r\n--${boundary}--\r\n`, 'utf8');

msg.headers = {
    'X-API-Key': 'YOUR_API_KEY',
    'Content-Type': `multipart/form-data; boundary=${boundary}`
};
msg.payload = Buffer.concat([bodyStart, msg.payload, bodyEnd]);
return msg;

Put your API key in a Node-RED env variable or credentials node instead of hardcoding it. I wrote it inline for clarity.

The debug node

Hook this up to see the full response. You'll get something like this:

{
  "request_id": "req_abc123",
  "schema_version": "1.1.0",
  "success": true,
  "is_cannabis": true,
  "cannabis_confidence": 0.95,
  "is_healthy": false,
  "health_confidence": 0.87,
  "growth_stage": "flowering",
  "growth_stage_confidence": 0.9,
  "conditions": [
    {
      "class_id": "calcium_deficiency",
      "display_name": "Calcium Deficiency",
      "confidence": 0.92
    }
  ],
  "pests": [],
  "mulders_hypotheses": [
    {
      "excess": "potassium_excess",
      "explains": ["calcium_deficiency"],
      "evidence": 0.92,
      "evidence_count": 1
    }
  ]
}

The response can also include diagnostic_confidence, safety_classification, uncertainty_factors, environmental_patterns, and progression_risks. You can ignore the ones you do not need.

One thing worth knowing: the response is trimmed by omission. On a clearly healthy plant, you will NOT see a conditions: [] array – the field is left out entirely. Same with pests and mulders_hypotheses. Always guard with payload.conditions && payload.conditions.length before indexing.

Deploy. Click the inject node's button once to run it manually. If the debug panel shows a response with success: true, the plumbing is done.

Step 2: Branch on the Result

Now it gets interesting. You want different things to happen depending on what the diagnosis came back with. Drop in a switch node right after the PlantLab response, three outputs:

• Property: msg.payload.is_healthy
• Output 1: equals false (problem detected)
• Output 2: equals true (all good)
• Output 3: otherwise (covers the case where the image is not cannabis – is_healthy is omitted)

Always wire the third branch. If you accidentally point the camera at the lens cap, the wall, or your cat, the API returns is_cannabis: false with is_healthy left undefined. A two-output switch drops those silently. The third output catches them so you can log or send a “check your camera” notification instead.

Most of the work lives on the false branch.

A second switch for confidence

Inside the problem branch, add another switch:

• Property: msg.payload.conditions[0].confidence
• Output 1: >= 0.75 (high confidence – alert)
• Output 2: < 0.75 (marginal – log only)

Early-stage symptoms produce lower confidences. You don't want every 0.4 nitrogen-deficiency blip triggering a Telegram ping at 3 AM.

Step 3: Notifications

Telegram

If you have a Telegram bot set up, drop a telegram sender node on the high-confidence branch. Use a template node before it to format the message:

[ALERT] Plant issue detected

Condition: {{payload.conditions.0.class_id}}
Confidence: {{payload.conditions.0.confidence}}
Growth stage: {{payload.growth_stage}}

Mulder's hypothesis: {{payload.mulders_hypotheses.0.excess}}

Discord

Swap the Telegram node for node-red-contrib-discord-advanced and point it at a webhook. Same template works.

Home Assistant (via webhook)

If you run both HA and Node-RED, Node-RED can fire an HA webhook that triggers a mobile notification with the snapshot attached:

[http request POST: http://homeassistant:8123/api/webhook/plantlab_alert]

The webhook handler in HA does the actual notification. Useful if you already have notification channels, templates, and quiet hours configured over there.

Step 4: Close the Loop

This is where Node-RED pays for itself over a static dashboard. You can fire automations directly from the diagnosis.

Auto-dose Cal-Mag on calcium deficiency

Add a switch on the condition class:

• Property: msg.payload.conditions[0].class_id
• Output 1: equals calcium_deficiency

Then wire a change node to set the MQTT payload and publish to your dosing pump:

[mqtt out]
  topic: grow/pumps/calmag/set
  payload: ON

Then a delay node (5 seconds), then another MQTT message flipping it back OFF. Always notify yourself when a dosing automation fires. A false positive that dumps nutrients is a bad morning to wake up to.

[set pump ON] -> [delay 5s] -> [set pump OFF] -> [notify]

Ramp up fan speed on fungal detection

If the diagnosis returns powdery_mildew or similar with high confidence, push the fan speed up and drop target humidity in your environmental controller. Same pattern – switch on class_id, change node for the new setpoint, MQTT publish.

Log everything to InfluxDB

Regardless of what happened, log every diagnosis to a time-series database so you can build dashboards later. Drop an influxdb out node on the main line, before the switches. A function node preps the fields:

msg.payload = [{
    is_healthy: msg.payload.is_healthy ? 1 : 0,
    health_confidence: msg.payload.health_confidence,
    top_condition: msg.payload.conditions[0]?.class_id || 'none',
    top_confidence: msg.payload.conditions[0]?.confidence || 0,
    growth_stage: msg.payload.growth_stage
}];
return msg;

Now you have a Grafana dashboard of plant health over time. Symptoms drift slowly over days. Watching a confidence line trending up on one specific condition is more useful than catching the single moment it crosses 0.75.

Step 5: Dashboard

With node-red-dashboard installed, you get a web UI for free. A simple panel:

• ui_template showing the latest snapshot
• ui_text nodes for condition, confidence, growth stage
• ui_gauge for overall health confidence
• A manual ui_button wired back to the inject node so you can trigger a check on demand

Drop them all in a group called “Plant Health” and they render in a grid at /ui. Pretty enough for the tablet stuck to the kitchen wall.

Putting It Together

The whole flow described in prose:

Three triggers feed the same pipeline. Two scheduled injects (morning, evening) and one manual dashboard button. Each trigger pulls a camera snapshot, wraps it as multipart, POSTs to PlantLab, and parses the JSON response. From there the signal fans out. One branch writes every result to InfluxDB so you can graph drift over time. The other branch hits switch: is_healthy. The true side logs and stops. The false side continues into a confidence switch. Low-confidence detections only log. High-confidence detections fan out into Telegram, an HA webhook, and a switch: class_id that routes specific conditions into downstream automations (cal-mag pump on calcium deficiency, fan bump on mildew, whatever you wire up).

One diagnosis call in. One structured log entry. Two scheduled checks, one manual button. Zero or more notifications, zero or more automations fired. All from five node types: inject, http request, function, switch, change.

Troubleshooting

Add a catch node wired to your alerting. When the flow itself breaks, you hear about it. Two weeks of silent green checkmarks on a flow that quietly stopped running is worse than a flow that never ran at all.

Why Node-RED Instead of Writing This in Python

A few reasons.

Protocols come free. MQTT, HTTP, WebSockets, Modbus, CoAP, serial, SNMP – all one node away. Your dosing pump speaks MQTT, your camera speaks RTSP, your logger speaks InfluxDB line protocol, alerts go to Telegram or Discord. Doing that same glue in Python means pulling in four libraries and maintaining them yourself.

Visual flows match the mental model. “When the camera sees X, send Y to the pump and notify me on Z” is already a diagram in your head. Node-RED lets you lay it out on a canvas instead of translating between code and back.

You can change a running flow. Deploy swaps it in place, no restart. Handy for grow-room automation where you tune thresholds based on what the plants actually end up doing, not what you assumed they would.

If you prefer code, the same flow is about 40 lines of Python with requests, paho-mqtt, and a cron entry. Use whichever fits.

What the API Actually Gives You

The response has every field you need for automation. The ones that matter most:

mulders_hypotheses is the block most growers end up leaning on. If the diagnosis is calcium deficiency but the hypothesis says the real cause is potassium excess, adding more cal-mag makes things worse. That's the kind of tip that saves you a week of chasing the wrong fix. More on nutrient antagonism here.

FAQ

Do I need a dedicated PlantLab Node-RED node?

Not yet. The standard http request node handles it fine. A node-red-contrib-plantlab package is on the roadmap and will collapse the multipart wrapping into one node. Until then, the function snippet above does the job.

How does this compare to the Home Assistant integration?

HA gives you entities and a config flow. Node-RED gives you wires and broader protocol reach. If your setup is already Node-RED-centric, don't force HA into the middle just for this. If you have both, let Node-RED handle the flow logic and use HA webhooks for the notifications that already work well there.

Rate limits?

Free tier: 3 per day, 90 per month. Pro: 500 per month. A home grow with morning and evening checks fits the free tier with a spare daily slot. If you're monitoring multiple tents or running high-frequency checks during flower, Pro is probably what you want.

Does 0.80 confidence really mean 80% certain?

Close to it. Over our evaluation data, a score of 0.80 lines up empirically with about 80% correctness. Worth knowing when you set automation thresholds – a 0.60 threshold fires more often than a 0.80 one, at a predictable cost in false positives. More on how we diagnose here.

Does it handle images from plant apps?

The endpoint accepts any JPEG or PNG. Grow-log app, phone gallery, file drop on a NAS – same POST, same result.

PlantLab detects 31 cannabis conditions – nutrient deficiencies, pests, diseases, environmental stress – at 99%+ accuracy in 18ms. Structured JSON out, works with anything that speaks HTTP. Free tier at plantlab.ai. HA integration is open source at github.com/plantlab-ai/home-assistant-plantlab.

Start Here

Something looks wrong. Maybe the bottom leaves are yellowing. Maybe the tips are curling. Maybe you walked into your tent and something just looked off in a way you can't articulate but your gut knows isn't right.

So you did what every grower does: you took a photo, posted it online, and got twelve different answers. Someone said CalMag. Someone said flush. Someone said “two more weeks.” None of them agreed on what the actual problem is.

This guide won't do that. It walks through a systematic process: look at where the damage is, what it looks like, and narrow it down to a specific cause. No guessing, no bro science, no “could be anything, hard to tell from the photo.”

Step 1: Where Are the Symptoms?

Look at where the damage is happening. Location tells you more than color does.

Here's the rule that eliminates half the guesswork: mobile nutrients (nitrogen, magnesium, potassium, phosphorus) move from old leaves to new ones. When they run low, old growth sacrifices itself first. Immobile nutrients (iron, calcium) stay put – so deficiency shows up on new growth first.

Bottom-up damage? Mobile nutrient problem. Top-down damage? Immobile nutrient or environmental. That single distinction saves you from chasing the wrong diagnosis for a week.

Step 2: What Do the Leaves Look Like?

Yellow Leaves

Ah, yellow leaves. The “check engine light” of cannabis growing. Universally alarming, completely nonspecific. Seven different things cause yellowing, and the forum advice for all of them is “probably CalMag.” The pattern of yellowing is what actually matters.

Bottom-up yellowing with veins turning yellow? That's nitrogen deficiency – the single most common issue for cannabis growers. See our complete nitrogen deficiency guide.

Yellow leaves but genuinely can't tell which deficiency? You're not alone – even experienced growers get these confused. PlantLab's AI was specifically trained to distinguish between 7 nutrient deficiencies that look nearly identical to the human eye. It's more reliable than asking strangers on Reddit, and faster than waiting three days for the wrong treatment to not work.

Brown Spots and Edges

Curling Leaves

White or Discolored Patches

| White webbing between leaves | Spider mites | Fine webs between branches. Flip a leaf over – if you see tiny moving dots, you have a serious problem. | | Bleached/white tips | Light burn | Primarily on the top canopy, closest leaves to your light. Move the light up. | | Purple/red stems and undersides | Phosphorus deficiency, cold, or genetics | Three common causes: (1) genetics – many strains naturally run purple stems, (2) cold temperatures below 60F/15C trigger anthocyanin production independently of nutrition, (3) actual P deficiency, which also causes dark leaves, slow growth, and stiff/brittle foliage. If purple stems are the only symptom, it's almost certainly not phosphorus. |

Step 3: Check for Pests

Pests leave evidence. Nutrient deficiencies create patterns. Knowing the difference matters – treating the wrong cause wastes time and can make things worse.

A jeweler's loupe is the single best diagnostic tool you can own. A 10x loupe ($8) catches most pests; a 60x pocket microscope ($15) is needed for broad mites and russet mites, which are invisible at lower magnification.

| Thrips | Silver/bronze streaks, tiny elongated insects | Upper leaf surfaces, inside new growth. The streaks are where they've been feeding. | | Aphids | Clusters of small bugs, sticky residue (honeydew) | Stems, new growth tips. They reproduce fast – a few today, hundreds next week. | | Broad mites / Russet mites | Twisted, distorted new growth; glossy or plastic-looking leaves; stunted tops | Invisible to the naked eye (need 60x+ magnification). Often misdiagnosed as heat stress, pH problems, or calcium deficiency. One of the most devastating cannabis pests because they're identified too late. | | Fungus gnats | Small flies near soil surface | Topsoil, especially in chronically overwatered pots. Adults are harmless; larvae feed on root hairs and create entry points for pathogens like Fusarium and Pythium. Dangerous for seedlings, less so for established plants unless the infestation is heavy. | | Whiteflies | Cloud of tiny white insects when plant is disturbed | Leaf undersides. Shake the plant gently – if a cloud of tiny white things takes off, you know. | | Caterpillars | Frass on/near buds, unexplained cola browning, holes in leaves | Inside buds, under leaves, along stems. Outdoor grows especially. The real threat is budworms boring into dense colas – the frass they leave behind promotes bud rot, which is often worse than the direct feeding damage. |

The key distinction: Pest damage is random and localized – wherever the pest fed. Nutrient deficiencies are systematic – they follow predictable patterns based on nutrient mobility. If the damage pattern doesn't make sense for any deficiency, get the loupe out.

Step 4: Rule Out the Usual Suspects First

Before you diagnose a deficiency and start adjusting nutrients, check the three things that cause most of the problems most of the time. Boring advice, but it would prevent about 60% of the “what's wrong with my plant” posts on every growing forum.

pH (The Actual Answer to Most Problems)

Here's the uncomfortable truth: the majority of “deficiency” symptoms in cannabis are actually pH lockout. Every nutrient is sitting right there in the soil. The plant just can't absorb any of it because the pH is wrong.

Check your pH before you diagnose anything. If it's off, fix it, wait 3-5 days, then see if the symptoms are still progressing. This is less exciting than diagnosing a rare micronutrient deficiency, but it's correct far more often. “pH your water bro” is the one piece of forum advice that's right almost every time.

Watering (The Other Usual Suspect)

The “lift the pot” test is free and takes one second. If the pot is heavy, stop watering. If it's light, water it. More sophisticated than most diagnostic protocols, honestly.

New growers overwater because they're paying too much attention. The plant doesn't need water every day. If the soil is still moist 2 inches down, walk away. Watering your plant because you're anxious about it is the gardening equivalent of refreshing your email.

Light and Heat

• Light burn: Bleached/white leaf tips closest to light. Your light is too close. Move it up.
• Heat stress: Leaves taco upward, fox-tailing in flower. If your hand is uncomfortable at canopy height for 30 seconds, the plant is uncomfortable all day.
• Light deficiency: Stretching, thin stems, pale color. The plant is reaching for something that isn't there.

The Cannabis Deficiency Quick-Reference Chart

For when you've checked pH, watering, and environment and the problem is still getting worse:

The mobile/immobile rule is worth memorizing. It's the difference between diagnosing in 10 seconds and spending a week on GrowWeedEasy trying to match photos.

When Eyeballing It Isn't Enough

Visual diagnosis works when symptoms are textbook. In reality, symptoms are rarely textbook. They're a blurry phone photo of a leaf under a purple blurple light, and three different conditions look identical at that resolution.

It breaks down especially when:

• Multiple problems overlap – spider mites AND potassium deficiency at the same time. Treat one, miss the other, wonder why the plant isn't recovering.
• Early symptoms are subtle – the difference between “early nitrogen deficiency” and “normal bottom leaf aging” is obvious in a textbook photo and invisible in your tent at 6 AM.
• Similar conditions need distinguishing – potassium vs magnesium deficiency requires comparing leaf position, vein color, edge pattern, and progression simultaneously. This is where “add CalMag and see what happens” comes from – it's not laziness, it's that telling the two apart with your eyes is genuinely hard.

PlantLab's AI was trained specifically on these ambiguities. It analyzes 31 cannabis conditions and can distinguish between 7 nutrient deficiencies that experienced growers regularly confuse. Not because it's smarter than a grower with 20 years of experience – but because it's been trained on 200,000+ images and doesn't get fooled by blurple lighting. The model is also improved continuously from real grower photos, not trained once and left alone.

Try it free at plantlab.ai – 3 diagnoses per day, no credit card.

FAQ

What is the most common cannabis plant problem? Nitrogen deficiency, by a wide margin. It's the most common real deficiency, and pH lockout causing symptoms that look like nitrogen deficiency is even more common. If you can only learn to identify one thing, learn what nitrogen deficiency looks like. Then learn to check your pH so you can rule out the fake version.

Why are my weed plant's leaves turning yellow? It depends. (Sorry. But it really does.) Start with where: bottom leaves = nitrogen, magnesium, or potassium. Top leaves = iron or calcium. Everywhere at once = pH lockout or root problems. The answer to “why are my leaves yellow” is always another question: “which leaves, and what does the yellowing pattern look like?” The table in Step 2 above will narrow it down.

How do I tell if my cannabis plant is overwatered or underwatered? Both cause drooping, which is unhelpful. The difference is in the leaves: overwatered leaves feel heavy, plump, and the soil is still wet. Underwatered leaves are papery thin and the plant perks up within hours of getting water. The pot-lift test works: heavy pot = too wet, light pot = too dry. Overwatering is far more common than underwatering, because new growers hover.

Can a cannabis plant have multiple problems at once? Frequently. Stressed plants attract pests, incorrect pH causes cascading lockouts across multiple nutrients, and a spider mite colony feasting on a plant that's already potassium-deficient produces a confusing mess of symptoms. Prioritize the most severe issue first. Fix that, stabilize, then address the next one. Trying to treat everything simultaneously usually means treating nothing effectively.

Should I remove yellow or damaged leaves? If a leaf is mostly brown and crispy, remove it – it's done photosynthesizing and it's just attracting pests. If it's partially yellow, leave it alone. It's still working. The plant will drop it when it's done with it. Never remove more than 20% of foliage at once, or you'll trade a nutrient deficiency for light stress from suddenly exposed lower growth.

What does it mean when my marijuana plant leaves curl up? Usually heat or light stress. The plant is doing what you'd do if someone held a heat lamp over your head – curling up to reduce its exposure. Move the light higher, improve airflow, or reduce intensity. If the curling comes with brown crispy edges, that's potassium deficiency instead. If the leaves are dark green and curling down (the claw), that's nitrogen toxicity – you overfed it.

How do I know if it's a nutrient deficiency or a pest problem? Deficiencies are systematic: they affect leaves in predictable order (old-to-new or new-to-old), create consistent patterns (interveinal, marginal, uniform), and progress gradually. Pest damage is chaotic: random holes, stippling in patches, silvery streaks where something was feeding, and actual visible bugs if you flip leaves over and look. When in doubt, get a 10x loupe and inspect the undersides. If nothing is moving and nothing is webbed, it's probably not pests.

Detailed guides: – Nitrogen Deficiency: Complete Visual Guide – Calcium vs Magnesium Deficiency: A Visual Comparison – 7 Nutrient Deficiencies: How PlantLab Tells Them Apart – Nutrient Antagonism: When Adding More Makes It Worse – Spider Mites: Early Detection Before the Damage – Powdery Mildew: Visual Detection and Prevention – Bud Rot and Root Rot: Detection Before It's Too Late – How AI Diagnoses 31 Cannabis Conditions in 18ms – The Work Nobody Sees: 47 Experiments to Make PlantLab Better – Why I Built PlantLab

You adjusted your cal-mag for two weeks. The yellowing got worse. Then you saw the webbing.

That's how most growers discover spider mites – not when the problem starts, but when it's already out of control. The early damage looks so much like a nutrient deficiency that your first instinct is to adjust the feed. Meanwhile, a single female mite is producing thousands of descendants in a month.

Spider mites are the most destructive pest in indoor cannabis cultivation. Not because they're hard to kill – they aren't, when caught early – but because their early symptoms mimic nutrient problems so convincingly that growers lose their detection window treating the wrong thing entirely.

This guide covers visual identification at every stage, how to tell mite damage from a deficiency, and what actually works for treatment.

Quick Identification

Spider mites on cannabis produce tiny yellow or white speckles (stippling) on upper leaf surfaces where mites feed from below. Unlike nutrient deficiencies – which cause broad, uniform color changes across leaves – stippling appears as distinct pinprick dots scattered irregularly across the leaf. The damage is caused by Tetranychus urticae (two-spotted spider mite), an arachnid that punctures individual plant cells and drains their contents. By the time webbing is visible, the colony has been feeding for weeks.

Quick checklist: – Tiny yellow/white pinprick dots on upper leaf surface – Dots are irregular and scattered, not following veins – Leaf undersides show tiny moving specks (mites are 0.3-0.5mm) – Fine webbing between leaf tips or at branch junctions (advanced) – Damage starts on lower/inner canopy where airflow is poorest – Leaves eventually bronze, curl, and drop

Why Spider Mites Are So Hard to Catch

They look like a nutrient deficiency

The single most common spider mite mistake has nothing to do with treatment. It happens at identification.

Early stippling – those tiny yellow dots where mites have punctured cells – looks like the beginning of a calcium deficiency or light stress. The dots are small, scattered, and appear on older growth first. A grower sees yellowing dots on lower leaves and reaches for the cal-mag bottle. Two weeks of feed adjustments later, the dots have spread, the plant looks worse, and then the webbing appears.

This is not a knowledge failure. It's a pattern recognition problem. The visual difference between early mite stippling and early nutrient deficiency is subtle enough that experienced growers miss it regularly.

The diagnostic key: flip the leaf over. Nutrient deficiencies don't leave anything on the underside. Spider mites leave everything there – adults, eggs, shed skins, webbing. A 10x loupe makes this definitive, but even a phone camera zoomed in on the leaf underside will show the difference.

They breed fast enough to outrun your diagnosis

Spider mites reproduce faster than almost any pest a cannabis grower will encounter.

• Generation time: 7 days at 30°C (86°F). Egg to egg-laying adult in one week.
• Reproductive rate: A single female lays up to 100 eggs. Her daughters start laying within a week.
• Population math: One mite becomes thousands in a month at optimal temperatures. Two months of unchecked growth reaches millions.

This is exponential growth in the literal sense. The population you can't see on Monday is visible by Friday and webbing by the following Monday. The detection window – the gap between “early enough to treat easily” and “too late for simple solutions” – is approximately 5-7 days.

Every day of misdiagnosis as a nutrient issue is a day lost in that window.

Visual Symptoms by Stage

Days 1-7: Invisible Phase

Mites have arrived but the colony is small. Fewer than 10 adults on the plant. No visible damage to the naked eye.

What to look for: Nothing you can see without magnification. Preventive inspection with a 10x loupe on leaf undersides is the only detection method during this phase – or an AI that can catch the earliest stippling pattern in a leaf photo before your eye does.

Days 7-14: Early Stippling

What you see: – Scattered yellow-white dots on upper leaf surfaces – Dots are pinprick-sized, irregular spacing – Lower and inner canopy leaves affected first – Leaves may appear slightly dull or dusty

This is the critical detection window. The damage is visible but the population is still manageable. Treat now and you win. Wait, and you're chasing exponential growth.

What growers confuse it with: Calcium deficiency, magnesium deficiency, early light stress, pH fluctuation damage. The distinguishing test: check the leaf underside with a loupe or zoomed phone camera.

Days 14-21: Moderate Infestation

What you see: – Stippling thickens into visible patches of yellow/bronze discoloration – Fine webbing appears at leaf tips and where leaves meet stems – Leaf edges may curl upward – Multiple plants now show symptoms (airborne spread via “ballooning” on silk threads)

Webbing marks the transition from “problem” to “crisis.” The silk isn't just housing – it protects colonies from predators and spray treatments. Once webs are established, contact sprays have to penetrate the silk to reach the mites.

Days 21+: Severe Infestation

What you see: – Dense webbing covering bud sites, connecting leaves – Leaves are bronzed, curled, and dropping – Mites visible as tiny moving dots on webbing – Plant growth has visibly slowed or stopped – Webbing on flowers makes bud unusable

At this stage, the plant is losing more photosynthetic capacity than it can replace. During flower, this level of infestation is often a total crop loss for affected plants. The mites are feeding on sugar leaves and bract tissue, leaving webbing embedded in the flower structure. Even if you kill every mite, the webbing and fecal matter remain.

Where to Look: Detection Hotspots

Spider mites prefer warm, dry, still air – the conditions that exist in the center and lower canopy of most indoor grows.

Check first: – Undersides of lower and inner canopy leaves – Where two leaves overlap (creates still-air microclimate) – Near intake vents (common entry point) – Any plant closest to heat sources

Check second: – Leaf undersides on middle canopy – Branch junctions where stems create sheltered pockets – Nearby houseplants, clones, or recently introduced plant material

High-risk conditions: – Temperature above 27°C (80°F) and rising – Humidity below 40% RH – Stagnant air in lower canopy – New clones or plants introduced without quarantine – Adjacent rooms or gardens with ornamental plants

One fact most growers don't realize: spider mites travel on clothing, pets, and skin. If you've been in a garden with mites and walk into your grow room, you may be the vector. This is why quarantine protocols matter even for indoor-only grows.

They're arachnids, not insects

This matters more than you'd think. Spider mites aren't insects. They're arachnids – closer to ticks and spiders than to aphids or thrips. A lot of insecticides just don't work on them, and growers figure this out the expensive way: they buy whatever pest spray the grow shop recommends, apply it twice a week for a month, and the mites keep spreading.

If a product label says “insecticide” but doesn't specifically list mites or arachnids, it probably won't work. You need a miticide (specifically targets mites) or a broad-spectrum acaricide (targets arachnids generally). Some biologicals and organic options work by physical mechanisms – suffocation, desiccation – that don't depend on the pest's taxonomy. These are often the safest first-line choice.

Treatment Strategies

They evolve faster than you can spray

Spider mites develop pesticide resistance at a rate that makes most agricultural pests look slow. With a 7-day generation cycle, resistance emerges in weeks, not seasons. Some strains of T. urticae are resistant to dozens of active ingredients simultaneously.

Worse: some pesticides cause “mite flaring” – the surviving mites respond to the chemical stress by increasing their reproductive rate by up to 30%. The intuitive response of “spray harder, spray more” can accelerate the infestation rather than control it.

Single-product treatment strategies fail. Always rotate between different modes of action.

During Vegetative Growth

Immediate response (first 48 hours): 1. Isolate affected plants if possible 2. Remove and dispose of heavily infested leaves (bag them, don't compost) 3. Spray leaf undersides thoroughly with a contact miticide or biological

Biological controls: – Phytoseiulus persimilis – predatory mite that feeds exclusively on spider mites. Effective in vegetative growth and early flower. Needs humidity above 60% to thrive. – Neoseiulus californicus – predatory mite that tolerates lower humidity and also eats thrips. Better for dry grow rooms. – Amblyseius andersoni – generalist predatory mite, survives without prey by eating pollen. Good for preventive releases.

Organic sprays (moderate infestations): – Neem oil (azadirachtin) – disrupts feeding and reproduction. Apply to leaf undersides only. Do not use in flower – affects taste and may not fully degrade. – Insecticidal soap (potassium salts of fatty acids) – kills on contact by desiccation. Must directly contact the mite. Repeat every 3-5 days for 3 applications to catch new hatchlings. – Spinosad – organic-approved, effective on thrips but weak against mites on its own. Can supplement a rotation but shouldn't be a primary miticide.

Spray rotation protocol: – Week 1: Product A (e.g., insecticidal soap) – Week 2: Product B (e.g., neem oil) – Week 3: Product A again (or a different miticide) – Never use the same active ingredient twice in a row

During flower

This is where most growers panic, and for good reason. During flower, almost everything that kills mites also ruins buds.

Safe in flower: – Predatory mites (biological control – no residue, no taste impact) – Water rinse with slightly elevated pressure (dislodges mites physically, must reach undersides) – Cold snap trick: drop temperature to 15°C (60°F) for 3 days if possible. Mite reproduction nearly stops below 18°C (65°F). This buys time for predatory mites to work.

Avoid in flower: – Neem oil (taste contamination, doesn't fully degrade on flower tissue) – Pyrethrin sprays (residue on buds) – Sulfur (burns trichomes, affects terpenes) – Any systemic product (absorbed into plant tissue including flower)

If webbing is on buds: The honest answer is that those buds are compromised. Webbing contains fecal matter and shed mite skins that don't wash off. You can salvage the plant by removing affected flowers and protecting remaining buds with predatory mites, but heavily webbed buds should be discarded.

Prevention

A few euros spent preventing mites saves hundreds in lost crop. Prevention beats treatment every time, especially with a pest that breeds this fast.

Environmental controls: – Keep humidity above 50% RH during veg (mites thrive in dry conditions) – Ensure airflow reaches the lower canopy (oscillating fans, open plant structure) – Run temperatures below 27°C (80°F) when possible – HEPA filter on intake if growing in an area with outdoor mite pressure

Good habits: – Quarantine new plants for 7-14 days before introducing to your grow – Change clothes before entering grow room if you've been in other gardens – Inspect leaf undersides weekly with a 10x loupe – make it routine, not reactive – Remove dead leaves and debris from the grow space (harboring sites) – Avoid overly dense canopy – defoliate lower growth that gets no light and creates still-air pockets

Preemptive predators: – Release Amblyseius andersoni or N. californicus at transplant. These predatory mites establish a background population that intercepts spider mites before colonies form. Cost: roughly €20-30 per release for a small grow, every 4-6 weeks.

How AI detection changes the timeline

The spider mite problem is a timing issue. The window between “just arrived” and “exponential growth” is about 5-7 days. Most growers catch mites after stippling is already obvious – right at the edge of that window, or past it.

The main reason growers miss that window isn't inattention. Early stippling – those first scattered yellow dots where mites have punctured cells – looks almost identical to the start of a calcium or magnesium deficiency. Same distribution, same size, same location on older growth. A grower sees the dots, checks pH, adjusts the feed, and waits a week for results. By the time the nutrient hypothesis is ruled out and a loupe comes out, mites have had 7-10 days of uncontested growth. At one generation per week, that adds up.

PlantLab's model covers 31 cannabis conditions including spider mite damage. It catches the stippling pattern at the 10-dot stage, from a routine photo. Not a replacement for the loupe – nothing is – but it flags the pattern before you've mentally filed it as “probably cal-mag” and moved on.

Catching mites at day 7 instead of day 14 is the difference between wiping down some leaves and losing a crop.

Free at plantlab.ai – 3 checks a day.

FAQ

How do I tell spider mite damage from a nutrient deficiency? Flip the leaf. Spider mite damage shows as scattered pinprick dots on top with mites, eggs, or webbing underneath. Nutrient deficiencies cause broader color changes with clean leaf undersides. A 10x loupe on the underside is the definitive test.

Can I see spider mites without a magnifying glass? Adults are barely visible to the naked eye (0.3-0.5mm) as tiny moving specks on leaf undersides. Eggs and juveniles are too small to see without magnification. By the time mites are easily visible, the colony is large. Use a loupe or phone camera zoom for early detection.

How fast do spider mites spread between plants? In optimal conditions (above 27°C / 80°F, below 40% RH), mites can move from one plant to adjacent plants within 24-48 hours. They also “balloon” on silk threads carried by air currents, reaching plants across a room. A single infested plant can become a room-wide problem in 5-10 days.

Will neem oil get rid of spider mites? Neem works as part of a rotation, not as a standalone. It disrupts feeding and reproduction but doesn't kill on contact, and mites build resistance to it quickly. Rotate with insecticidal soap and other modes of action. And never use it during flower – it doesn't come off.

What kills spider mites instantly? Insecticidal soap and pyrethrin kill on contact, but only what they touch. You'll miss eggs. Plan for 3 rounds over 2 weeks to catch hatching cycles.

You won't smell it at first. By the time you do – that damp, musty sweetness coming off a cola that looked fine yesterday – you've already lost that bud and probably the ones touching it. You cut it open, and the inside is grey mush. A week from harvest.

Bud rot. It colonizes from the inside out, hiding in the densest parts of your canopy where airflow is worst and humidity is highest. By the time the exterior shows damage, the interior has been decomposing for days.

Root rot is the same story, underground. A plant that was drinking normally starts drooping despite a wet medium. You check the roots and they're brown, slimy, and smell like a swamp. The pathogen has been destroying the root system for a week before the canopy showed a single symptom.

What they share: the window between “detectable” and “devastating” is days, not weeks. Nutrient deficiencies give you time. Pest infestations give you time. Rot doesn't. It doubles and doubles, and by the time most growers catch it, the only option left is damage control.

Quick Identification

Bud rot is caused by Botrytis cinerea, a fungus that colonizes dense flower clusters from the inside out. The first thing you'll notice: a sugar leaf or two within a cola turning yellow or brown while everything around it stays healthy. That isolated patch of dead tissue – not matching any nutrient pattern – is your warning. Pull the bud apart and you'll find grey or brown tissue, soft and wet, with grey-white fuzz (mycelium) growing through it.

Root rot comes from several pathogens – water molds like Pythium (especially common in hydro) and true fungi like Fusarium (which hits both soil and hydro). The first sign is a plant that droops for no obvious reason even though you just watered. Growth slows. Roots shift from white to tan or brown. By the time the roots are dark brown, slimy, and smell rotten, the plant may not recover.

What separates rot from everything else: it's local. One cola dying while the rest of the plant looks fine. One section of roots going brown while others stay white. Nutrient deficiencies hit the whole plant uniformly. Rot has an epicenter.

Bud Rot: What to Look For

The Inside-Out Problem

Bud rot starts where you can't see it. Botrytis spores land on flower tissue, germinate in the humidity, and go straight for the densest part of the bud – the interior, where moisture sits longest. Outside? Green and healthy. Inside? Grey mush.

Doesn't matter how many cycles you've run. You can eyeball your canopy every day and miss it completely, because the infection is in the one place a surface inspection doesn't reach.

Early Symptoms (Day 1-3)

The first visible sign is almost always a single sugar leaf – or a small cluster of them – within a cola that yellows and wilts while the rest of the bud stays green. This is easy to dismiss as a light-deprived leaf dying naturally. It isn't.

What to look for: – A single yellowing/browning leaf within an otherwise healthy cola – The leaf pulls out easily with a slight tug (the stem base is already rotting) – The area around the discolored leaf feels softer or more moist than adjacent tissue – A faint musty smell when you press your nose close to the bud

Moderate Symptoms (Day 3-7)

• Brown or grey tissue visible when you gently spread the cola apart
• Multiple leaves in the same bud turning yellow or brown
• White or grey fuzzy mycelium visible inside the bud under magnification
• The affected area feels distinctly wet or spongy

Advanced Symptoms (Day 7+)

• Grey mold visible on the bud exterior
• Bud tissue is soft, wet, and pulls apart easily
• Dark brown or black discoloration spreading to adjacent colas
• Spore dust (grey powder) released when the bud is disturbed
• Unmistakable musty or ammonia smell

At this point, that bud is gone. Everything you do now is about keeping it from spreading.

Where Bud Rot Hits First

Bud rot isn't random. It goes where the moisture is:

Your main cola. Any thick, tightly-packed bud where moisture can't escape. Spots deep in the canopy where leaves overlap and trap humidity. Anywhere a fan leaf rests against a bud, creating a little moisture pocket. And anywhere the bud surface is already damaged – caterpillar bore holes, supercrop scars, anything that gave the fungus a way in.

If you're only going to inspect one thing daily in late flower, make it the main cola and any bud that's touching a fan leaf. That's where bud rot lives.

Root Rot: What to Look For

The Drooping Paradox

Root rot looks like underwatering. Plant's drooping, so you water it. The drooping gets worse, so you water more. And now you're feeding the exact conditions that are killing the roots.

The tell: is the medium already wet? Overwatering droop and root rot droop look identical from the canopy. The answer is always below the surface.

Early Symptoms (Day 1-5)

• Drooping or wilting even though the medium is wet
• Slowed growth rate compared to other plants in the same environment
• Roots shifting from bright white to off-white or light tan
• Slight sour or stale smell from the root zone (especially in hydro)

Moderate Symptoms (Day 5-14)

• Roots turning brown and developing a slimy texture
• Leaves yellowing from the bottom up (mimics nitrogen deficiency)
• Plant drinking less water than expected for its size
• Stems near the base feeling soft or mushy
• Distinct foul odor from the root zone

Advanced Symptoms (Day 14+)

• Dark brown, mushy root mass that falls apart when touched
• Severe wilting that doesn't recover with watering
• Lower leaves dropping rapidly
• Base of stem may show brown discoloration
• The entire root zone smells of decay

Hydro vs Soil vs Coco

Root rot behaves differently across growing media:

Hydroponic growers have one advantage here: you can actually see the roots. Check them daily. One brown root tip caught early is a ten-second trim. Caught late, it's a dead plant.

Why Speed Matters More Than Treatment

Most treatment guides bury the uncomfortable truth: by the time you've confirmed rot, your best options are already behind you. Both conditions double fast once established, and the pathogens produce spores (bud rot) or zoospores (root rot) that reinfect tissue you've already treated.

For bud rot: – Day 1-3: Remove affected cola plus 2-3cm of healthy tissue around it. Sterilize cutting tool between cuts. Drop humidity below 50%. Increase airflow. The remaining harvest is likely safe. – Day 4-7: You're removing multiple colas. Some adjacent buds may be internally compromised but not yet showing symptoms. Harvest early if possible. – Day 7+: Salvage what you can. Anything near the infected area should be assumed compromised.

For root rot: – Early stage: Hydrogen peroxide root drench (3ml of 3% H2O2 per liter for mild cases, up to 5ml/L for aggressive treatment), drop reservoir temperature below 20C / 68F, increase dissolved oxygen. Beneficial microbes (Bacillus, Trichoderma) as a preventive – not a cure, but they compete with pathogens. Note: H2O2 kills beneficials too, so don't use both simultaneously. – Moderate stage: Root pruning (remove all brown tissue), full reservoir change, lower temperature, and hope the remaining root mass can support the plant. – Advanced: The plant is dying. What's left of the root system can't support it. Sometimes the honest move is to pull it and focus on the plants you can still save.

Every day you don't catch it, your options get worse. Two days is the difference between losing one cola and losing a quarter of the canopy.

How to Distinguish Rot from Other Problems

Early rot symptoms can look like nutrient deficiencies, overwatering, or heat stress. The giveaway is where the damage is concentrated.

If damage is spreading from one spot and doesn't respond to feed or environment changes – treat it as rot. Verify later. You don't have time to be wrong slowly.

Environmental Triggers

Rot is an environmental disease. The pathogen is probably already in your grow room – Botrytis spores are everywhere. But it needs specific conditions to take hold.

Bud Rot Triggers

• Humidity above 60% during flower – this is the one that matters most
• Poor airflow through the canopy, especially within dense colas
• Temperature swings that cause condensation on flower tissue (lights-off drops are the usual culprit)
• Dense genetics – strains bred for bag appeal often produce bud structures that trap moisture
• Late flower, week 6-8, when buds are at their densest and you're tired of babysitting the dehumidifier

Root Rot Triggers

• Reservoir temperature above 22C / 72F in hydro – this is the big one
• Overwatering in any medium, especially with poor drainage
• Low dissolved oxygen in the root zone
• Contaminated medium or tools (reusing coco without sterilizing, dirty res)
• Dead organic matter sitting in the reservoir

The 60/22 Rule

Two numbers. That's all you need to remember: flower room humidity below 60%, reservoir temperature below 22C / 72F. Not arbitrary – those are the inflection points where Botrytis and Pythium growth rates drop off hard. Stay below them and you're making it difficult for the pathogen. Go above and you're rolling out a welcome mat.

Catching It Before You Can

With rot, speed is the whole game. Early symptoms look like half a dozen other things, and most growers burn their response time treating the wrong problem.

PlantLab's vision model detects both bud rot and root rot as distinct conditions. You get a specific diagnosis with a confidence score, not “something might be wrong with your plant.” The model was trained exclusively on cannabis images – over 2,000 verified bud rot samples alone – across every severity stage from the first discolored leaf to full colonization.

If you're growing one plant, daily inspection is enough. But for a larger canopy – or if you're running cameras on a timer – a system that flags bud rot at 6 AM on a Tuesday before you walk into the room is worth having.

Try it free at plantlab.ai.

FAQ

How fast does bud rot spread?

Fast. An entire cola can go from first visible symptom to grey mush in 48-72 hours under favorable conditions (humidity above 60%, poor airflow). During that window, spores are landing on neighboring buds and starting new infections that won't show for days. Inspect your densest colas daily in late flower. There's no substitute.

Can you save a bud with rot?

No. Once Botrytis is inside the flower structure, that bud is done. Cut the affected cola plus a margin of healthy tissue around it, sterilize your tool between cuts, and get humidity down. Everything after detection is about containment, not cure.

Does hydrogen peroxide cure root rot?

It kills Pythium on contact, but it also nukes every beneficial microbe in the root zone. Think of it as a reset button, not a treatment plan. Use it alongside temperature correction (below 22C / 72F) and better oxygenation. Once most of the roots are brown and slimy, H2O2 won't save the plant – there's not enough healthy root mass left to recover from.

Why does my plant droop even though the soil is wet?

Rotting roots can't absorb water even when they're sitting in it. The plant wilts, you water more, the root zone stays waterlogged, and the pathogen thrives. If a plant droops and the medium is already wet, stop watering and check the roots.

Can bud rot spread to other plants?

Absolutely. Botrytis cinerea produces airborne spores, and disturbing an infected bud – touching it, cutting it, even a fan blowing across it – sends them into the air. They land on neighboring plants and start the cycle over. When you remove infected colas, work carefully and bag the tissue immediately. Some growers hit neighboring plants with a preventive fungicide application after removal, which isn't a bad idea.

Something's wrong with your plant. The leaves look off. You post a photo to a growing forum and within minutes, three people reply: “CalMag.”

You could have posted a picture of your dog and someone would have said CalMag.

It's the universal answer to every cannabis problem, the “have you tried turning it off and on again” of indoor growing. Yellowing? CalMag. Spots? CalMag. Weird leaf curl? Believe it or not, CalMag. And hey – sometimes it works. But when it doesn't, most growers just add more CalMag, which can make things actively worse.

Here's the thing nobody on the forums tells you: calcium and magnesium are two different nutrients that cause two different problems in two different places on the plant. Dumping a combined supplement at every symptom is like taking both Advil and Tylenol every time anything hurts – sometimes you need one, sometimes the other, and sometimes the extra dose of the wrong one creates a new problem.

This guide breaks down what calcium deficiency actually looks like versus magnesium deficiency, where to find each one on your plant, and how to stop guessing.

Quick Identification

Calcium deficiency produces irregular brown spots and necrotic patches on newer, upper growth. Magnesium deficiency produces interveinal yellowing – green veins with yellow tissue between them – on older, lower leaves.

The single most useful diagnostic: location on the plant. Calcium can't move once the plant deposits it in cell walls, so when supply runs short, it's the newest growth that suffers first. Magnesium is mobile – the plant pulls it from old leaves to feed new ones, so the oldest leaves show damage first.

Lower leaves yellowing between the veins? Magnesium. Upper leaves developing brown dead spots? Calcium. Or Calcium = High, Magnesium = Low, if you want it super simple.

Why They Get Confused

Blame the Bottle

The supplement industry packages calcium and magnesium together because both are secondary macronutrients that RO and filtered water strips out. As a preventive baseline, that's fine. As a diagnostic tool, it's useless.

When a grower sees something wrong and reaches for the CalMag, one of three things happens:

1. The plant needed magnesium. The CalMag contains magnesium, so it helps. The grower walks away thinking “CalMag works” without learning anything.
2. The plant needed calcium. Same thing.
3. The plant needed one but not the other. This is where it gets ugly. Calcium and magnesium are both cations that compete for the same uptake sites on roots. Adding an excess of the one your plant didn't need starts blocking the one it did.

That third scenario is why “I added CalMag and it got worse” is a meme for a reason. It's not that CalMag is bad – it's that using it as a diagnostic shortcut can create the exact antagonistic lockout you were trying to fix.

The Photo Problem

Both deficiencies can produce yellowing. Both can cause spots. A photo of a calcium-deficient upper leaf and a magnesium-deficient lower leaf can look surprisingly similar without context. And context – which part of the plant, which leaves, what pattern – is exactly what gets lost in a blurry photo posted at odd hours.

Visual Symptoms: Side by Side

Calcium Deficiency

Shows up on new growth at the top of the plant – upper leaves, growing tips, youngest tissue.

What you'll see: – Irregular brown or tan spots that seem to appear overnight – The spots feel crispy and dead, not soft or yellow – New leaves coming in distorted, curled, or crinkled – Growing tips stunting or dying back – Stems developing weak, hollow sections in bad cases – Spots that don't follow any vein pattern – they just show up randomly

How it progresses: 1. Small brown spots appear on young leaves 2. Spots expand and merge into larger dead patches 3. Leaf edges curl inward and brown 4. Growing tips stunt or die 5. Stems weaken – the plant gets structurally fragile

The quick test: If you can crumble the affected tissue between your fingers, and the damage is on the top of the plant, calcium deficiency is your most likely suspect.

Magnesium Deficiency

Shows up on older growth at the bottom of the plant – lower leaves, middle canopy, the oldest tissue first.

What you'll see: – Yellowing between leaf veins while the veins themselves stay green (interveinal chlorosis) – Starts at the leaf edges and creeps inward toward the midrib – The classic “tiger stripe” pattern on fan leaves – Older leaves eventually going fully yellow, then brown, then dropping off – Veins staying distinctly green throughout – this is what separates it from nitrogen deficiency

How it progresses: 1. Lower leaf margins start yellowing 2. Yellowing spreads between veins, creating that green-vein / yellow-tissue contrast 3. Edges go brown and necrotic 4. Leaves curl upward slightly 5. Worst-hit leaves drop

The quick test: Green veins with yellow tissue between them, starting from the bottom of the plant. If the veins are yellowing too, that's nitrogen, not magnesium.

The Comparison Table

What Else It Could Be

Calcium and magnesium each have their own lookalikes. Getting these wrong sends you down the wrong treatment path.

Calcium vs Potassium

Both produce brown, crispy leaf edges. Calcium does it on new growth with irregularly placed spots. Potassium does it on older leaves with a defined burned-edge pattern that starts at tips and margins and works inward. If the crispy edges are at the bottom of the plant, think potassium before calcium.

Magnesium vs Nitrogen

Both cause yellowing on older leaves. The tell is the veins. Magnesium keeps the veins green – the yellowing is only between them. Nitrogen yellows the entire leaf uniformly, veins and all. No interveinal pattern means nitrogen, not magnesium.

Magnesium vs Iron

Both cause interveinal chlorosis. Same pattern, opposite location. Magnesium hits old leaves at the bottom (mobile nutrient moving to new growth). Iron hits new leaves at the top (immobile nutrient that can't be redistributed). If the interveinal yellowing is at the top of the plant, it's iron. Bottom, magnesium. This one is actually definitive.

Common Causes

Why Calcium Runs Low

Reverse osmosis or filtered water. Tap water naturally contains calcium. RO strips it. If you switched to RO without adding calcium back, this is probably your answer.

Low pH. Below pH 6.0 in soil, calcium is still physically present but chemically locked out. You can add all the calcium you want – the plant can't access it.

Excessive potassium or ammonium. Both compete with calcium for root uptake. Those high-K bloom feeds? They can induce calcium deficiency even when there's plenty of calcium in the medium.

High humidity. Calcium moves through the plant via transpiration. In very humid environments, transpiration slows, and calcium stops reaching the growing tips. This is the one that catches experienced growers off guard – everything else looks perfect but the new growth keeps getting spots.

Why Magnesium Runs Low

Coco coir. The single most common cause in modern indoor growing. Coco has a natural affinity for calcium and magnesium cations – it holds onto them rather than releasing them to roots. If you grow in coco and don't buffer for this, magnesium deficiency is basically guaranteed.

Too much calcium supplementation. Ironic, right? Excess calcium blocks magnesium at root exchange sites. The fix for one deficiency can cause the other. This antagonistic relationship is why “just add CalMag” is sometimes exactly the wrong move.

Low pH. Same as calcium – availability drops below pH 6.0.

Intense LED lighting. LEDs drive more photosynthesis per watt than HPS, and magnesium is the central atom in every chlorophyll molecule. More light means more chlorophyll demand means more magnesium consumption. Growers who switch from HPS to LED at the same feed rate often see magnesium deficiency appear within two to three weeks. It's not the lights causing the problem – they're just exposing a margin that was previously fine.

Treatment

Fixing Calcium Deficiency

Check pH first. If your root zone is below 6.0, no amount of calcium will help – it's locked out. Correct to 6.0-6.5 (soil) or 5.8-6.0 (hydro/coco) before you add anything.

Use a calcium-specific supplement. Calcium nitrate provides calcium without adding magnesium. This matters when your magnesium levels are fine and you don't want to throw off the ratio.

Dolomite lime for soil. Slow-release calcium and magnesium. Better as a preventive amendment mixed in at planting than as a mid-grow rescue.

Look at competing cations. Running a heavy bloom feed with high potassium? The K might be the reason calcium can't get through. Temporarily dial it back.

New growth should improve within 5-7 days. The damaged leaves won't recover – don't wait for them to. Watch the new growth above the damage zone instead.

Fixing Magnesium Deficiency

Check pH first. Same story – lockout before deficiency.

Epsom salt. 1-2 teaspoons per gallon of water. Magnesium sulfate is the fastest targeted fix and it's cheap. Your plant doesn't care that it came from a $3 bag at the pharmacy.

Foliar spray for speed. 1 teaspoon Epsom salt per litre of water, sprayed directly on affected leaves. Foliar absorption bypasses whatever root problem is blocking uptake. Useful as a quick fix while you sort out the root zone.

Reduce calcium if you over-supplemented. If you've been heavy on CalMag or calcium nitrate, the excess calcium may be the reason magnesium can't get through. Sometimes the treatment is subtraction, not addition.

Foliar spray shows results in 3-5 days. Root-zone correction takes 7-10 days. Same as calcium – old leaves won't recover, but the damage should stop spreading and new growth should come in clean.

Prevention

Test your water. Know your baseline calcium and magnesium before adding anything. Tap water in many regions provides enough of both. If you're on tap water and getting deficiency symptoms, the problem is almost certainly pH or antagonism, not supply.

Manage your pH. Root zone between 6.0-6.5 (soil) or 5.8-6.0 (hydro/coco). This single practice prevents more deficiencies than every supplement combined.

Match your medium. Coco growers need more CalMag than soil growers. LED growers need more magnesium than HPS growers. Generic feeding charts are written for average conditions – adjust for your actual setup.

Watch the ratio. Optimal Ca:Mg is 3:1 to 5:1. When this drifts – usually from over-supplementing one side – the other becomes deficient through antagonism, not absence. You can cause a deficiency by adding too much of the other nutrient. That's the cruel joke of cation chemistry.

How AI Detection Works

This confusion between calcium and magnesium is a pattern recognition problem at its core. The symptoms are visually distinct – brown spots versus interveinal yellowing, top versus bottom – but at 2 AM, staring at a phone photo of a leaf under a blurple light, those distinctions get fuzzy. The human answer to “CalMag or not?” has always been “post a photo and hope someone experienced is online.”

PlantLab's nutrient subclassifier was trained on exactly this confusion pair. When the primary model flags a nutrient issue, a specialist second-pass model distinguishes between seven specific deficiencies – including calcium and magnesium individually. That two-stage approach resolves 93% of the nutrient misclassifications a single model would make.

The subclassifier tested at 99.5% accuracy on 15,000+ held-out images. That number matters most on the hard cases: telling calcium from magnesium when the symptoms overlap and the photo quality isn't great.

One photo. A specific answer. Not “CalMag deficiency” – calcium or magnesium, with a confidence score attached.

Try it free at plantlab.ai – three diagnoses per day, no credit card.

FAQ

Can a plant have both calcium and magnesium deficiency at the same time?

Yes, and it's common with RO water or unbuffered coco. You'll see interveinal yellowing on lower leaves (magnesium) and brown spots on upper leaves (calcium) at the same time. This is the one scenario where reaching for the CalMag bottle is genuinely the right call. Confirm with pH testing first – if pH is the root cause, a single correction may fix both.

Is CalMag ever the right answer?

For prevention, absolutely. As a baseline addition to RO water or coco grows, CalMag works well. The problem is using it as a diagnostic reflex – adding it before you've figured out which nutrient is actually short. If only one is deficient, a targeted supplement avoids throwing off the ratio of the one that was fine.

Why do LED growers see more magnesium issues?

Magnesium is the central atom in chlorophyll. LEDs drive more photosynthesis per watt than HPS, which means more chlorophyll turnover, which means higher magnesium demand. Growers who switch to LEDs at the same feed rate they used under HPS often see magnesium deficiency show up within weeks. The plant was fine before because it wasn't photosynthesizing as hard.

How long before I see improvement after treatment?

Foliar magnesium spray: 3-5 days. Root-zone magnesium correction: 7-10 days. Calcium (new growth): 5-7 days. In every case, the old damaged leaves are done – they won't green back up. Watch the new growth above the damage.

Can pH lockout cause both deficiencies at once?

Yes. Both calcium and magnesium availability drops sharply below pH 6.0. A single pH correction can resolve what looks like a dual deficiency without adding any supplements at all. This is why “check pH first” appears in every treatment section above. It's boring advice, but it's boring because it works.

It looks like your plant is getting frosty. White powder spreading across the leaves, that pale shimmer catching the grow light. Then you touch it, and your finger comes away white.

That's not trichome development. That's powdery mildew – and if you're seeing it now, the infection has been active inside your plant for up to two weeks already.

Powdery mildew is one of the most misidentified conditions in cannabis cultivation – not because the advanced stage is hard to recognize, but because early-stage colonies genuinely look like trichome buildup to the untrained eye. Growers see white on their leaves and feel reassured rather than alarmed. By the time the mistake is obvious, the fungus has spread.

This guide covers visual identification at every stage, how to distinguish PM from trichomes and other lookalikes, and what to do when you find it.

Quick Identification

Powdery mildew on cannabis appears as white, flour-like patches on leaf surfaces that transfer to your finger when touched. Unlike trichomes – which are crystalline, sticky, and firmly attached – powdery mildew is fuzzy, powdery, and wipes off. It typically starts on older, lower leaves and can spread from a single infected plant to your entire grow within 5-10 days under favorable conditions.

Quick checklist: – White powdery patches on leaf surfaces (usually upper side) – Fuzzy texture, not crystalline or glittery – Transfers to your finger when touched – Wipes off with cloth (trichomes stay attached) – Started on older, lower leaves – Circular colony patterns, expanding outward

Why Powdery Mildew Is So Destructive

The Timing Problem

Powdery mildew is caused by obligate biotrophic fungi – primarily Golovinomyces species (formerly classified as Erysiphe) – that require a living plant host to survive. As an obligate biotroph, the fungus spends its first 7-10 days growing inside plant tissue, establishing a mycelial network before producing the visible white sporulation on the surface.

The practical implication: by the time you see powdery mildew, you're already two weeks behind.

This timing overlaps with the worst possible moment in the grow cycle. PM typically produces visible symptoms approximately two weeks into flowering – when plants are at their most developed and most valuable. A disease that becomes visible at week two of a nine-week flower has seven weeks to damage a mature crop.

The Spread Problem

Once sporulating, powdery mildew spreads through airborne spores called conidia. Unlike many fungal diseases that require water droplets to spread, PM spores travel through air and remain viable in typical grow room conditions. A single infected plant can contaminate an entire facility within 5-10 days.

This is not a slow disease. It spends two weeks being invisible, then spreads rapidly.

Visual Symptoms by Stage

Days 1-7: No Visible Symptoms

The fungal network is developing inside plant tissue. Nothing is visible externally. The only detection method during this phase is molecular PCR testing – available commercially but not practical for most growers as a daily routine.

What to do: Prevention only. No reactive treatment exists for pre-symptomatic infection.

Days 7-14: Early Visible Stage

What you see: – Fine white coating on upper leaf surface, often concentrated near veins – Circular “chalk-dust rings” as colonies grow radially from infection points – Small, discrete white spots (1-5mm diameter) resembling flour or powdered sugar – Patches separated by healthy-looking green tissue initially

This is when intervention is most effective. Catching PM at this stage – and responding within 48 hours – gives you the best chance of containing the infection before airborne spread reaches other plants.

Days 14+: Advanced Stage

What you see: – Spots grow larger and merge into confluent white coverage – Thick, prominent coating across entire leaf surfaces – Fuzzy, hair-like texture that can resemble spider webs or white cotton candy in severe cases – Affected leaves turn yellow (chlorosis) as photosynthetic capacity is reduced – Leaf death and necrosis in severely affected tissue – Contamination of flower bracts and bud sites

At this stage, individual plant treatment may still limit damage, but facility-wide spread is likely already underway.

Where to Look: Detection Hotspots

Not all areas are equally at risk. Focus visual inspections here:

Check first: – Upper surfaces of older, lower leaves – Corners with poor airflow – Areas where leaves touch each other – Near the base of the plant

Check second: – Lower leaf surfaces – Leaf petioles and stems – Flower bracts and bud sites – Plants adjacent to any previously infected individual

High-risk conditions: – Humidity above 60% (optimal for PM at 95%+) – Temperature 68-86°F (20-30°C) – Poor air circulation or stagnant air pockets – Overcrowded plants with leaf-on-leaf contact – Recently introduced plant material (a common entry point)

One counterintuitive note: many growers assume low humidity prevents powdery mildew. It slows initial infection, but once PM is established, the fungus can continue growing even below 50% relative humidity. Humidity reduction is a preventive tool, not a cure.

Powdery Mildew vs. Trichomes: The Critical Distinction

This comparison matters because the error goes in both directions – growers see PM and think “good frost,” and they sometimes see heavy trichome coverage and worry it's disease.

Three Tests to Confirm

Touch test. Lightly rub the white area with your finger. PM transfers as a dusty powder. Trichomes are sticky and stay on the plant.

Wipe test. Try to wipe the coating with a cloth. PM wipes off cleanly. Trichomes remain attached.

Magnification (10x loupe). Under magnification, trichomes show distinct mushroom-shaped heads on uniform stalks. PM looks like fuzzy, irregular filaments with no consistent structure.

If you're unsure after all three tests, assume it's PM and treat accordingly. The cost of a false positive – treating a healthy plant – is much lower than the cost of a false negative.

Distinguishing From Other Conditions

Powdery Mildew vs. Bud Rot (Botrytis)

Both can appear during flowering, but they start in different places and look different up close.

• PM: Starts on leaf surfaces as white powder, spreads outward
• Bud rot: Starts inside dense bud tissue as gray-brown mold, spreads inward
• PM: Dry, wipes off as powder
• Bud rot: Slimy, penetrates tissue, leaves mushy gray-brown areas when probed

Powdery Mildew vs. Spider Mite Webbing

Heavy spider mite webbing can be confused with PM in advanced stages.

• PM: Powdery coating directly on leaf surfaces, no web structure
• Webbing: Actual filamentous strands connecting leaves and stems, visible as a network with tiny mites present
• PM: Surface phenomenon on the leaf
• Webbing: Spans between plant structures

Powdery Mildew vs. Fertilizer Residue

Spray residue and fertilizer salt deposits are a common false positive.

• PM: Fuzzy texture, grows and expands over days
• Residue: Crystalline, stays fixed, doesn't spread
• PM: Circular colonies from infection points
• Residue: Irregular splatter pattern matching where spray landed

Treatment and Prevention

If You've Found It: Immediate Steps

1. Isolate the infected plant. Remove it from the grow space carefully – don't shake the leaves, which disperses spores.
2. Remove heavily infected leaves. Seal them in a bag before removal. Dispose of, don't compost.
3. Increase airflow immediately. Run oscillating fans, check that exhaust is adequate.

4. Apply treatment to the infected plant and all immediate neighbors:

   • Potassium bicarbonate spray (effective at any stage, flower-safe)
   • Copper-based fungicides (veg stage only)
   • Neem oil (veg stage only – off-gasses problematically in flower)
   • Commercial PM treatments labeled as flower-safe for late-stage infections

5. Inspect every other plant in the grow. Assume airborne spread has already occurred. Look for early colonies on older lower leaves of adjacent plants.

Prevention

Environmental control (most effective): – Maintain humidity below 60%, below 45% in late flower – Install oscillating fans for continuous air movement – Prevent leaf-on-leaf contact through spacing and selective defoliation – Maintain stable temperature – fluctuations create favorable infection windows – Consider HEPA filtration between grow cycles to reduce ambient spore load

Cultural practices: – Inspect plants daily, particularly lower leaves and poor-airflow corners – Quarantine any new plant material for at least two weeks before introducing to your grow – Sterilize tools between plants – Remove dead leaves promptly – they create moisture pockets

Preventive treatments (before symptoms appear): – UV-C light treatment between grow cycles kills residual spores – Preventive potassium bicarbonate or copper sprays provide significantly better protection than reactive treatment after symptoms appear – IPM programs that address PM as a standing preventive protocol, not a reactive one

How AI Detection Works

Powdery mildew is fundamentally a texture classification problem – distinguishing the powdery, irregular surface of PM colonies from the crystalline structure of trichomes and the smooth surface of healthy leaf tissue.

PlantLab's model analyzes:

• Color contrast: White patches against green leaf tissue create a high-contrast signal the model identifies reliably
• Texture signature: PM colonies have a granular, matte surface texture measurably distinct from trichomes (crystalline) and healthy leaf (smooth with natural sheen)
• Colony geometry: PM grows in circular patterns from infection points with fuzzy, irregular edges – different from the uniform distribution of trichome coverage
• Location context: Where on the plant the pattern appears matters; PM preferentially affects older, lower leaves in early infection

Early-stage detection – colonies as small as 5mm – catches infection when treatment options are broadest. Automated daily scanning catches what manual inspection misses when you're managing more than a few plants.

Try it free at plantlab.ai – 3 diagnoses per day, no credit card required.

FAQ

Can I smoke buds with powdery mildew? No. PM spores and fungal material can cause respiratory issues, particularly for anyone with lung conditions or compromised immunity. Infected flower should be disposed of, not consumed.

Does powdery mildew spread to other plants? Yes, rapidly. Airborne spores can reach every plant in a contained grow space within 5-10 days under favorable conditions. Isolate infected plants immediately and inspect everything nearby.

Can plants recover from powdery mildew? Mildly infected plants can survive and produce with aggressive treatment, but affected tissue doesn't recover. The goal is to stop the spread. Heavily infected plants in late flowering are usually a loss.

Does lowering humidity kill powdery mildew? It inhibits new infection but doesn't eliminate established colonies. PM can remain active even below 50% relative humidity once established. Humidity reduction is a prevention tool, not a cure for active infection.

When is powdery mildew most likely to appear? Typically around two weeks into flowering, when dense bud sites create microclimates with trapped humidity and reduced airflow. It can appear at any life stage given favorable conditions, but flowering onset is the highest-risk window.

PlantLab's AI detects 31 cannabis conditions – including powdery mildew, bud rot, and 7 specific nutrient deficiencies. Start diagnosing free at plantlab.ai.

PlantLab now runs a specialist model after detecting any nutrient issue. Instead of “nutrient deficiency,” the API returns “potassium deficiency” or “magnesium deficiency” or whichever of the seven it actually is. Tested and validated at 99.5% accuracy on 14,182 real-world images it has not seen before. Same API, same JSON shape – no changes required on your end.

The Problem With “Nutrient Deficiency”

Ask any experienced grower what's wrong with a yellow cannabis leaf and you'll get a look that says: it depends.

Yellow leaf edges? Could be potassium deficiency. Or magnesium deficiency. Or potassium deficiency causing secondary magnesium lockout. Or nitrogen toxicity making an unexpected debut as interveinal chlorosis. Or pH off by half a point, causing any of the above at once.

The standard advice at this point is: “Add CalMag and see what happens.” Sometimes that's right. Sometimes it makes things worse. Sometimes it's right for the wrong reasons.

PlantLab's Stage 2 model was already good at detecting that a nutrient problem was present – 99%+ accuracy across all 31 conditions. But “nutrient deficiency” as a diagnosis is only half the answer. Potassium deficiency and magnesium deficiency are treated differently. Nitrogen deficiency and nitrogen toxicity are treated opposite to each other. The generic classification was accurate. It just wasn't useful enough.

What the Subclassifier Does

The new nutrient subclassifier is a second-pass specialist that runs only when Stage 2 detects a nutrient condition. Its job is narrow: take the image that triggered a nutrient flag and determine which specific nutrient is responsible.

It was trained on 200,000 images, selected specifically to represent the hard cases – the pairs of conditions that look the most alike under the camera. Not a bigger version of Stage 2. A focused model with a focused problem.

The Seven Classes

The subclassifier currently handles:

Calcium deficiency — upper leaf distortion, brown spots with yellow halos, new growth first	Iron deficiency — interveinal chlorosis on young leaves; veins stay green while tissue yellows
Magnesium deficiency — interveinal chlorosis on older leaves; mobile nutrient, progresses bottom-up	Nitrogen deficiency — uniform pale yellowing from lower leaves upward; oldest growth first
Nitrogen toxicity — dark blue-green, claw-shaped tips curling down; not a deficiency, the opposite	Phosphorus deficiency — purple-red discoloration on undersides and stems, common in cold or early veg
Potassium deficiency — brown, crispy scorched edges at leaf margins; progresses inward

These are the seven classes that generated the most diagnostic confusion in Stage 2. They share enough visual features that a generalist model regularly gets them wrong – not randomly, but in consistent patterns.

The Confusion Pairs

The specific pairs that Stage 2 was systematically mixing up:

K ↔ Mg – Both show yellowing that progresses from lower leaves, affecting older growth. Leaf margins vs. interveinal chlorosis is the tell, but early presentations overlap.

K ↔ N – Potassium deficiency causing tip burn and nitrogen deficiency causing general yellowing both start at the bottom of the plant.

Mg ↔ N – Both are mobile nutrients that deplete oldest tissue first. The yellowing progression is similar; the pattern of which tissue goes first is what separates them.

Mg ↔ Fe – Interveinal chlorosis is the signature symptom of both. The difference is which leaves are affected (new growth for iron, old growth for magnesium), but this requires accurate growth stage context.

N deficiency ↔ N toxicity – One is too little, one is too much. The visual signatures are distinct to an experienced grower but genuinely confusing for a model trained to see both ends of the spectrum.

These aren't edge cases. They're the day-to-day diagnostic mistakes that cause growers to add CalMag to a potassium deficiency, or flush a nitrogen toxicity that needed nothing but time.

Validation

The model was validated on 14,182 real-world nutrient images – photos from actual grows, not controlled test conditions. And these are new-to-the-model photos – it has not seen them before.

• Balanced accuracy: 99.5%
• Per-class F1: All seven classes above 99.8%
• Cross-nutrient confusions: Reduced to 0.058%

For comparison, Stage 2 alone on those same 14,182 images had a 93% higher cross-nutrient error rate. The subclassifier resolves 93% of Stage 2's nutrient misclassifications.

What Changes in the API

Nothing in the request or response shape changes. Stage 2 already returns specific nutrient names — potassium_deficiency, magnesium_deficiency, and so on. What changes is how often those names are correct.

The subclassifier runs as a second pass after Stage 2 flags a nutrient condition. If it disagrees with Stage 2's classification, it overrides it. Same field, more accurate value.

To make this concrete: a plant with potassium deficiency might have previously come back as:

{
  "conditions": [
    {
      "condition": "magnesium_deficiency",
      "confidence": 0.78,
      "severity": "moderate"
    }
  ]
}

With the subclassifier in the pipeline, that same image now returns:

{
  "conditions": [
    {
      "condition": "potassium_deficiency",
      "confidence": 0.97,
      "severity": "moderate"
    }
  ]
}

No schema changes required. If your automation is already acting on nutrient condition names, it will automatically benefit from the correction.

What's Not in It Yet

Three nutrient conditions remain handled by Stage 2 only: zinc deficiency, manganese deficiency, and boron deficiency. The reason is simple – not enough quality training data to build a reliable specialist for these yet. Including them with insufficient data would reduce the accuracy of the classes that are in the model.

These will be added when the training data exists to support them.

What's Next

The nutrient subclassifier is the first piece of the reasoning layer – a set of specialist models that run after Stage 2 to provide higher-resolution diagnoses on the conditions that benefit most from it.

The broader vision: a pipeline that doesn't just tell you what's wrong, but narrows it down to the point where the corrective action is unambiguous. Potassium deficiency doesn't leave you wondering whether to add CalMag or check your VPD. It tells you what to add and how much – if the context supports it.

More on that as it ships.

PlantLab is free to try at plantlab.ai. API documentation is available for growers building automation.

Related reading: – Nitrogen Deficiency in Cannabis: A Visual Guide – Detailed identification and treatment for the most common nutrient deficiency – How PlantLab's AI Diagnoses 31 Cannabis Plant Problems in 18 Milliseconds – The full 4-stage pipeline – Why I Built PlantLab – The origin story