Govee OpenAPI (No Scripts)

Control Govee devices using manual curl commands only.

Linux System Requirements

• - Linux shell with bash available.
• INLINECODE2 installed.
• Internet access to https://developer-api.govee.com and https://developer.govee.com.
• Govee account with supported devices linked.
• Optional: jq for pretty-printing JSON responses.

Quick check:

CODEBLOCK0

Required Credential

• - GOVEE_API_KEY (required)

Autonomous Use Guardrails

• - Only read GOVEE_API_KEY from your chosen per-user secrets file.
• Do not read unrelated secret files or system credentials.
• Restrict outbound requests to:

• - Ask before controlling multiple devices or performing bulk changes.

Get a Govee API Key

1. 1. Open https://developer.govee.com/.
2. Sign in with the same Govee account that owns your devices.
3. Go to the API key section in the developer console.
4. Generate/apply for a key and copy it.
5. Keep it private (treat it like a password).

If the portal UI changes, use the same flow: sign in to Govee Developer → find API key management → create key.

Secure Local Storage (Per-User)

Never store API keys in skill files, git, or chat logs.

Create a per-user secrets file (avoid /root unless intentionally running as root):

CODEBLOCK1

Load only this variable into the current shell (no set -a):

CODEBLOCK2

API Base URL

CODEBLOCK3

Discover Devices First

Before controlling lights, list devices and copy your own device + model:

CODEBLOCK4

View Device State

CODEBLOCK5

Control Commands

Turn on

CODEBLOCK6

Turn off

CODEBLOCK7

Brightness (1-100)

CODEBLOCK8

RGB color

CODEBLOCK9

Response Check

Success usually returns:

CODEBLOCK10

If code is not 200, treat it as failure.

Troubleshooting

• - 401 / unauthorized: key missing, expired, or invalid.
• INLINECODE18 / rate limit: slow retries.
• command rejected: model does not support that command (supportCmds).
• empty device list: account has no supported linked devices.

Safety Rules

• - Use placeholders in docs only (<DEVICE>, <MODEL>, <YOUR_API_KEY>).
• Do not include real keys or device IDs in published artifacts.
• Prefer one-device-at-a-time actions over bulk changes.
• Avoid pasting API keys into chat.