DTFGENETICSDREAM THE FUTURE
Teaching
Healthy Cultivation
Tools›THC Root-Zone Temperature Reference

Root environment

THC Root-Zone Temperature Reference

Record root-zone temperature beside air temperature and irrigation context so root conditions are not inferred from room temperature.

Root-zone check

Why record it

Root-zone temperature can diverge from room temperature because of irrigation temperature, container mass, floor contact, radiation, airflow and evaporative cooling. Trend the root-zone value directly.

Temperature and EC are context, not oxygen measurements. Root-zone temperature can influence gas solubility and root metabolism, but this tool does not infer dissolved oxygen from temperature or EC. Use an appropriate oxygen measurement method when oxygen itself is the question.

Filtered root-zone summary

—Avg root °C
—Avg root-air Δ
—Avg solution-root Δ
—Avg root-feed EC Δ

All saved readings.

Multi-sensor / position comparison

Compares the latest saved reading from each sensor, probe or plant-position identifier for the selected zone and timing. Spatial spread can reveal disagreement or root-zone variability, but it does not prove which sensor or position is correct. Keep probe type, depth, placement and substrate configuration comparable.

—Latest identifiers
—Root temp spread °C
—Root EC spread
—Root-air Δ spread °C
IdentifierTimeRootAirSolutionRoot-air ΔRoot ECRoot-feed EC Δ

Root-zone trend

Charting the three temperatures together helps separate room-driven changes from irrigation-solution or root-zone divergence.

Recent readings

TimeZoneIdentifierTimingRootAirSolutionRoot-feed EC Δ

Connected root-zone provider

Load normalized root-zone temperature, room temperature, solution temperature and EC through the same-origin telemetry gateway when a compatible provider/device is configured. Provider credentials remain on the server. Reads only populate this form; nothing is saved until you use Save reading.

—provider
0mapped metrics
—latest observation
No authenticated provider loaded.
This requires the same-origin telemetry gateway to be deployed with provider credentials stored on the server.