LED

What	Where
Route module	`os/hal/routes/led.py`
`POST /led/solid` — solid RGB colour	`def set_led_solid(req: LEDSolidRequest)`
`POST /led/paint` — per-pixel colours	`def set_led_paint(req: LEDPaintRequest)`
`POST /led/effect` — named animation (breathing, blink, pulse, rainbow…)	`def start_led_effect(req: LEDEffectRequest)`
`POST /led/status` — status-cue overlay (booting, listening, error)	`def set_led_status(req: LEDStatusRequest)`
`POST /led/off`	`def turn_off_leds(...)`
`POST /led/effect/stop` — stop the running animation, keep last frame	`def stop_led_effect()`
`POST /led/restore` — hand strip back to user's saved state (after a transient overlay)	`def restore_led()`
`GET /led` — current state	`def get_led_state()`
`GET /led/color` — current RGB colour of the whole strip	`def get_led_color()`
Named status → colour/effect table	`STATUS_LED_PRESETS`, `os/hal/presets.py`

Concrete calls, all copy-pasteable:

# 1. Solid colour — cold blue
curl -X POST http://127.0.0.1:5001/led/solid \
  -H 'Content-Type: application/json' \
  -d '{"color": [0, 135, 255]}'

# 2. Per-pixel paint — colour each of the N LEDs individually
#    (useful for progress bars, level meters, tests)
curl -X POST http://127.0.0.1:5001/led/paint \
  -H 'Content-Type: application/json' \
  -d '{"colors": [[255,0,0],[0,255,0],[0,0,255],[255,255,0]]}'

# 3. Named animation with tint + speed
curl -X POST http://127.0.0.1:5001/led/effect \
  -H 'Content-Type: application/json' \
  -d '{"effect": "breathing", "color": [0, 255, 0], "speed": 1.0}'

# Other effects: blink, pulse, rainbow, wave, chase, sparkle, …
curl -X POST http://127.0.0.1:5001/led/effect \
  -H 'Content-Type: application/json' \
  -d '{"effect": "rainbow", "speed": 0.5}'

# 4. Status overlay — HAL picks the colour/effect from STATUS_LED_PRESETS
#    ("booting", "listening", "wifi_connecting", "hardware", "agent_down", …)
curl -X POST http://127.0.0.1:5001/led/status \
  -H 'Content-Type: application/json' \
  -d '{"state": "listening"}'

# 5. Stop the animation but keep the last frame lit
curl -X POST http://127.0.0.1:5001/led/effect/stop

# 6. Restore the user's saved LED after a transient overlay
curl -X POST http://127.0.0.1:5001/led/restore

# 7. Off
curl -X POST http://127.0.0.1:5001/led/off

# 8. Read current state
curl http://127.0.0.1:5001/led
curl http://127.0.0.1:5001/led/color

Where the LED is actually driven from in this repo (good places to copy patterns from):

Caller	File	What it does
Status-cue overlay service	`os/services/internal/statusled/service.go` — `func (s *Service) Set(state State)`	Priority-stacked overlay: booting / ota / error / connectivity / hal_down / agent_down / hardware / wifi_connecting. Highest priority wins; on `Clear` the strip is restored.
State constants (booting, wifi_connecting, agent_down, …)	`os/services/internal/statusled/service.go`	The exact set of states you can pass to `/led/status`.
Wi-Fi connecting blue-blink	`os/services/internal/device/service.go` — `s.statusLED.Set(statusled.StateWifiConnecting)`	Fires the blue blink while the STA join is happening during setup.
HAL health watchdog	`os/services/internal/healthwatch/service.go`	Sets `StateHALDown` / `StateHardware` when HAL or a driver stops responding.
Agent-runtime health	`os/services/internal/openclaw/service_ws.go`, `internal/claudecode/client.go`, `internal/codex/client.go`, `internal/picoclaw/client.go`, `internal/hermes/health.go`	Every agent runtime sets `StateAgentDown` when its socket drops so the user sees the LED go red without having to check logs.
LLM skill / tool-call bridge (`[HW:/led/…:{...}]`)	`os/services/server/agent/delivery/http/handler_hw.go`	When an OpenClaw / Hermes / Claude Code skill emits e.g. `[HW:/led/solid:{"color":[255,0,0]}]`, this handler forwards it to HAL. This is how any skill turns the LED red without wiring plumbing itself.
Go HAL client (helpers you'd call from an os-server service)	`os/services/lib/hal/client.go` — `StartEffect`, `StopEffect`, `SetLEDStatus`, `RestoreLED`, `GetColor`	Fire-and-forget wrappers around the endpoints above. New Go services should use these instead of hand-rolling HTTP.

Full LED preset catalogue and rendering rules (colours, priorities, per-preset behaviour) live in the autonomous-os repo docs.