List all devices with their channels, types, and addresses. Optional filters: room, function, type, name. Use this first to discover device addresses for get_value/set_value.

List available communication interfaces (BidCos-RF, HmIP-RF, VirtualDevices, etc.).

List all rooms with their assigned channel IDs. Use with list_devices to find devices by room.

List all function groups (Heating, Lighting, etc.) with their assigned channel IDs.

List all automation programs. Use execute_program to trigger them.

List all system variables with current values and metadata. Use set_system_variable to modify them.

Get the full channel/datapoint schema for a device type (e.g. 'HmIP-eTRV-2'). Shows all channels, paramsets, datapoint names, types, ranges, and operations. Served from cache (instant). Use list_devices first to find device types.

List direct device links (Direktverknüpfungen) — sender→receiver channel pairings that operate independently of the CCU (e.g. a wall switch directly driving a lamp, or thermostats linked to a FALMOT). Read-only. Optionally filter to links involving a specific device or channel address.

Read a single datapoint value from a device channel. Only address and valueKey are required — interface is auto-resolved. Use list_devices to find addresses, describe_device_type to find valid valueKeys.

Read datapoint values for multiple channels at once via HM Script. Provide either a list of channel addresses, or filter by room or function name.

Read all parameters for a channel: VALUES (runtime state), MASTER (config), or a link paramset — for the latter pass the LINK PARTNER's channel address as paramsetKey (find partners with list_links). Interface is auto-resolved from the address.

Set a single datapoint value on a device channel. Only address, valueKey, and value are required — interface and type are auto-resolved. Returns the previous value for undo. Use describe_device_type to find valid valueKeys and ranges.

Write multiple parameters at once (e.g. thermostat weekly profile). Interface is auto-resolved from address.

Set a system variable value. Type is auto-detected — use list_system_variables to see available variables.

Create a new system variable. Types: 'bool', 'float' (optional min/max/unit), 'enum' (requires values list), 'string'. Use set_system_variable to write it afterwards, list_system_variables to see existing ones.

Delete a system variable by name. Use list_system_variables to see existing names. On a protected target, EVERY call needs confirm:true — the session unlock from other write tools does not apply.

Trigger an automation program on the CCU. NOT idempotent — will not be auto-retried. Use list_programs to find program IDs.

Assign a channel to a room and/or a function group. Identify the channel by address and the room/function by name (use list_rooms / list_functions to see names). At least one of room or function is required.

Remove a channel from a room and/or a function group. Identify the channel by address and the room/function by name (use list_rooms / list_functions to see names). At least one of room or function is required.

Get all active service messages (low battery, unreachable, etc.) with device details and timestamps.

Confirm/dismiss active service messages (e.g. clear a low-battery or unreachable warning). Provide an alarm id (from get_service_messages) to confirm one message, or a channel address to confirm all active messages on that channel. A warning reappears if its condition persists.

Get CCU system information: firmware version, serial number, addresses. Reports the active login user and inferred role (ADMIN/USER) — note that version/serial/address are ADMIN-only on the CCU, so they show "N/A" for a non-admin (USER) login. Also reports the running server's build identification (git branch/commit/tag and build time) under build.

Report radio link quality (RSSI, in dBm) for every device, resolved to device names, plus BidCos interface health (duty cycle, connected state). Covers both transports: BidCos-RF via Interface.rssiInfo, and HmIP-RF via each device's RSSI_DEVICE/RSSI_PEER maintenance datapoints. Use to answer 'why is this sensor flaky?'. Higher (closer to 0) dBm is better; null = no measurement.

Context-aware help. No args: conceptual guide. Tool name (e.g. 'set_value'): tool usage. Device type (e.g. 'HmIP-eTRV-2'): capabilities from cache.

Execute arbitrary HomeMatic Script on the CCU. NOT idempotent — will not be auto-retried. Use for anything the other tools don't cover. On a protected target, EVERY call needs confirm:true — the session unlock from other write tools does not apply.

List all configured CCU targets (profiles) you can switch between with use_ccu — name, host, user, whether protected/read-only, which is active, and login state. Never exposes passwords.

Report which CCU target is currently active — host, user, https, protected/read-only flags, and login state. Use this to confirm WHERE a command will run (especially before a write). No password.

Switch the active CCU target. All subsequent tool calls go to this target until switched again (use the per-call target arg on read tools for a one-off without switching). Returns the new active connection info. Login happens lazily on the first call.