Govee Cloud

cloudby ALYT

What it adds to a house

adds lights, switches, sensors and appliances.

How a person connects it

Method: form. Enter your Govee Developer API key. Devices must already be connected to Wi-Fi and visible on that account. Cloud control needs internet; LAN Control is not required.

Field	Kind	Required
Govee API key (apiKey)	password, secret	yes

What it can look for

Yes: “Find account devices”.

What stops working when it is disconnected

The things it brought stop answering until it is connected again.

The descriptor

Connection fields are served for a program at /connectors/govee_cloud.json.

{
  "source": "built-in",
  "visibility": "public",
  "listed": true,
  "version": "1.0.0",
  "docsUrl": "https://developers.alyt.com/connectors/govee_cloud",
  "kind": "GOVEE_CLOUD",
  "logo": {
    "url": "/integrations/logos/govee.svg",
    "color": "#000000",
    "ratio": 3.76,
    "background": "#FFFFFF",
    "inset": 0.12,
    "scale": 1
  },
  "name": "Govee Cloud",
  "icon": "plug",
  "connectivity": "cloud",
  "brings": [
    "light",
    "switch",
    "sensor",
    "appliance"
  ],
  "connect": {
    "method": "form",
    "fields": [
      {
        "key": "apiKey",
        "label": "Govee API key",
        "kind": "password",
        "secret": true,
        "required": true
      }
    ],
    "help": "Enter your Govee Developer API key. Devices must already be connected to Wi-Fi and visible on that account. Cloud control needs internet; LAN Control is not required."
  },
  "discovery": {
    "verb": "Find account devices"
  },
  "disconnect": {
    "consequence": "{count} {things} stop answering until it is connected again."
  },
  "author": {
    "kind": "alyt",
    "name": "ALYT",
    "url": "https://alyt.com"
  }
}

The guide

Govee Cloud connects one existing Govee account to a selected ALYT home with a Developer API key. It discovers devices already on Wi‑Fi and visible to that account, and it uses the provider’s cloud path, so internet access and a valid key are required. The connector exposes normal ALYT controls and readings only for capabilities the account API declares; it does not provide factory Wi‑Fi enrollment, Bluetooth fallback, or LAN Control setup.

Connect and place devices

In the household app, select the home, then choose Add a device → Connect something new → Govee Cloud. Enter the Govee Developer API key and connect. After that, use Find account devices under Integrations to discover again when needed, then choose a room for each device. The direct Add device menu lists connected brands.

Partners select the customer’s home, start the authorized visit, and use Connectors → Add a connector → Govee Cloud. The same connection uses the common Name and API key fields, and those are the only provider fields on this form. The approved on-site visit is a prerequisite for partner changes on SELF homes. On supported hosted homes, cloud account setup uses the assigned partner authorization and does not require a local network scan. Device configuration happens through the authorized Configure this home workflow. The Devices panel is read-only.

Use one active local or cloud route per physical Govee identity in a home. If a duplicate route is already present, ALYT refuses discovery with a route-selection explanation. Disable the previous device route before changing it. Matter products are added through Matter setup, and should not be added twice.

What the connector exposes

This connector discovers every device model the account API returns, without a per-model allowlist. It maps declared device families such as lights, plugs, fans, heaters, humidifiers, sensors, and other documented types into normal ALYT descriptors. The exposed controls are based on declared capabilities: power, scalar ranges, choices, colour, colour temperature, and read-only properties where available.

The connector does not guess controls for unknown or future types. Compound segments, music, work modes, and structured temperature programs are listed as unavailable unless a faithful adapter exists. Sensor units are not invented. Missing, invalid, or empty values remain unknown.

Some model-specific limits are preserved exactly as reported. For example, the H6182 cloud model advertises colour temperature in Kelvin, and brightness is normalized into percentage for screens and routines. Native byte 254/255 formats are converted consistently in reads, descriptors, and command encoding, and percentage 101 rounding becomes 100. The server keeps the declared native evidence internally, so a low raw value is not inferred from a single sample.

Brightness accepts device rounding of at most one percentage point. The connector still returns the real reported percentage, not the requested value. Other fields must match exactly. A successful provider acknowledgement is not treated as completion unless the separate cloud readback confirms every requested field.

