led-control
Control the device's RGB light when the user asks for a SPECIFIC color (e.g. "yellow", "red", "yellow", "red", "turn on color X", "enable X light"), an LED effect, or turning LEDs off. Do NOT use for ambiance/activity lighting (use Scene) or emotion expression (use Emotion).
- License 许可
- MIT
- 最近更新
- 2026-10-08
- Stars
- ★ 11
- Forks
- 3
01 前言 Front Matter
- name
- led-control
- description
- Control the device's RGB light when the user asks for a SPECIFIC color (e.g. "yellow", "red", "yellow", "red", "turn on color X", "enable X light"), an LED effect, or turning LEDs off. Do NOT use for ambiance/activity lighting (use Scene) or emotion expression (use Emotion).
02 资源文件 1
- 参考文档skill.json65 B
03 SKILL.md 正文
LED Control
Quick Start
Control the device's RGB light directly. Use this skill only when the user requests a specific color, effect, or to turn LEDs off.
Workflow
- Determine the user's intent:
- Specific color ->
[HW:/led/effect/stop:{}][HW:/led/solid:{"color":[R,G,B]}] - Two or more colors / mix / gradient ->
[HW:/led/effect/stop:{}][HW:/led/paint:{"colors":[[R,G,B],[R,G,B]],"gradient":true}] - Effect ->
[HW:/led/effect:{"effect":"name","color":[R,G,B],"speed":1.0}] - Turn off ->
[HW:/led/off:{}]
- Specific color ->
- Place markers at start of reply — the device fires them in order before TTS
- Confirm the action to the user
Examples
Input: "Make it purple" / "turn on purple"
Output: [HW:/led/effect/stop:{}][HW:/led/solid:{"color":[100,50,200]}] I've set the LEDs to purple.
Input: "Turn on yellow light" / "set yellow" / "switch to yellow" / "yellow light"
Output: [HW:/led/effect/stop:{}][HW:/led/solid:{"color":[255,220,0]}] Yellow light on!
Input: "Turn on red light" / "set red" / "switch to red" / "red light"
Output: [HW:/led/effect/stop:{}][HW:/led/solid:{"color":[255,0,0]}] Red light on!
Input: "Turn on white light" / "set white" / "white light"
Output: [HW:/led/effect/stop:{}][HW:/led/solid:{"color":[255,255,255]}] White light on!
Input: "Change to cyan purple" / "mix blue and pink" / "gradient from red to orange"
Output: [HW:/led/effect/stop:{}][HW:/led/paint:{"colors":[[0,200,200],[150,0,255]],"gradient":true}] Cyan-to-purple gradient on!
Input: "Do a breathing light with warm color"
Output: [HW:/led/effect:{"effect":"breathing","color":[255,180,100],"speed":0.5}] Breathing effect started with a warm glow.
Input: "Rainbow mode!"
Output: [HW:/led/effect:{"effect":"rainbow","speed":1.0}] Rainbow effect is running!
Input: "Turn off the lights"
Output: [HW:/led/off:{}] LEDs are off.
Input: "I want to relax" / "reading mode" / "goodnight" Output: Do NOT use this skill. Use Scene skill instead.
Input: Conversational reply needing emotion Output: Do NOT use this skill. Use Emotion skill instead.
How to Control LEDs
No exec/curl needed. Use inline markers at start of reply — the device fires them in order:
Solid color (stop effect first)
[HW:/led/effect/stop:{}][HW:/led/solid:{"color":[255,220,0]}] Yellow light on!
Color is an RGB array [R, G, B].
Multi-color / gradient (stop effect first)
[HW:/led/effect/stop:{}][HW:/led/paint:{"colors":[[0,200,200],[150,0,255]],"gradient":true}] Cyan-to-purple gradient!
colors: list of RGB gradient stops (2+ colors), blended smoothly across the whole stripgradient: trueis REQUIRED — without it the colors paint only the first N pixels and the rest of the strip keeps its old color- Works with 3+ stops too:
{"colors":[[255,0,0],[255,220,0],[0,200,80]],"gradient":true}= red -> yellow -> green
Effect
[HW:/led/effect:{"effect":"breathing","color":[255,180,100],"speed":0.5}] Breathing warm glow.
effect(required): effect name from table belowcolor(optional): RGB arrayspeed(optional): 0.1 (slow) to 5.0 (fast), default 1.0duration_ms(optional): auto-stop after N ms
Turn off / stop effect
[HW:/led/off:{}] LEDs off.
[HW:/led/effect/stop:{}]
Available effects
| Effect | Description | Best for |
|---|---|---|
breathing |
Slow fade in/out with given color | Relaxation, idle ambient, meditation |
candle |
Warm flickering like a real candle | Cozy evening, romantic mood |
rainbow |
Hue cycle across all pixels | Fun, party, showing off |
notification_flash |
3 quick flashes then auto-stops | Alerts, timer done, reminders |
pulse |
Radial brightness wave from center | Attention, heartbeat, alive feeling |
Color suggestions
| Color name | Color (RGB) |
|---|---|
| White | [255, 255, 255] |
| Yellow | [255, 220, 0] |
| Warm white | [255, 180, 100] |
| Orange | [255, 100, 0] |
| Red | [255, 0, 0] |
| Green | [0, 200, 80] |
| Blue | [0, 150, 255] |
| Purple | [100, 50, 200] |
| Pink | [255, 80, 150] |
Error Handling
- If the API returns an error or is unreachable, inform the user: "I couldn't control the LEDs right now. The hardware service may be unavailable."
- If the user requests an unknown effect name, pick the closest match from the available effects table or tell the user which effects are available.
Rules
- ALWAYS include the JSON body, even for no-argument commands. Every marker is
[HW:/path:{...}]— for commands that take no arguments the body is the empty object{}. Emit[HW:/led/off:{}]and[HW:/led/effect/stop:{}], NEVER the bodyless[HW:/led/off]or[HW:/led/effect/stop]. A marker without:{...}is malformed and the device silently drops it — the light will NOT turn off. - The marker is NOT a markdown link. Never wrap it as
[some text](HW:/led/off:{})— emit the plain marker[HW:/led/off:{}]followed by your sentence as normal text. - "Turn on color X" / "set light X" / "change color X" = THIS skill. Any request naming a color (yellow, red, green, purple, white, orange, pink…) routes here — NOT to Emotion or Scene. Emotion yellow/happy is for YOUR feelings, not user's lighting request.
- NEVER use
/led-coloror/led/colorfor setting color — these endpoints do NOT exist. Always use[HW:/led/effect/stop:{}][HW:/led/solid:{"color":[R,G,B]}]. - Two or more colors at once =
/led/paintwith"gradient":true./led/solidtakes exactly ONE color — never try to express "cyan purple" as a single blended RGB; paint a gradient instead. - Stop effect before solid. Always call
/led/effect/stopbefore/led/solid. A running effect thread overwrites solid every 40ms — skipping the stop causes the color to flicker and revert. - Solid colors = full brightness. For dim/ambient lighting, use the Scene skill instead.
- Effects run until stopped (unless
duration_msis set). Starting a new effect auto-stops the previous one. /led/offalso stops any running effect.- For "make it cozy" or "candle light" -> use
candleeffect, NOT a static orange color. - For "breathing" or "pulsing" requests -> use the matching effect.
- Combine effects with low speed (0.3-0.5) for calm moods, high speed (2.0-3.0) for energy.
- Do NOT use for activity/ambiance lighting (sleeping, relaxing, reading, focus, movie) -> use Scene skill.
- Do NOT use for expressing emotion -> use Emotion skill.
Output Template
[LED Control] {action} — {details}
Examples:
[LED Control] Solid color set — purple [100, 50, 200][LED Control] Effect started — breathing, warm [255, 180, 100], speed 0.5[LED Control] LEDs off
04 同仓库更多 Skills
obsidian-clipper-template-creator
Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
obsidian-clipper-template-creator
Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
python-api
Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP/mAP semantics, and source-style import diagnostics.
file-evaluation
Folder-based PASCAL VOC AP/mAP evaluation from ground-truth and detection text files.
object-detection-metrics
Guides legacy Object-Detection-Metrics PASCAL VOC AP/mAP evaluation from detection text folders and direct Python API classes.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.