The short answer
Node ONE is a small, dedicated appliance that lives at home beside your aquarium. It connects to your network, gathers monitoring data from supported reef controllers and smart equipment, and organizes that information in one reef-specific dashboard. Selected readings can also appear in Reef Trak, so the same tank story is available on your phone when you are away from the display.
In practical terms, Node ONE combines a reef aquarium monitoring hub, a Neptune Apex companion dashboard, a reef-specific Home Assistant appliance, and a bridge to Reef Trak in one dedicated device. It is being designed for reef keepers who want connected equipment without turning the aquarium into another do-it-yourself server project.
The point is not that nobody else can build a computer running Home Assistant. Plenty of technical reef keepers can. The point is that most reef keepers do not want to become the installer, integrator, dashboard designer, update manager, and support department for another home server. Node ONE is intended to turn that collection of technical parts into an appliance experience.
The approved promise is simple: You set it up. We take it from there.
The problem: every part of the reef speaks a different language
A modern reef can contain a controller, automated tester, dosing system, lights, return pump, power-monitoring plugs, leak sensors, temperature probes, cameras, and battery backup. Many of those products are smart, but they are not necessarily smart together. One app shows the controller. Another shows the lights. Another shows power. A web portal shows a test result. A notification arrives from somewhere else.
The result is not one system. It is a collection of islands. The reef keeper has to remember which app owns which device, which account is still signed in, which graph matters, and whether a missing reading means the tank changed or one vendor service stopped responding.
Node ONE is designed to sit above those individual systems for monitoring. Compatible equipment keeps doing its original job. Node ONE provides a local integration layer and translates selected information into a consistent reef view.
What Node ONE is, and what it is not
Node ONE is a local integration hub, a dedicated touchscreen, a browser dashboard for the home network, and a bridge to Reef Trak monitoring. Underneath the Reef Trak experience is a complete Home Assistant installation, because Home Assistant already provides a mature way to represent devices from many manufacturers. Node ONE adds a reef-specific product layer on top so normal use does not begin with a blank server and a pile of community instructions.
Node ONE is not a replacement for a Neptune Apex, CoralVue HYDROS, ReefBeat system, doser, relay box, or probe interface. Those products remain responsible for their own hardware and safety functions. Node ONE is also not a promise that every aquarium product will work. Compatibility will expand device by device and will be claimed only after the path is tested.
The Reef Trak path is monitoring-first. The current product promise does not include remotely switching every connected device from Reef Trak. A technical owner may choose to use native Home Assistant features through the Advanced interface, but that is separate from the supported Reef Trak monitoring experience.
How the information moves
That separation matters. The controller still controls. The smart plug still measures power. Node ONE gathers supported observations and gives them aquarium meaning. Reef Trak carries the selected monitoring story beyond the local screen.
The everyday path is equipment to Node ONE to Reef Trak. Each stage has a different job.
| Stage | What happens |
|---|---|
| 1. Equipment | A supported controller, monitor, plug, sensor, light, pump, or other device reports the information its integration exposes. |
| 2. Local integration | Node ONE receives supported data through local or vendor-specific integrations and keeps the integration engine in the home. |
| 3. Reef dashboard | Node ONE groups readings by tank and equipment role, shows current status, and provides local history where available. |
| 4. Reef Trak | Only selected supported monitoring data is shared with the paired Reef Trak tank so it can appear with the rest of the aquarium record on the phone. |
Example flows
These examples describe the intended monitoring pattern. Exact fields depend on the device and the verified integration.
| Source | Node ONE view | Reef Trak result |
|---|---|---|
| Neptune Apex | Supported telemetry such as temperature, pH, ORP, outlet state, and other exposed readings can be organized around the tank. | Selected readings can appear with the tank record in Reef Trak instead of remaining isolated in a controller screen. |
| Power-monitoring smart plug | Node ONE can show whether supported equipment is drawing its normal power and provide history that makes an outage or unusual pattern easier to recognize. | A reef keeper can check the selected equipment status from the same Reef Trak experience used for parameters, maintenance, and livestock. |
| Leak or environmental sensor | A compatible local sensor can be assigned to the aquarium area instead of remaining an anonymous smart-home entity. | The reading can travel with the tank context, subject to the supported data and sharing choices. |
| Supported light or pump integration | Available state and telemetry can be grouped as reef equipment without replacing the manufacturer controls. | Selected monitoring information can join the tank history while control remains with the original system or native Home Assistant interface. |
Why the box lives beside the reef
A cloud-only dashboard depends on the internet and on every vendor service between the tank and the screen. Node ONE keeps the integration engine at home, close to the equipment it observes. When an integration supports direct local communication, the path can stay on the home network instead of taking a round trip through a manufacturer cloud.
The local touchscreen also gives the aquarium a permanent status display. You do not have to find a phone, unlock it, open an app, choose a tank, and navigate to the right screen just to see whether temperature and return-pump power look normal. Favorites can stay on Home, equipment can be browsed by group, and a reading can open into history when something deserves attention.
At home, the same Node ONE experience is also available through a browser on the local network. The browser has more room for equipment, readings, history, and system status, while the touchscreen remains optimized for quick glances and large taps beside the aquarium.
Node ONE and Reef Trak have different jobs
Node ONE is the appliance in the house. Reef Trak is the reef-management system that travels with you. Reef Trak already combines parameters, livestock, equipment records, maintenance, dosing, expenses, photos, controller imports, reports, and long-term history. Node ONE adds a persistent local equipment view and a path for selected supported device data to join that record.
This is why Node ONE is more than a tiny screen running a generic dashboard. The equipment has to be understood as aquarium equipment. A 42-watt plug is not useful by itself. It becomes useful when the system knows it belongs to the return pump on the display tank, knows where the normal pattern has been, and presents it beside the other life-support information a reef keeper cares about.
Why not just build a Home Assistant box?
You absolutely can. Home Assistant is open, capable, and designed to run on hardware in the home. A technically comfortable owner can choose a computer, install Home Assistant OS or another supported installation type, research integrations, add devices, name entities, build dashboards, configure remote access, manage backups, and troubleshoot every layer. For some people, that project is part of the fun.
If that is you, Node ONE may not be necessary. The product is for the reef keeper who wants the benefit of a local integration platform without beginning with an empty Home Assistant installation. The intended experience is reef-specific onboarding, curated compatibility, understandable device selection, a known software environment, a dedicated display, and Reef Trak presentation.
Node ONE does not hide the underlying computer from an owner who wants it. An Advanced Home Assistant entry point remains available for technical users. The difference is that advanced administration is an option rather than the front door.
Privacy: selected tank data, not the whole house
Home Assistant runs on hardware in the home and favors local communication when a device supports it. Node ONE builds on that local-first model, but the Reef Trak bridge adds a stricter selection boundary: only devices and readings chosen for the aquarium are eligible to leave the home through the bridge.
The design does not call for uploading the complete Home Assistant device registry, local network addresses, Home Assistant credentials, person names, or unrelated household devices. Pairing uses Reef Trak credentials and scoped tokens rather than exposing the Home Assistant administration port directly to the internet.
The owner should always be able to understand which tank is paired, which devices are selected, and how to revoke the connection. Privacy is not a one-time promise hidden in setup. It is part of the device-selection model.
The benefits
- One dedicated reef-specific view for supported equipment from more than one ecosystem
- A permanent touchscreen beside the aquarium for glanceable status
- A larger local browser view on phones, tablets, and computers in the home
- Selected supported monitoring data available through Reef Trak when away from the display
- Equipment organized by tank and role instead of raw smart-home entity names
- Local history and trends that help distinguish a changing reef from a disconnected device
- A guided appliance path for people who do not want to build and maintain a home server
- An Advanced Home Assistant path for owners who do want the underlying platform
- No Reef Trak subscription required for the core local monitoring experience
The tradeoffs and current limits
An integration hub creates value by connecting systems, but it also sits in the middle of them. Honest status matters. Node ONE needs to show when the source device is offline, when the local integration is stale, when Reef Trak sync is paused, and when the last reading is too old to trust. A dashboard that quietly displays yesterday’s number as if it were live is worse than no dashboard.
- Compatibility is not universal and will be published only after each integration is verified
- Some equipment depends on community integrations or manufacturer clouds that can change
- The Reef Trak product path is monitoring-first and does not replace a controller or its independent safeguards
- A network, the Node ONE appliance, the source device, and its integration can each fail and need clear offline states
- A technical DIY owner may already have the skills and hardware to build a similar Home Assistant foundation
- The interface, enclosure details, compatibility list, and release process are still being finalized
Node ONE is moving toward release
Node ONE is a working pre-production prototype, several units have been built, and Reef Research Labs is preparing the device for release. Current development is focused on the final interface, repeatable setup and provisioning, verified compatibility, enclosure details, assembly and quality checks, recovery, updates, packaging, compliance review, shipping, and support.
The prototype has been used with Neptune Apex telemetry and Shelly power monitoring. That is evidence of the integration pattern, not a promise that every model, field, or third-party device is ready. CoralVue HYDROS and other ecosystems will be described as supported only after their exact paths are verified.
Node ONE is not yet commercially available, but it is moving toward release. Pricing and availability will be announced when the product, support process, and release details are ready. Images on this page show the working pre-production direction. The final enclosure finish and interface may change.
Who Node ONE is for
Node ONE is for the reef keeper who has useful equipment but does not want reef status scattered across unrelated apps. It is for the person who wants a local display beside the tank, wants selected information in Reef Trak, and values a guided product over an open-ended server project.
It is also for the technically curious owner who likes Home Assistant but wants an aquarium-specific layer with a known starting point. Advanced access remains available without requiring every household member to understand integrations, entities, dashboards, and network administration.
It is probably not for someone who already has a carefully maintained Home Assistant server, a dashboard they love, a remote-access plan, working backups, and no interest in a Reef Trak-specific appliance. That is not a failure of the product. It is the boundary that makes the value clear.
For everyone else, the promise remains: You set it up. We take it from there.