Hydros Cloud Sensor Setup Beta
ReefMind integrates Hydros (CoralVue) as a read-only shared tank source. Customers share their tank/controller with reefmind@reefmind.ai; ReefMind verifies delegated access and pulls supported live readings without asking for the customer’s Hydros password.
Customer setup steps
- Open the Hydros/CoralVue app and select the tank/controller to connect.
- Open that tank’s sharing/users area.
- Invite
reefmind@reefmind.aiwith view/read-only access. - In ReefMind, choose Hydros during onboarding, or open Settings → My Tanks → Hydros beta.
- Enter the Hydros account email that owns the shared tank. This is a non-secret lookup key so ReefMind can pick the correct shared controller from
reefmind@reefmind.ai. - Select the matching ReefMind tank and click Verify Hydros Share.
- If multiple Hydros controllers are shared, use the advanced Grant ID / Thing Name fields only when provided by support.
If verification succeeds, Dashboard vitals and history show new readings using source/provenance hydros.
What ReefMind uses
- Delegated Hydros account:
reefmind@reefmind.ai. - Data path: Hydros shared access → ReefMind API → tank readings/history/dashboard/Captain Chris context.
- Storage: customer integrations reference the ReefMind delegated credential. Customer Hydros passwords are never requested or stored.
Read-only boundary: the adapter fetches and normalizes Hydros live status/readings only. There are no Hydros write/control routes.
Sensor mapping behavior
Hydros can return generic channels and output states. ReefMind handles this conservatively:
- Known kinds/codes map to ReefMind parameters such as
temp,ph,orp,salinity,alk,no3, andpo4. - Device-confirmed mappings can override generic channel codes and are marked with
mappingTrust: device_confirmed. - Unknown channels are stored as raw/unmapped and are not alert-eligible until confirmed.
- Original units and raw channel codes remain in reading provenance for audit/debugging.
Troubleshooting
Share not found / no devices visible
Confirm the tank/controller was shared with exactly reefmind@reefmind.ai, then tap Verify Hydros Share again. If more than one controller is shared, support may provide a Grant ID or Thing Name.
401 / 403 Unauthorized
The delegated ReefMind Hydros credential may need refresh, or the share was revoked.
Channel appears raw/unmapped
The Hydros payload did not include a recognized kind/unit. Keep it visible as unknown until a device-confirmed mapping is added.
Operational notes
- Feature flag:
HYDROS_BETA_ENABLED=true. - Delegated credential ref defaults to the production delegated Secret Manager ref (
gcp-secret:reefmind-hydros-token-Y6zmYrn6EMqvhfUOXu5E-hydros-fiji-cube-38-93aef9915797) orHYDROS_DELEGATED_CREDENTIAL_REF. - Scheduled polling uses
POST /api/internal/hydros/poll-duewithX-Internal-Secret. - Fleet polling is sharded by top-level
thirdPartyIntegrationsdocuments, staggered across the hour, capped per shard, lease-protected, and configured with Scheduler retries disabled so ReefMind does not stampede Hydros/CoralVue APIs. - This is cloud/shared-access only. It does not require Pi collector OTA or LAN access.
{
"provider": "hydros",
"enabled": true,
"state": "active",
"delegatedShare": true,
"credentialRef": "gcp-secret:reefmind-hydros-delegated-creds",
"externalDeviceId": "thingName"
}