To control Philips Hue lights from OpenClaw, run `clawhub install openhue`, set HUE_BRIDGE_IP in your OpenClaw config, press the link button on your Hue Bridge to authenticate, and start issuing light commands in OpenClaw chat. Once configured, you can turn lights on and off, change colors, adjust brightness, activate scenes, and control individual bulbs or entire rooms using natural language.
Local-First Philips Hue Control From OpenClaw
Philips Hue is the most widely deployed smart lighting system in the world, and its local API is one of the most capable in the smart home space. The Hue Bridge runs a REST API server on your local network that exposes complete control over every connected bulb, light strip, and fixture — including color, brightness, color temperature, dynamic effects, and scenes. The openhue skill taps directly into this local API, giving OpenClaw complete lighting control without routing commands through any cloud service.
The key differentiator of the openhue skill compared to controlling Hue through Home Assistant is directness. While Home Assistant provides a unified smart home hub that can also control Hue lights, the openhue skill provides a deeper, more granular API surface: access to Hue-specific features like entertainment zones, custom dynamic scenes, and individual light resource IDs. If your smart home is primarily or exclusively Philips Hue, the openhue skill delivers faster response times and richer control options than going through a Home Assistant intermediary.
Because the integration is entirely local, it works even when your internet connection is down. Commands travel from OpenClaw to the Hue Bridge entirely within your home network — Philips' cloud services are never involved. For users who prioritize privacy and reliability, this local-first architecture is a significant advantage over cloud-dependent alternatives.
Integration method
The openhue skill is a native ClawHub skill that connects directly to your Philips Hue Bridge over your local network using the Hue Bridge's local REST API. Authentication uses the Bridge's button-press pairing mechanism — you press the physical link button on the Bridge to authorize OpenClaw, which generates a local API username stored in your OpenClaw config. All communication is local: no cloud account required, no Philips Hue account needed, and no internet dependency for controlling lights.
Prerequisites
- OpenClaw installed and running (see openclaw.ai for installation instructions)
- ClawHub CLI available in your terminal (comes bundled with OpenClaw)
- A Philips Hue Bridge (generation 2 or later — the square hub, not the round first-generation one)
- Hue lights already paired with the Bridge through the Hue app
- Physical access to the Hue Bridge for the link button press during authentication
Step-by-step guide
Install the openhue Skill via ClawHub
Install the openhue Skill via ClawHub
Open your terminal and install the openhue skill. This skill wraps the Hue Bridge local REST API, handling authentication, entity discovery, and command translation so you can control lights with natural language instead of raw API calls. After installation, ClawHub lists the required configuration: HUE_BRIDGE_IP is mandatory, and the skill will generate a HUE_USERNAME (local API key) automatically during the Bridge authentication step in Step 3. You do not need to find or generate the username manually. If you have multiple Hue Bridges on your network, you can configure them by running `clawhub install openhue` multiple times with different profiles, or by adding multiple bridge configurations to the skill's YAML config.
1clawhub install openhuePro tip: Run `clawhub info openhue` after installation to see the full list of configuration options, including support for multiple Hue Bridges and HueLabs entertainment features.
Expected result: Terminal shows: 'openhue@X.X.X installed successfully. Required config: HUE_BRIDGE_IP (HUE_USERNAME will be generated during pairing)'. The skill appears in `clawhub list`.
Find Your Hue Bridge IP Address
Find Your Hue Bridge IP Address
The Hue Bridge IP address (HUE_BRIDGE_IP) is the local network address of your Hue Bridge. There are several ways to find it: **Method 1 — Hue app:** Open the Philips Hue app > Settings > My Hue system > Hue Bridges. Tap your Bridge. The IP address is shown in the Bridge details screen. **Method 2 — Hue discovery portal:** Open a browser and navigate to `https://discovery.meethue.com/`. This Philips-provided service scans for Hue Bridges on your network and returns their IP addresses as JSON. **Method 3 — Router admin panel:** Log in to your home router and look at the list of connected devices. Find the device named 'Philips' or 'HueBridgeV2' and note its IP address. The IP address will be in the format `192.168.X.X` or `10.X.X.X` depending on your router's configuration. Make a note of it — you will configure it in OpenClaw in the next step. For a stable setup, consider assigning a static (reserved) IP address to your Hue Bridge in your router's DHCP settings. This prevents the IP from changing if the router restarts or reassigns leases.
1# Find Hue Bridge IP via discovery endpoint (run in browser or curl)2curl https://discovery.meethue.com/3# Returns: [{"id":"...","internalipaddress":"192.168.1.X"}]Pro tip: The Hue Bridge uses a fixed local port (80 for HTTP). You only need the IP address — do not include a port number in HUE_BRIDGE_IP. The skill appends the correct port and API path automatically.
Expected result: You have your Hue Bridge IP address in the format `192.168.X.X` ready to add to OpenClaw's configuration.
Configure HUE_BRIDGE_IP and Authenticate via Link Button
Configure HUE_BRIDGE_IP and Authenticate via Link Button
Set your Hue Bridge IP address in OpenClaw's configuration, then run the pairing command to authenticate. The Hue Bridge uses a button-press pairing mechanism for security: to generate a local API username, you must physically press the large circular button on the top of the Bridge within 30 seconds of running the pairing command. This proves physical access to the Bridge. First, set the HUE_BRIDGE_IP config value. Then run the pairing command — you have 30 seconds after running it to press the Bridge's link button. Once you press it, the Bridge generates a local API username and the skill stores it in your OpenClaw configuration automatically. You will not need to press the button again unless you reset your OpenClaw config. If you miss the 30-second window, just run the pairing command again.
1# Step 1: Set the Bridge IP2clawhub config set HUE_BRIDGE_IP 192.168.1.X34# Step 2: Run the pairing command (then press the Bridge link button within 30 seconds)5clawhub run openhue pair67# The skill will output:8# "Press the link button on your Hue Bridge now (30 seconds)..."9# "Pairing successful. HUE_USERNAME saved to config."1011# Verify both values are set12clawhub config get HUE_BRIDGE_IP13clawhub config get HUE_USERNAMEPro tip: The physical link button is the large circular button on the top surface of the Hue Bridge. You do not need to hold it — a single press is sufficient. The Bridge's LED will pulse briefly to confirm the pairing request was received.
Expected result: The pairing command succeeds and the terminal shows 'HUE_USERNAME saved to config.' Running `clawhub config get HUE_USERNAME` returns a non-empty string.
Test the Skill with Light Control Commands
Test the Skill with Light Control Commands
With authentication complete, open OpenClaw chat and test the integration. The openhue skill maps natural language descriptions to your Hue lights using the friendly names you assigned in the Hue app. It also understands room and zone groupings as configured in your Hue app. Start with a simple on/off test for a light you can see. The skill will return the light name, its entity ID, and the new state after the command. This confirms the integration is working correctly before you start using more complex commands. For color commands, the skill understands color names (red, blue, warm white, cool white, purple), CSS hex codes (#FF5733), and descriptive terms like 'sunset orange' or 'ocean blue' — it translates these to the Hue color space internally. Brightness can be specified as a percentage (50%), a descriptive level (dim, medium, bright, full), or a 0-254 integer value for precision.
Turn on the living room lights and set them to a warm white at 60% brightness.
Paste this in OpenClaw chat
Pro tip: Ask OpenClaw to 'list all Hue lights and rooms' to see the exact names and groupings from your Hue app. Reference these names in commands for precise control.
Expected result: The living room lights turn on at warm white, 60% brightness. OpenClaw confirms the action with the entity names and new state values.
Advanced: Scenes, Groups, and Dynamic Effects
Advanced: Scenes, Groups, and Dynamic Effects
The openhue skill provides access to the full Hue API surface, including scenes, groups, and Hue Labs formulas. Scenes are multi-light presets saved in the Hue app — activating a scene adjusts multiple lights to their scene-specific colors and brightnesses simultaneously. The skill can list all available scenes, activate them by name, and even create new scenes programmatically. Rooms and zones defined in the Hue app are available as groups. Commands targeting a room name ('bedroom lights') apply to all lights in that room simultaneously. Zones work similarly but can span multiple rooms. For advanced users, the skill also supports Hue dynamic scenes — the animated lighting effects introduced in recent Hue firmware versions. Activate them by describing the effect: 'start the candle flicker effect in the dining room' or 'activate the northern lights dynamic scene in the bedroom'. RapidDev recommends pairing the openhue skill with OpenClaw's scheduling capabilities for automated lighting routines — for example, gradually warming the color temperature each evening starting at sunset, or dimming lights to 20% in children's rooms at bedtime.
Activate the 'Energize' scene in the office and tell me what color temperature and brightness it sets the lights to.
Paste this in OpenClaw chat
1# ~/.openclaw/skills/openhue.yaml — optional advanced configuration2openhue:3 bridge_ip: "" # Leave blank if using HUE_BRIDGE_IP env var4 username: "" # Leave blank — auto-populated during pairing5 # Optional: configure multiple bridges6 bridges:7 main:8 ip: "192.168.1.50"9 username: "" # Auto-populated per bridge during pairing10 studio:11 ip: "192.168.1.51"12 username: ""Pro tip: For multi-Bridge setups, run `clawhub run openhue pair --bridge main` and `clawhub run openhue pair --bridge studio` separately, pressing the link button on each Bridge within the 30-second window for each pairing session.
Expected result: Scene activation, group commands, and dynamic effects all work from OpenClaw chat. The skill confirms each action with entity states and effect names.
Common use cases
Color and Mood Control
Change light colors, set specific color temperatures, and adjust brightness for different activities and times of day. The openhue skill understands both color names and technical parameters like kelvin temperature values and hue/saturation coordinates.
Set the living room lights to a warm amber color at 40% brightness. Then set the office lights to cool daylight white at full brightness.
Copy this prompt to try it in OpenClaw
Scene Activation
Activate any scene saved in the Hue app — including scenes you have created — across specific rooms or zones. Scenes adjust multiple lights simultaneously with a single OpenClaw command.
Activate the 'Concentrate' scene in the office and the 'Relax' scene in the bedroom.
Copy this prompt to try it in OpenClaw
Scheduled and Conditional Lighting
Combine the openhue skill with OpenClaw's workflow capabilities to create time-based or condition-based lighting changes — gradually dim lights in the evening, turn on specific lights when your calendar shows a meeting, or flash lights as a notification.
Turn the hallway lights to red for 3 seconds as a flash notification, then return them to their previous state.
Copy this prompt to try it in OpenClaw
Troubleshooting
clawhub run openhue pair times out — 'link button not pressed in time'
Cause: The 30-second window for pressing the Hue Bridge link button expired before the button was pressed, or the button was not pressed firmly enough.
Solution: Run `clawhub run openhue pair` again and press the large circular button on the top of the Bridge immediately after running the command — do not wait. A single firm press is sufficient. If the button press is not registering, check the Bridge power indicator LEDs are on (the Bridge should show at least one solid LED).
1# Re-run pairing2clawhub run openhue pairOpenClaw returns 'openhue: bridge not found' or connection refused
Cause: HUE_BRIDGE_IP is set to an incorrect IP address, the Bridge is offline, or OpenClaw is on a different network segment from the Bridge.
Solution: Verify the Bridge IP using the Hue app (Settings > My Hue system > Hue Bridges) or by visiting `https://discovery.meethue.com/`. Update HUE_BRIDGE_IP with the correct address. Ensure OpenClaw and the Hue Bridge are on the same local network — the Bridge's local API is not accessible over the internet.
1# Check current IP setting2clawhub config get HUE_BRIDGE_IP34# Re-discover bridge IP5curl https://discovery.meethue.com/67# Update if needed8clawhub config set HUE_BRIDGE_IP 192.168.1.X9clawhub reloadOpenClaw cannot find a light or room by name
Cause: The name used in the OpenClaw command does not match the friendly name assigned in the Hue app. Room and light names are case-sensitive in the Hue API.
Solution: Ask OpenClaw to 'list all Hue lights' or 'list all Hue rooms' to see the exact names from the Hue app. Reference those exact names in commands, or rename devices in the Hue app to something more natural for voice/text commands.
clawhub install openhue fails with '429 Too Many Requests'
Cause: ClawHub's registry is experiencing temporary rate limiting.
Solution: Wait 2-3 minutes and retry. Use `--force` flag if a partial installation is blocking the retry.
1clawhub install openhue --forceBest practices
- Use consistent, descriptive room names in the Hue app that match how you naturally refer to spaces — 'Living Room' is better than 'Group 1' for readable OpenClaw commands.
- Assign a static IP address to your Hue Bridge in your router's DHCP settings to prevent HUE_BRIDGE_IP from becoming stale after router restarts or lease renewals.
- After initial pairing, back up your HUE_USERNAME value from `clawhub config get HUE_USERNAME` — you can restore it to a new OpenClaw config without pressing the Bridge link button again.
- Use scenes for complex multi-light states rather than setting each light individually — scenes are faster to activate and keep lighting configurations consistent.
- For multi-Bridge setups, use the YAML-based multi-bridge configuration rather than duplicating skills — this keeps all Hue bridges accessible from a single OpenClaw skill instance.
- Combine the openhue skill with OpenClaw's event triggers to create condition-based lighting — flash lights as a notification when a workflow completes, or change colors based on external data.
- Keep HUE_USERNAME private — it grants full control over your Hue Bridge and all connected lights. If exposed, regenerate it by running the pair command again (which invalidates the old username).
Alternatives
Home Assistant provides a unified hub for all smart home devices including Hue — use it instead of openhue if you have multiple smart home brands and want a single skill to control everything.
SonosCLI controls Sonos speakers rather than lights — pair it with openhue to control both lighting and audio from OpenClaw in a coordinated smart home experience.
Frequently asked questions
How do I install the openhue skill in OpenClaw?
Run `clawhub install openhue` in your terminal. Then find your Hue Bridge IP address (check the Hue app or visit discovery.meethue.com). Set it with `clawhub config set HUE_BRIDGE_IP 192.168.1.X`, then run `clawhub run openhue pair` and press the link button on your Hue Bridge within 30 seconds. The skill is ready to use immediately after successful pairing.
What is HUE_BRIDGE_IP for the OpenClaw openhue integration?
HUE_BRIDGE_IP is the local network IP address of your Philips Hue Bridge — the square hub device that your Hue bulbs connect to. Find it in the Hue app (Settings > My Hue system > Hue Bridges) or by visiting discovery.meethue.com in a browser. It is in the format `192.168.X.X` and should not include a port number.
How do I configure OpenClaw Philips Hue API key?
The Hue Bridge does not use API keys in the traditional sense — it uses a local username generated during pairing. Run `clawhub run openhue pair` with your HUE_BRIDGE_IP configured, press the Bridge link button within 30 seconds, and the skill generates and stores the HUE_USERNAME credential automatically. You do not need to set this manually.
ClawHub install openhue is not working — what should I do?
Verify the skill name is `openhue` (all lowercase). If the install fails with a network error, wait a few minutes and retry — ClawHub's registry occasionally has brief rate limits. Run `clawhub install openhue --force` to clear any partial installation state before retrying.
Does the openhue skill require a Philips Hue account?
No — the openhue skill communicates directly with your local Hue Bridge via its local API. No Philips cloud account, no internet dependency. You only need physical access to the Bridge for the initial link button press. This local-first approach means the integration works even when your internet connection is down.
Does RapidDev offer help with OpenClaw Hue light configuration?
Yes — RapidDev can assist with configuring the openhue skill for complex setups such as multi-Bridge environments, custom scene management, and integrating Hue control into broader OpenClaw automation workflows. The self-serve setup on this page handles most individual use cases.
Can I control Hue lights in multiple rooms at once from OpenClaw?
Yes — use room and zone names from the Hue app in your commands. You can also issue multi-room commands in a single prompt: 'turn off all lights in the kitchen and bedroom' processes as two separate API calls applied in parallel. The openhue skill supports group commands, scene activation across groups, and all entity types exposed by the Hue Bridge.
Talk to an Expert
Our team has built 600+ apps. Get personalized help with your project.
Book a free consultation