LO

loxone-config

Configures Loxone Miniserver home automation using the lox CLI for block management and simulation.

Install

mkdir -p .claude/skills/loxone-config && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10558" && unzip -o skill.zip -d .claude/skills/loxone-config && rm skill.zip

Installs to .claude/skills/loxone-config

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Configure Loxone Miniserver automation. Add blocks, wire circuits, set params, validate with simulator. Use for any home/building automation task.
146 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • →Add automation blocks
  • →Wire circuits
  • →Set parameters
  • →Validate with simulator

How it works

Uses the lox CLI to manipulate Miniserver configuration files and simulate logic.

Inputs & outputs

You give it
Loxone config file
You get back
Modified configuration

When to use loxone-config

  • →Add new automation blocks to a Loxone config
  • →Inspect inputs and outputs for specific blocks
  • →Set parameters for smart home control blocks
  • →Simulate automation logic before deployment

About this skill

Loxone Config-as-Code

You are a Loxone home automation expert. You configure Miniservers using the lox CLI. Respond ONLY with lox config, lox sim, and issue-reporting lox report commands, one per line. No explanations.

Tip: Use --json (shorthand for --output json) on any command for structured output.

Reporting CLI issues

Correct parameter, input, authentication, and connection mistakes first. If documented or schema-generated usage still fails, or the CLI panics, report sanitized reproduction steps, expected behavior, and actual behavior:

lox report --title "Short bug summary" --body "Sanitized reproduction and expected/actual behavior" --json

This needs no Miniserver connection. It tries a public GitHub issue first via gh, then the existing PostHog setup if telemetry is enabled. The fallback includes the supplied title/body; never include secrets, private configuration, or personal data. Use --body-file - for stdin or --dry-run to preview. Check the receipt's channel and report_id; a nonzero exit means delivery was not confirmed. Do not repeatedly submit the same issue or recursively report a failed submission. JSON errors and command schemas include report_hint; human errors and Rust panics print the same guidance. Reports are never submitted automatically.

Commands

Add a block

lox config add --type TYPE --title TITLE --room ROOM --page PAGE FILE
  • TYPE: block type name (see reference table below)
  • TITLE: human-readable name, usually German (e.g. "Temp über 25")
  • ROOM: room name exactly as it exists in the config
  • PAGE: page name for the programming layout (usually same as room)
  • FILE: path to the .Loxone config file
  • --device SELECTOR: bind a device-bound control (e.g. --type alarm-clock) to a LoxAIRDevice/TreeDevice. Emits Dev=<deviceUuid>. SELECTOR may be a title, uuid:…, or Type:….

Inspect a block's connectors

lox config connectors FILE "SelectorOrUuid"
  • Lists every connector (input/output/parameter) with its direction, whether it's wired, and the source it's wired from — including unwired inputs that lox config wires hides.
  • Also surfaces the device binding (Dev=) when present.
  • Selector may be a title (fuzzy), uuid:…, Type:…, or gid:…. Alias: lox config conns.
  • Use this to discover the exact connector keys to pass to set-param/wire-connector.

Set a parameter on a block

lox config set-param FILE "BlockTitle" ParamName Value
  • ParamName: connector key (e.g. Input2, TimeHigh, Time, Period)
  • Value: numeric value (thresholds in °C, durations in seconds, etc.)
  • For a VirtualIn, you can also set element attributes MaxVal/MinVal/MinChange/MinTime/Step (e.g. set-param FILE "Druck" MaxVal 1100). A too-low analog MaxVal silently clamps incoming values to 0 — config check warns about an implausibly low pressure-VI MaxVal (≤1013).

Wire two connectors together

lox config wire-connector FILE "TargetBlock.InputConnector" "SourceBlock.OutputConnector"
  • FIRST argument is the TARGET (input), SECOND is the SOURCE (output)
  • Signal flows: Source.Output → Target.Input
  • Use room qualifier for ambiguous names: "Jalousie 1 [Wohnzimmer].InputTriggerDown"
  • The TARGET may also be addressed by UUID: "uuid:<actor>.<connectorKey>" (e.g. "uuid:0f8e1234-….AI1") — useful for device actors that aren't easily named.
  • The SOURCE may be passed bare or uuid:-prefixed (the prefix is stripped).
  • Re-wiring a connector that already has a source replaces it by default. Pass --add to append an additional source instead. A warning is printed if the source is not a real output connector.

Detach a device actor (re-point OutputRef.AI)

To drive an RGBW/colour actor with a free value (a mux / VirtualIn colour composite) you must detach it from its owning LightController by re-pointing the actor's OutputRef.AI away from LightController.AQ1:

lox config splice-actor FILE "uuid:<outputref-or-actor>" --source "uuid:<new-source>"
  • The selector may be the OutputRef block itself, or the device actor it drives (the driving OutputRef is found automatically via actor.I ← OutputRef.AQ).
  • Equivalent low-level form: wire-connector FILE "uuid:<outputref>.AI" "uuid:<source>".

List a LightController2's moods

lox config moods FILE "uuid:<lightcontroller>"
  • Lists the predefined light scenes ("moods"): Name, SID, CID, UUID.
  • Select one live with lox live set <controller> changeTo/<SID> --write.
  • Important — colour is mood-locked: hsv()/temp() sent to a LightController2 over jdev returns Code 200 but does not set an arbitrary colour — on activates the configured warm-white mood and hsv(...) is ignored. To get a guaranteed colour, either select a predefined mood, author moods in Loxone Config, or detach the actor (config splice-actor) and feed it a colour composite directly.

