QU

Provides syntax and templates for Fibaro QuickApp development in Lua.

Install

mkdir -p .claude/skills/quickapp-types && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10709" && unzip -o skill.zip -d .claude/skills/quickapp-types && rm skill.zip

Installs to .claude/skills/quickapp-types

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.

All Fibaro device types (40+ types: switches, sensors, climate, covers, controllers), plua file headers (--%%name, --%%type, --%%var, --%%u:, --%%debug, etc.), UI element syntax (label, button, slider, switch, select, multi), and minimal starter templates for each device category. USE FOR: creating a new QuickApp, choosing the right device type (e.g. "what type for a temperature sensor?"), defining UI elements, understanding required actions per device type.
462 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Provides syntax for plua file headers
  • Defines UI element syntax for labels, buttons, and sliders
  • Offers starter templates for various device categories
  • Maps Fibaro device types to required actions

How it works

It provides a reference for plua headers and UI element definitions, allowing developers to scaffold QuickApps using predefined templates.

Inputs & outputs

You give it
Device category or UI element type
You get back
Lua code snippet or header configuration

When to use quickapp-types

  • Scaffolding new Fibaro QuickApps
  • Defining device interface headers
  • Creating UI elements like buttons or sliders
  • Determining required actions per device type

About this skill

QuickApp Device Types and Headers

Reference for all plua QuickApp file headers and the complete set of Fibaro device types.

Starter Lua templates are in the templates/ directory — reference them when the user needs a working skeleton for a specific device type.


plua Header Syntax

--%%key:value

Headers are Lua comments processed by plua before execution. All headers must appear before any Lua code.


Device Configuration Headers

--%%name:My QuickApp            -- display name (required)
--%%type:com.fibaro.binarySwitch -- device type (required)
--%%manufacturer:ACME Corp
--%%model:SmartDevice v1.0
--%%description:What this device does
--%%uid:unique-id-string

Variable Headers

--%%var:apiKey="abc123"          -- string value: must be a Lua string literal
--%%var:location="Stockholm"     -- strings need quotes
--%%var:updateInterval=30        -- numbers are Lua literals, no quotes needed

Gotcha: The value is evaluated as a Lua expression. --%%var:X=London evaluates the global London (likely nil). Use --%%var:X="London" for strings.

Interface Headers

--%%interfaces:{"battery","energy"}

Multi-file Headers

--%%file:./lib/utils.lua,utils   -- include external Lua file (path, module name)

To include a plua library file, use --%%file:$fibaro.lib.libraryName,alias (e.g. --%%file:$fibaro.lib.qwikchild,qwikchild)

Development & Debug Headers

--%%debug:true        -- verbose debug logging
--%%desktop:true      -- auto-open QuickApp UI desktop window
--%%offline:true      -- run without HC3 connection
--%%breakonload:true  -- pause in debugger immediately on load
--%%save:state.json   -- persist state across restarts
--%%project:1001      -- associate with HC3 device ID for upload/sync
--%%proxy:true        -- enable proxy mode (sync with real HC3 QA)
--%%qacolor:lightblue -- background color of the QA desktop window

UI Element Headers

Each --%%u: line defines one row. Use {{...},{...}} for multiple elements on the same row.

Label

--%%u:{label="statusLbl",text="Status: Ready"}

Button

--%%u:{button="myBtn",text="Click Me",onReleased="handleClick"}
-- callback: function QuickApp:handleClick(event) end

Switch (toggle)

--%%u:{switch="autoSwitch",text="Auto Mode",value="false",onToggled="handleSwitch"}
-- event.values[1] == true/false (boolean)

Slider

--%%u:{slider="brightSlider",text="Brightness",min="0",max="100",value="50",onChanged="handleSlider"}
-- use tonumber(event.values[1]) to get numeric value

Select (single-choice)

--%%u:{select="modeSelect",text="Mode",value="1",onToggled="handleSelect",
--      options={{type='option',text='Economy',value='1'},{type='option',text='Comfort',value='2'}}}

Multi (multi-select)

--%%u:{multi="tagMulti",text="Tags",values={"1","3"},onToggled="handleMulti",
--      options={{type='option',text='Tag A',value='1'},{type='option',text='Tag B',value='2'}}}

Multiple elements on one row

--%%u:{{button="onBtn",text="On",onReleased="turnOn"},{button="offBtn",text="Off",onReleased="turnOff"}}

Updating dropdowns at runtime

Single-select (select) — use "selectedItem" to set the current selection:

self:updateView("modeSelect", "options", {{type='option',text='Economy',value='1'},{type='option',text='Comfort',value='2'}})
self:updateView("modeSelect", "selectedItem", "1")   -- value string of the selected option

Multi-select (multi) — use "selectedItems" to set selected values, "options" to update the list:

self:updateView("tagMulti", "options", {{type='option',text='Tag A',value='1'},{type='option',text='Tag B',value='2'}})
self:updateView("tagMulti", "selectedItems", {"1","3"})  -- table of selected value strings

Gotcha: Using "values" instead of "selectedItems" (or "selectedItem" for single-select) will silently fail or have no effect on the HC3.

UI event callback pattern

function QuickApp:handleClick(event)
    -- event.deviceId, event.elementName, event.eventType, event.values
    self:debug("clicked:", event.elementName)
end

function QuickApp:handleSlider(event)
    local value = tonumber(event.values[1])
    self:updateView("brightSlider", "value", tostring(value))
end

Device Type Quick Reference

Switches

