For smart-aquarium manufacturers · preview

Connected Aquariums — Manufacturer Integration Programme

Bring your smart tanks into BioSensei: monitored, explained and — later — safely controlled, through your own official interfaces.

Status: programme in preparation. No manufacturer integration is available yet and no partnership is established. Compatibility will only be announced after an integration has been implemented and tested.

Aquaculture, research installations and other industrial uses of BioSensei are handled by BioSensei Industrial, part of Ajinomatrix BioSphere.

Observe

Temperature and equipment status from your tank, next to the keeper’s own test-kit readings, in one timeline.

Explain

Every tank gets a plain status — Urgent, Attention, Verify, OK, No data — with the evidence, the age of each reading and what to check first.

Act

Later, authorised control of light, feeding and pump through your interface, with confirmations, safety limits and device-confirmed states.

How it connects

  1. Your smart tankMYG, Mijia and other models
  2. Your cloudTuya / Smart Life · Xiaomi Home (MIoT) · your own API
  3. BioSensei gatewayone adapter per platform · owner consent · audited
  4. BioSensei appmonitoring · explainable alerts · history · caretaker hand-over

The tank owner links their own account and can revoke it at any time. BioSensei reads through your official interface first; commands come later, only with the owner’s approval. AI never operates equipment.

Specification mapping bench Stage 1 · available

Paste your device’s data-point specification and see how BioSensei would map each sensor and control. Accepted formats: a Tuya device specification (the functions / status lists from the Tuya IoT Platform) or a Xiaomi MIoT-Spec-V2 instance (services with properties and actions).

Runs entirely in your browser — nothing you paste is uploaded or stored.

What this is not: mapping a specification shows how BioSensei would interpret your data points. It does not test live connectivity with a device — that happens in the authenticated partner portal (stage 2 below).

The examples are illustrative, not real device data. Mapping uses BioSensei’s current naming rules; a code we do not recognise is listed so you can tell us what it means.

Compatibility register

Every model moves through four recorded states. Only the last carries the “Works with BioSensei” mark.

  1. Identifiedmodel known to BioSensei
  2. API verifiedauthorised route and data points confirmed
  3. Integration testedreadings (and later commands) checked on test units
  4. BioSensei compatible“Works with BioSensei”
MakerModelPlatformState
WonderFactorySAM1 / S1 smart aquarium, 5 galSmart Life (Tuya)Identified
WonderFactoryMYG series, smaller vertical tankto confirmIdentified
XiaomiMijia Smart Fish Tank MYG100Xiaomi Home (MIoT)Identified
XiaomiMijia Smart Fish Tank 2 ProXiaomi Home (MIoT)Identified

“Identified” means only that we know the model exists. No model is compatible yet, and no manufacturer has joined the programme.

Integration stages

  1. 1 · Specification mapping — how BioSensei would interpret your published data points. Public, in your browser. Available
  2. 2 · Authenticated connectivity test — BioSensei reaches a test device through the authorised route. Partner portal. Planned
  3. 3 · Read-only telemetry validation — values, units, timestamps and freshness checked on test units. Proposed v0.5.8
  4. 4 · Simulated command validation — commands acknowledged and confirmed in a sandbox, with safety limits. Planned
  5. 5 · Authorised physical control — owner-approved, device-confirmed commands on real test units. Proposed v0.5.9
  6. 6 · Compatibility certification — “Works with BioSensei” for models that pass, recorded in the register above. Planned

Partner access

This public page only explains the programme and demonstrates stage 1. Everything partner-specific — credentials, device configurations, test devices, logs and integration results — lives in the authenticated partner portal, behind per-partner sign-in and permissions, and is never published here.

Request an introduction