Openhue Hue CLIP API

Name: Hue CLIP API
Brand: Hue CLIP API
Availability: InStock

✓ Official Vendor SpecIOTHome AutomationapiKey133 EndpointsREST

For Agents

Control Philips Hue lights, scenes, rooms, sensors, and entertainment configurations through the local Hue Bridge CLIP v2 API.

Install Jentic One Beta

Connect the Hue CLIP API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hue CLIP API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Hue CLIP API.

Switch lights on or off and adjust brightness, colour, and colour temperature on individual bulbs or groups

Recall and update scenes to apply preset lighting moods across rooms or zones

Read motion, contact, temperature, and light-level sensor values for automation triggers

GET STARTED

Start building with Hue CLIP API

Explore with Jentic

View OpenAPI Document

The Hue CLIP API v2 is the local REST interface exposed by every Philips Hue Bridge for controlling and observing the connected smart-home devices. It covers lights, scenes, rooms, zones, motion and contact sensors, smart buttons, entertainment configurations, geofencing, behavior scripts, and bridge-level features such as software updates and Matter and HomeKit pairing. Authentication is via the hue-application-key header issued by the bridge, and all calls are made directly to the bridge IP rather than to a cloud endpoint, so the API is local-network-only.

Use Cases

Patterns agents use Hue CLIP API for, with concrete tasks.

★ Voice-Controlled Room Lighting

Build a voice or chat assistant that turns lights on or off, dims them, or recalls a scene by name. The agent looks up the room or zone, finds the grouped_light service, and updates its on, dimming, and color attributes via PUT /clip/v2/resource/grouped_light/{id}. Because the bridge speaks locally, latency is well under a second on the home network.

List rooms, find the one named 'Living Room', then PUT to its grouped_light resource setting on.on=false to turn off all lights in that room.

Automation Triggers from Motion and Contact Sensors

Read the current state of motion, contact, and light-level sensors via GET /clip/v2/resource/motion and related endpoints to drive automation logic such as turning hallway lights on at night when motion is detected. The CLIP v2 event model also exposes /eventstream for pushed updates, complementing polled sensor reads.

Get the motion sensor list, find the one in the hallway, and if its motion.motion_report.motion is true, set the hallway grouped_light on to true at 40 percent brightness.

Entertainment Light Sync for Media

Configure entertainment areas and stream synchronised colour effects to a group of lights for music, gaming, or video. Entertainment configurations are managed under /clip/v2/resource/entertainment_configuration and reference the participating light services. This is the local-bridge surface that lights up sync apps and game integrations.

Create a new entertainment_configuration referencing the four lights in the gaming room and start the configuration so it is ready to receive a UDP stream from a sync application.

AI Agent Smart-Home Control via Jentic

An AI agent can take natural-language commands like 'dim the lights for movie night' and translate them into the right Hue CLIP v2 calls. Through Jentic the hue-application-key is vaulted and the agent works against the bridge IP it is told about, with the operation schema returned for each step rather than parsed from the 133-endpoint spec.

Use Jentic to search for 'recall a hue scene', execute PUT /clip/v2/resource/scene/{id} with recall.action='active' for the 'Relax' scene, and confirm the response status is 200.

Key Endpoints

133 endpoints — the hue clip api v2 is the local rest interface exposed by every philips hue bridge for controlling and observing the connected smart-home devices.

METHOD

PATH

DESCRIPTION

GET

/clip/v2/resource/light

List all lights

PUT

/clip/v2/resource/light/{lightId}

Update a light's on state, brightness, or color

GET

/clip/v2/resource/grouped_light

List grouped lights for rooms and zones

GET

/clip/v2/resource/scene

List saved scenes

GET

/clip/v2/resource/room

List rooms

GET

/clip/v2/resource/motion

List motion sensors and their state

GET

/clip/v2/resource/entertainment_configuration

List entertainment configurations

GET

/clip/v2/resource/light

List all lights

PUT

/clip/v2/resource/light/{lightId}

Update a light's on state, brightness, or color

GET

/clip/v2/resource/grouped_light

List grouped lights for rooms and zones

GET

/clip/v2/resource/scene

List saved scenes

GET

/clip/v2/resource/room

List rooms

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The hue-application-key is stored in the MAXsystem vault per bridge. Jentic injects the header at request time so the key never appears in agent prompts or logs, which matters for shared homes and multi-tenant setups.

Intent-based discovery

Rather than parsing 133 endpoints, the agent searches Jentic with intents like 'turn off lights in a room' or 'activate a scene' and gets the exact CLIP v2 operation with its schema.

Time to first call

Direct integration: 1-3 days to handle local network discovery, application-key pairing, and the full 133-endpoint surface. Through Jentic: under 1 hour for the common control intents.

FAQs

Specific to using Hue CLIP API through Jentic.

What authentication does the Hue CLIP API use?

API key authentication via the hue-application-key header, issued by the bridge after a physical button press during pairing. Through Jentic the key is stored in the MAXsystem vault and added to each request automatically.

Can I control individual lights and scenes with the Hue CLIP API?

Yes. PUT /clip/v2/resource/light/{lightId} updates a single bulb's on, dimming, color, and color_temperature attributes, and PUT /clip/v2/resource/scene/{id} with recall.action='active' activates a saved scene.

What are the rate limits for the Hue CLIP API?

The bridge enforces a soft cap of around 10 light commands per second to a single light and 1 grouped_light command per second per room or zone. Stay within these limits to avoid dropped commands; entertainment streaming uses a separate UDP channel rather than HTTP.

How do I turn off all lights in a room with the Hue CLIP API through Jentic?

Search Jentic for 'turn off lights in a room', load PUT /clip/v2/resource/grouped_light/{id}, then execute it with on.on=false using the grouped_light id of the target room. Jentic injects the hue-application-key from the vault.

Does the Hue CLIP API run locally or in the cloud?

The CLIP v2 API runs on the Philips Hue Bridge on the local network, addressed by the bridge's IP. There is no cloud round trip, so latency is low but the agent or its proxy must be reachable from the same network as the bridge.

Can the Hue CLIP API drive entertainment light sync?

Yes. Create an entertainment_configuration referencing the participating lights and start it; the bridge then accepts a UDP stream of colour values for low-latency effects. The HTTP API handles configuration, the UDP channel handles the streaming.