What is a reef controller integration app?
A reef controller integration app brings controller readings into the broader reef record. Controllers are excellent for monitoring and automation, but reef keepers also need historical context around what happened in the tank before, during, and after a reading changed.
Reef Trak treats controller data as one layer of the reef history. Apex Fusion, HYDROS, Alkatronic, Mastertronic, and AquaWiz readings can sit beside manual tests, dosing records, livestock notes, equipment changes, maintenance, photos, ICP results, and reports.
Why controller data belongs in long-term reef history
pH, temperature, salinity, ORP, alkalinity, and other readings are more useful when they are connected to real tank events. A number by itself can show a change. The surrounding history helps explain what may have caused it.
- Changed a dosing schedule
- Added livestock
- Changed lighting
- Cleaned a skimmer
- Adjusted a refugium
- Performed a water change
- Changed salt mix
- Added trace elements
- Changed a return pump or flow pattern
Apex Fusion imports
Reef Trak supports a read-only Apex Fusion workflow where Apex readings can flow into Reef Trak parameter history. Apex remains the equipment control and monitoring layer. Reef Trak organizes the longer reef history around those readings.
HYDROS imports
Reef Trak supports HYDROS imports for readings such as pH, temperature, salinity, and ORP where available. HYDROS continues to handle monitoring and control, while Reef Trak connects those readings to manual care and tank history.
Alkatronic, Mastertronic, and AquaWiz imports
Reef Trak is built around a multi-source controller direction. Alkatronic, Mastertronic, and AquaWiz readings can be recorded as part of the same tank history where supported, instead of forcing every reefer into one controller ecosystem.
Read-only by design
Reef Trak combines controller readings with long-term history, reporting, and analysis. Direct controller imports preserve existing controller programs and settings, while Node One provides confirmed local control for supported switch entities.
Why Reef Trak is different from a controller dashboard
A controller dashboard shows what is happening now. Reef Trak helps show what changed, why it may have changed, and what else was happening in the tank at the same time. Controller data becomes stronger when it is paired with manual testing, dosing logs, livestock history, maintenance records, photos, ICP results, and exports.
Reef Trak FAQ
What reef controllers does Reef Trak support?
Reef Trak supports controller imports from Apex Fusion, HYDROS, Alkatronic, Mastertronic, and AquaWiz where available.
How does control work with Apex or HYDROS?
Direct Apex and HYDROS connections import controller readings. Node One provides confirmed local control for compatible switch entities through its supported local integration paths.
Is Reef Trak read-only?
For controller imports, Reef Trak is presented as read-only. It records and organizes readings without changing controller settings.
Can Reef Trak import Neptune Apex data?
Yes. Reef Trak supports a read-only Apex Fusion workflow for importing controller readings into long-term tank history.
Can Reef Trak import HYDROS data?
Yes. Reef Trak supports HYDROS imports for readings such as pH, temperature, salinity, and ORP where available.
Why use Reef Trak if I already have Apex Fusion?
Apex Fusion is built around controller monitoring and control. Reef Trak is built around full reef history, so Apex readings can be reviewed beside tests, dosing, livestock, maintenance, photos, and reports.
Why use Reef Trak if I already have HYDROS?
HYDROS is built for monitoring and control. Reef Trak adds long-term history across controller readings, manual tests, dosing, livestock, maintenance, photos, and reports.
Can I combine controller data with manual tests?
Yes. That is one of the main reasons to use Reef Trak with a controller.
Can Reef Trak help me understand parameter trends?
Yes. Reef Trak connects imported readings with other tank events so parameter trends have more context.