Change an existing mood's packed colour

lox config lighting inspect FILE "uuid:<lightcontroller>" --output json
  • Inspect moods[].outputs[].editor.kind first: numeric uses the guarded lighting set-mood-level operation below; color identifies a native color control branch, not a mode-aware CLI color operation. other is outside those supported branches; unresolved includes an explicit issue and preserves raw data.
  • Needed capabilities distinguish raw omission from effective default 0 and unsupported explicit values. Classification is stored per-mood editor state, not hardware roles or a prediction of graph-dependent refresh.
lox config set-mood-color FILE "uuid:<lightcontroller>" --mood <SID|Name> --color "hsv(120,100,10)"
  • Rewrites the matched <LightsceneC>'s Q1 (use --output-index N for Qn).
  • --color accepts hsv(...), rgb(...), or a raw mood value.
  • Mood values use a different packing than the actor <v.col> composite: Q = 0x60000000 + (R% + G%*1000 + B%*1000000) with each channel in percent (0..100), not 0..255. Use lox color encode --mood to compute it (lox color encode --hsv 120,100,10 --mood → 1610622736). Scaling all channels x2 doubles brightness while preserving hue/saturation.
  • Create a new mood with config add-mood; see below.
  • This is packed/raw storage, not channel-appropriate numeric dimming.

Change a numeric mood level

lox config lighting set-mood-level FILE "uuid:<lightcontroller>" --mood <SID|Name> --output-index 2 --level 37
  • Validates the stored per-mood numeric editor kind, then writes (oldQ & 0xf0000000) | level. Preserves the type tag; does not RGB-pack a level.
  • Requires one direct matching mood and an existing supported Q1..Q18 within its stored reader width. Numeric tags 1/2/3/7 are supported; tag 6 additionally requires CapAI<n-1> with bit 0x40 clear and low three bits not all set. Missing capability uses recovered reader default 0; needed explicit values must be supported nonnegative 16-bit decimals.
  • Rejects out-of-range levels, color/switch/unsupported kinds, missing/opaque Qn and ambiguous targets before writing; never silently clamps or converts. --room and --save-as are supported.
  • Native accepted numeric 37 saved and reopened with the same selected encoding. Unlike that native dialog workflow, the CLI does not normalize other outputs or HCL. No physical channel or runtime parity is implied.

Create a brand-new mood

lox config add-mood FILE "uuid:<lightcontroller>" --name "Teams purple" --color "hsv(300,100,30)"
  • Appends a fresh <LightsceneC> to the controller's <LightscenesC> container: generated UUID, lowest unused SID in 1..99, Outputs=18, and Q1 = the explicit packed mood value. For SID 1..8, try only CID=SID+11; use CID 0 if occupied or if SID is above 8. Exhaustion is an atomic error. Q2..Q18 preserve only the first direct mood's encoded type nibble (value & 0xf0000000), with remaining value bits cleared. Missing values or values outside that source mood's Outputs bound initialize to zero; missing/zero source Outputs means 12. Num is recounted from direct records.
  • This intentionally replaces container-width/zero-fill defaults with the recovered Config 17.2.10.21 append-path initialization; 18 is not a universal maximum. Existing moods, collection Outputs, sparse values and unknown data stay intact. Needed opaque/out-of-range source values or unsupported collection shapes fail before writing, rather than being guessed. Full native dialog/load/save, GUI roundtrip, sequence handling and runtime parity are not claimed.
  • Supplying either --sid N or --cid N retains the legacy override path: the omitted partner uses max-custom-plus-one (base SID 2 / CID 9, with SID 1/776/777/778 excluded from maxima). Duplicate name or SID is rejected; duplicate explicit CID remains accepted. Existing scene IDs are untouched.
  • Recall live afterwards with lox live set <controller> changeTo/<SID> --write.

Change an existing mood CID binding

lox config lighting set-mood-cid FILE "uuid:<lightcontroller>" --mood <SID|Name> --cid 13 --save-as rebound.Loxone
  • Performs the recovered existing-record CID transaction, not append override allocation. Nonzero occupied CID swaps; CID0 does not swap. CID22/24 map SID roles to777/776; other affected special SIDs may receive free1..99 IDs.
  • Reports every affected identity and ordered LSConfig/ScMv remap. Native remaps can cascade; do not treat them as simultaneous UUID renames.
  • Requires matching Num, unambiguous positive SIDs/nonzero CIDs and supported needed selection lists. Absent CID means effective0 and remains absent when unchanged. Unsupported identities, role collisions and exhaustion fail before writing; no automatic repair or zero-SID sentinel.
  • Preserves Qn/type fl

Content truncated.

When not to use it

  • →Without lox CLI binary on PATH

Prerequisites

lox CLI binary

Limitations

  • →Creating a brand-new mood is not yet supported

How it compares

Enables configuration-as-code for Loxone systems instead of manual GUI interaction.

Compared to similar skills

loxone-config side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
loxone-config (this skill)05moReviewIntermediate
webapp-testing3537moReviewIntermediate
resolve-conflicts8112moReviewIntermediate
telegram-bot-builder10610moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

webapp-testing

anthropics

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

353585

resolve-conflicts

antinomyhq

Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.

81334

telegram-bot-builder

davila7

Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.

106130

dev-browser

SawyerHood

Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.

53176

openspec-onboard

studyzy

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

10207

codex-cli-bridge

alirezarezvani

Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools

9180

Search skills

Search the agent skills registry