If the separate state feed lags an already received ACK, the connector may perform up to five additional read-only checks after 1000, 2000, 3000, 3000, and 3000 ms, while time and quota remain, within the original 14-second operation budget and the caller’s expiry, whichever expires first. Requested-field normalization applies only to confirmation, ordinary state reads continue normalizing all fields, and no physical command is repeated.

Routines and control behavior

Govee Cloud steps use the existing saved routine, hub scheduler, and cloud-action relay. Independent local steps stay on the Hub. The current routine version, grants, deadline handling, and durable run/step replay rules still apply. Unavailable cloud steps are reported individually.

A warm-white RGB choice is available when an advertised Kelvin command is not confirmed by a separate read. It approximates the look of white light, but it does not guarantee an exact Kelvin match. Save the same colour and brightness in the required routines, including existing nested routines that share those steps without exceeding the per-routine action limit.

Writes are checked against the device’s declared capabilities before they are sent. If a field is not advertised, ALYT rejects the request. For multi-field writes, every requested field and remaining request capacity are checked first. Conflicting writes, such as mixing colour modes in an incompatible way, are refused. The connector sends each request once and does not automatically retry uncertain physical actions.

Before any RGB effect, the connector also inspects the official legacy inventory. It selects the documented legacy PUT RGB path only when the exact device and model entry is controllable, retrievable, and declares color. A product that is absent from that inventory keeps the primary RGB path for RGB effects. Wrong model data, duplicate or invalid inventory evidence, and unavailable quotas fail before any multi-field writes. There is no SKU allowlist and no fallback after an uncertain write. Non-colour controls remain on the primary path.

Legacy inventory reads use 10/minute/account with burst 10, legacy colour control uses 10/minute/device with burst 10, and the legacy state budget shares the 10000/day/account quota and returned remaining/reset headers. The fixed HTTPS hosts and the 2.5 second legacy read path apply only to the documented legacy calls. The connector uses existing bounded maps for counters; it does not introduce a new cache or queue.

Failure checks

If discovery fails, check that the API key is valid, the device is already on Wi‑Fi, and the product is visible in the Govee account. Internet access is required. If state reads fail, the device may be absent from the current account inventory, busy, or rate limited. A cloud read can also stay deferred, in which case previous evidence is not refreshed.

If control fails, check that the device is still in the account and that the requested capability is actually advertised. Partial failures can leave partial effects. When the provider returns a rate limit response, the account is blocked for at least 60 seconds.

Access and data handling

The API key is sealed and tenant-bound. It is not returned publicly or shown in firmware. Household permissions are narrower than staff permissions. DEV credentials act in the developer sandbox, and LIVE credentials only act on their own installed connector.

The connector supports the normal authenticated integration connect, discover, Thing read and command, and routine APIs. It is cloud-dependent, so if the provider cloud path is unavailable the connector cannot function. The local Govee connection remains separate for LAN-enabled products.

One brand tile covers Govee local and Govee Cloud entries in the searchable inventory, including the deduplicated set of 486 compatible model labels that also includes Matter-only models. That catalogue is a compatibility listing, not a statement that every model or proprietary feature is physically qualified.

Legacy brightness reads use the separate official state API only when needed for correlation. That read path is limited to the documented host, takes up to 2.5 seconds, respects 512 KiB response size, and follows the separate 10/minute/device and 10000/day/account budgets plus returned quota headers. A 429 on that path has its own backoff, and unsupported 400/404 reads are deferred for five minutes. Existing bounded maps are reused, and the connector keeps identity, model, online, and power agreement before trusting the normalized percentage.

After an accepted physical write, transient network/timeout or provider HTTP5xx errors during verification can recover through bounded read-only retries inside the existing 14-second caller deadline, operation budget, quota, and read-count limits; the caller deadline and operation budget are separate bounds, and whichever expires first ends verification. This never retries the physical write; 429/rate budget, 401/auth errors, invalid JSON/schema, or unrelated identity mismatches abort verification, and persistent outage remains unconfirmed when the budget ends.