Monitoring is a deliberate boundary
Reef Trak’s current Home Assistant integration can display selected aquarium values, equipment states, power readings, recent history, and connectivity information. It cannot remotely switch a heater, pump, feeder, light, doser, smart plug, or other device. That is a deliberate product boundary, not an unfinished control button.
Monitoring receives information. Control sends instructions that can change the physical aquarium. Those directions have different consequences. A delayed temperature value is inconvenient and should be marked stale. A delayed or duplicated command to a heater or dosing pump can create a direct hazard.
A monitoring application can help the keeper notice that something deserves inspection. It should not imply that a generic state or smart plug contains enough context to decide what aquarium equipment ought to do next.
Monitoring and control have different responsibilities.
| Question | Monitoring path | Control path |
|---|---|---|
| Direction | Equipment data flows toward the viewer | Commands flow toward physical equipment |
| Failure effect | Missing, delayed, or stale information | Unexpected physical operation or shutdown |
| Required context | Value, unit, time, availability | Device capability, safe state, interlocks, acknowledgement |
| Current Reef Trak bridge | Supported for selected readings | Not implemented |
A switch does not understand the aquarium
A smart plug can often report on or off, and some models report watts. It does not necessarily know whether the attached device is a return pump, heater, fan, skimmer, feeder, or dosing pump. It may not know which tank it serves, whether a maintenance mode is active, whether another device provides redundancy, or what the safe recovery sequence should be.
Turning a return pump off can stop circulation between the display and sump. Leaving a heater on can overheat the system if its independent control fails. Repeating a feeder or dosing command can add too much food or supplement. Turning equipment back on in the wrong order can overflow a skimmer or change sump level. The electrical command is easy; the aquarium context is the hard part.
Even a correctly designed automation needs to consider network loss, server restarts, stale state, duplicate events, conflicting controllers, manual intervention, and what happens when the target device cannot confirm the result.
Examples of consequences that a generic remote command must account for.
| Equipment | Possible unsafe command | Independent protection that still matters |
|---|---|---|
| Heater | Stuck on or enabled at the wrong time | Internal thermostat, independent limit, correct sizing and placement |
| Return pump | Unexpected stop or restart | Overflow capacity, siphon control, oxygenation plan, manual recovery |
| Dosing pump | Repeated or excessive dose | Volume limits, concentration checks, schedule safeguards |
| Feeder | Repeated feed cycle | Mechanical portion limit and deliberate schedule |
| Skimmer | Restart at an unsafe sump level | Delay, cup capacity, overflow management |
Visibility still provides substantial value
Monitoring can show that temperature is moving, a device has stopped reporting, or power behavior has changed. Recent history can reveal whether the event is brief or persistent. Those signals help a person investigate with more information than a simple push alert.
A monitoring-only design also lets Home Assistant remain the authority for any automations the owner deliberately configured there. Reef Trak does not create a second command surface with different permissions, timing, or assumptions. The aquarium record receives selected information while equipment management stays where it was established.
Monitoring does not remove the need for safeguards
A dashboard should never be the only protection for life-support equipment. Sensors can drift, integrations can stop, power can fail, networks can partition, and notifications can be missed. Use equipment appropriate for aquarium duty, independent limits where needed, safe overflow capacity, battery or generator planning, and regular physical inspection.
Reef Trak reports the information it receives and makes connectivity visible. It does not certify that a device is operating correctly or diagnose a failure from one state. The keeper remains responsible for interpreting the evidence and taking action.
The product philosophy
Reef Trak is an aquarium management application for iOS, Android, and web. Home Assistant monitoring belongs beside the tank’s parameters, dosing, livestock, maintenance, equipment, and notes because it adds evidence about what the system was doing.
Remote equipment control would require a separate safety case, protocol, permission model, acknowledgement design, and failure strategy. The current bridge does not pretend that monitoring automatically satisfies those requirements. It provides visibility without opening that command path.