TypeRequired ActionsValue / Notes
com.fibaro.binarySwitchturnOn, turnOffvalue = boolean
com.fibaro.multilevelSwitchturnOn, turnOff, setValuevalue = 0–99
com.fibaro.colorControllerturnOn, turnOff, setValue, setColorvalue = 0–99, color = "r,g,b,w" string e.g. "200,10,100,255"

Templates: binary-switch.lua · multilevel-switch.lua · color-controller.lua

Binary Sensors

All update value (boolean). No required actions.

TypeTypical use
com.fibaro.binarySensorGeneric open/closed
com.fibaro.doorSensorDoor/window
com.fibaro.windowSensorWindow
com.fibaro.motionSensorPIR motion
com.fibaro.smokeSensorSmoke detector
com.fibaro.fireDetectorFire detector
com.fibaro.floodSensorWater/flood
com.fibaro.waterLeakSensorWater leak
com.fibaro.gasDetectorGas leak
com.fibaro.coDetectorCarbon monoxide
com.fibaro.rainDetectorRain
com.fibaro.heatDetectorHeat detector

Template: binary-sensor.lua

Numeric Sensors

All update value as number or {value=n, unit="C"}. No required actions.

TypeValue format
com.fibaro.temperatureSensor{value=21.5, unit="C"}
com.fibaro.humiditySensornumber 0–100
com.fibaro.lightSensornumber (lux)
com.fibaro.multilevelSensornumber
com.fibaro.energyMeternumber (kWh)
com.fibaro.powerMeternumber (W)
com.fibaro.rainSensornumber (mm/h)
com.fibaro.windSensornumber (m/s)

Template: templates/numeric-sensor.lua

Climate / Thermostat

All thermostat setpoint/temperature values use {value=n, unit="C"} format.

Full thermostat types — handle setThermostatMode, update thermostatMode, supportedThermostatModes, temperature:

TypeExtra ActionsExtra Properties
com.fibaro.thermostatsetThermostatMode, setHeatingThermostatSetpoint, setCoolingThermostatSetpointheatingThermostatSetpoint, coolingThermostatSetpoint
com.fibaro.thermostatHeatsetThermostatMode, setHeatingThermostatSetpointheatingThermostatSetpoint
com.fibaro.thermostatCoolsetThermostatMode, setCoolingThermostatSetpointcoolingThermostatSetpoint
com.fibaro.thermostatHeatCoolsetThermostatMode, setHeatingThermostatSetpoint, setCoolingThermostatSetpointheatingThermostatSetpoint, coolingThermostatSetpoint

Setpoint-only types — no mode, just setpoints + temperature:

TypeRequired Actions
com.fibaro.thermostatSetpointsetHeatingThermostatSetpoint, setCoolingThermostatSetpoint
com.fibaro.thermostatSetpointHeatsetHeatingThermostatSetpoint
com.fibaro.thermostatSetpointCoolsetCoolingThermostatSetpoint
com.fibaro.thermostatSetpointHeatCoolsetHeatingThermostatSetpoint, setCoolingThermostatSetpoint

HVAC System types — same interface as full thermostat counterparts:

TypeActions
com.fibaro.hvacSystemHeatsetThermostatMode, setHeatingThermostatSetpoint
com.fibaro.hvacSystemCoolsetThermostatMode, setCoolingThermostatSetpoint
com.fibaro.hvacSystemHeatCoolsetThermostatMode, setHeatingThermostatSetpoint, setCoolingThermostatSetpoint
com.fibaro.hvacSystemAutosetThermostatMode, setHeatingThermostatSetpoint, setCoolingThermostatSetpoint

Templates: thermostat.lua (full) · thermostat-heat.lua · thermostat-cool.lua · thermostat-heatcool.lua · thermostat-setpoint-heat.lua · thermostat-setpoint-cool.lua · thermostat-setpoint-heatcool.lua

Covers and Controllers

TypeRequired ActionsNotes
com.fibaro.windowCoveringopen, close, stop, setValuevalue = 0–99 (% open)
com.fibaro.deviceController(none — generic)define your own methods
com.fibaro.remoteController(none)call self:emitCentralSceneEvent(keyId, keyAttribute) to emit button events; keyAttribute defaults to "Pressed"
com.fibaro.alarmPartitionarm, disarmarmed = boolean, alarm = boolean

Templates: controller.lua · window-covering.lua · alarm-partition.lua · remote-controller.lua

Special

TypeRequired ActionsProperties
com.fibaro.playerplay, pause, stop, next, prev, setVolume, setMutevolume (0–100), mute (boolean), power (boolean)
com.fibaro.weather(none)Temperature {value=n,unit="C"}, Humidity (number), Wind (number) — note capital property names
com.fibaro.genericDevice(none)No specific interface contract

Templates: player.lua · weather.lua · generic-device.lua

When not to use it

  • Non-Fibaro QuickApp development

Limitations

  • Requires manual implementation of event callbacks
  • Incorrect UI element property usage can cause silent failures

How it compares

This centralizes device-specific syntax and templates, avoiding the need to manually look up Fibaro API requirements.

Compared to similar skills

quickapp-types side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
quickapp-types (this skill)04moNo flagsIntermediate
telegram-bot-builder1066moReviewIntermediate
workflow-orchestration-patterns102moNo flagsAdvanced
bullmq-specialist256moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

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

workflow-orchestration-patterns

wshobson

Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.

10117

bullmq-specialist

davila7

BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.

2595

unity-mcp-orchestrator

CoplayDev

Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.

1795

async-python-patterns

wshobson

Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.

1299

modal

davila7

Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.

587

Search skills

Search the agent skills registry