Aquarino Cloud Sensor Setup Beta

What ReefMind uses

• Endpoint: GET https://cloud.aquarino.com.br/api/integrations/sensors
• Auth: Authorization: Bearer <Aquarino API token>
• Data path: Aquarino Cloud → ReefMind API → tank readings/history/dashboard/Captain Chris context.
• Storage: the token is verified once and stored server-side as a Secret Manager reference. It is not stored in browser JavaScript or collector config.

Read-only boundary: the adapter exposes only fetch/normalize helpers. There are no Aquarino write/control routes.

Customer setup steps

1. Create or choose the ReefMind tank. During onboarding, pick Aquarino, or add it later from Settings → My Tanks.
2. Open Settings → My Tanks → Aquarino beta.
3. Select the tank that should receive the sensor readings.
4. Paste the Aquarino API bearer token and click Link Aquarino.
5. After the linked status appears, click Sync now to pull the first readings immediately.

If the first sync succeeds, Dashboard vitals and history should show the new readings using source/provenance aquarino.

Aquarino Intelligence Pack

For Aquarino owners with a ReefMind Collector Box on the same network, ReefMind can also use read-only Aquarino Local Manager data as Captain Chris context. That makes Aquarino feel less like a raw controller feed and more like an AI-reviewed tank story.

• Controller-aware advice: Captain Chris can reference Aquarino sensor highlights, pH/CO2 context, dosing status, feeder timing, and Powerbar state when those local read-only endpoints are available.
• Dosing confidence checks: ReefMind flags disabled channels, low reservoirs, placeholder timestamps, and enabled channels with no exposed next-run time.
• AI-only, not control: local Aquarino data is used to explain what may be happening in the aquarium. ReefMind does not change outlets, feeders, dosing pumps, schedules, or Aquarino automations.
• Sales positioning: Aquarino runs the aquarium; ReefMind explains what the controller data means and what to watch next.

Collector advantage: this local path can expose richer controller context than cloud sensors alone while keeping the same read-only safety boundary.

Sensor mapping behavior

Aquarino can return generic codes such as sensor1 with type: "unknown". ReefMind handles this conservatively:

• Known types/codes are mapped to ReefMind parameters such as temp, ph, orp, salinity, alk, no3, and po4.
• A vendor-confirmed default sensor map (from Aquarino) maps the standard controller sensor indices for every Aquarino controller, because the firmware does not yet report per-sensor unit/type. Reef-parameter readings (temp, pH, ORP, alkalinity, CO2) are stored as canonical parameters; control/state and user-defined indices stay as raw labels.
• Per-device mappings can still override the default map for a specific controller and are marked with mappingTrust: device_confirmed.
• Sensors with no mapping are still stored and visible as their sensor code. ReefMind does not guess risky chemistry mappings.
• Original units and raw sensor codes remain in reading provenance for audit/debugging.

Troubleshooting

401 Unauthorized

Token is invalid or revoked. Generate a new Aquarino API token and link again.

404 Not Found

The token may not be mapped to a device in Aquarino Cloud.

405 Method Not Allowed

Confirms this endpoint is GET-only. ReefMind does not use POST/PUT/DELETE for Aquarino.

Sensor appears as sensorN

The index is outside the vendor-confirmed default map (for example a user-defined or control/state slot), so ReefMind keeps it visible as its raw sensor code rather than guessing a parameter. Add a per-device mapping to override a specific controller.

Operational notes

• Feature flag: AQUARINO_BETA_ENABLED=true.
• Scheduled polling uses the internal route POST /api/internal/aquarino/poll-due with X-Internal-Secret.
• Fleet polling is sharded by top-level thirdPartyIntegrations documents, staggered across the hour, capped per shard, lease-protected, and configured with Scheduler retries disabled so ReefMind does not stampede Aquarino Cloud APIs.
• This is cloud/API-only. It does not require Pi collector OTA or LAN access.

{
  "provider": "aquarino",
  "enabled": true,
  "state": "active",
  "credentialRef": "gcp-secret:...",
  "externalDeviceId": "deviceUuid"
}