LIFX Control via OOMOL for Openclaw

Openclaw Skills for LIFX lets you manage lights, scenes, power, colors, and effects through the OOMOL-connected oo CLI without handling raw API tokens.

oomol
v1.0.0
Jul 30, 2026
0
250
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install oo-lifx

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install oo-lifx using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is LIFX Control via OOMOL?

This Openclaw Skills package provides a safe, CLI-driven way to operate LIFX devices through an OOMOL-connected account. Instead of calling the LIFX API directly, it uses the oo connector workflow to inspect each action's live schema, then execute validated read or write operations against your account.

The skill is designed for reliable smart-light automation, with clear separation between read actions and state-changing actions. It supports common LIFX tasks like listing lights and scenes, activating scenes, setting color or brightness, toggling power, validating color strings, and turning effects off, while keeping credentials server-side and out of your hands.

LIFX Control via OOMOL Use Cases

  • Query visible LIFX lights for inventory, status checks, or device selection.
  • List available LIFX scenes before triggering an ambient lighting routine.
  • Activate a saved scene for work, sleep, gaming, or presentation modes.
  • Adjust power, brightness, color, infrared, or transition timing on matching lights.
  • Toggle one or more lights by selector for quick on/off control.
  • Stop active effects and optionally power lights down.
  • Validate a LIFX color string before sending a state-changing request.
  • Recover from setup issues such as missing CLI, expired authentication, or disconnected provider credentials.

How LIFX Control via OOMOL Works

  1. Confirm the user has already installed the oo CLI and connected the LIFX provider in OOMOL.
  2. Inspect the live contract for the target action so you use the authoritative input and output schema.
  3. Build a JSON payload that matches the schema exactly, or omit --data to send an empty object when supported.
  4. Run the connector action through oo connector run "lifx" and capture the returned data and meta.executionId.
  5. Treat read actions as safe to execute directly, but require explicit user confirmation before any [write] action changes device state.
  6. If execution fails, resolve only the matching first-time setup condition: install oo, sign in, reconnect LIFX, or fix billing issues.
  7. Repeat with updated payloads or different selectors to manage additional lights, scenes, or effects.

LIFX Control via OOMOL Setup

  1. Install the oo CLI if it is not already available.
curl -fsSL https://cli.oomol.com/install.sh | bash

On Windows PowerShell:

irm https://cli.oomol.com/install.ps1 | iex
  1. Sign in to your OOMOL account once if authentication is missing.
oo auth login
  1. Connect the LIFX provider in OOMOL if the account is not already linked or the connection expired.
https://console.oomol.com/app-connections?provider=lifx
  1. Verify billing only if you encounter an HTTP 402 or OOMOL_INSUFFICIENT_CREDIT error.
https://console.oomol.com/billing/token-recharge
  1. Before any action, inspect the live schema to avoid payload mismatches.
oo connector schema "lifx" --action "<action_name>"
  1. Run the action with validated JSON data.
oo connector run "lifx" --action "<action_name>" --data '{"selector":"all"}' --json

LIFX Control via OOMOL Data Schema & Taxonomy

The skill organizes work around connector actions, live schemas, and execution metadata rather than local files.

Core data model

Element Purpose Notes
Connector lifx The OOMOL connector used for all operations
Action activate_scene, list_lights, list_scenes, set_state, toggle_power, turn_effects_off, validate_color Must be checked with oo connector schema before use
Payload JSON object passed via --data Can be inline JSON or @path/to/file.json
Result { "data": ..., "meta": { "executionId": "..." } } Execution ID is returned under meta.executionId

Action taxonomy

  • Reads: list_lights, list_scenes, validate_color
  • Writes: activate_scene, set_state
  • State toggles / control: toggle_power, turn_effects_off

Operational metadata

  • metadata.title: LIFX
  • metadata.author: OOMOL
  • metadata.version: 1.0.0
  • metadata.services: lifx
  • allowed-tools: Bash(oo *)

Safety metadata

  • Untagged actions are safe read operations.
  • [write] actions must be confirmed before execution.
  • [destructive] actions require explicit approval before running.

External references

LIFX Control via OOMOL Advanced Features

  • Live schema introspection ensures payloads match the connector contract before execution.
  • OOMOL-managed credentials keep raw LIFX tokens off the client and out of the prompt.
  • Fine-grained safety classification separates reads, writes, and potentially destructive operations.
  • Supports scene orchestration for reusable lighting states across workflows and environments.
  • Selector-based targeting enables control of specific lights or groups without direct API calls.
  • Color validation helps prevent invalid state updates by translating strings into LIFX-ready values.
  • Effect shutdown support can stop animations and optionally power lights off in one step.
  • Openclaw Skills integration makes LIFX management accessible through a standardized CLI automation pattern.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*