[Claude] - Add author and missing description to blueprints headers.
This commit is contained in:
@@ -1,6 +1,28 @@
|
||||
# =============================================================================
|
||||
# MQTT Button Control Blueprint
|
||||
# =============================================================================
|
||||
# Controls lights and switches using Zigbee2MQTT button devices with multiple
|
||||
# action mappings.
|
||||
#
|
||||
# Features:
|
||||
# - Map multiple action IDs to different lights/switches
|
||||
# - Supports light, switch, and input_boolean entities
|
||||
# - Visual feedback via blink indication when pressing already-active light
|
||||
# - Tracks last interacted entity in an input_text helper
|
||||
# - Supports multiple MQTT topics (multiple buttons)
|
||||
#
|
||||
# How It Works:
|
||||
# - Receives MQTT messages with action IDs from Zigbee buttons
|
||||
# - Maps action ID to corresponding entity by index position
|
||||
# - Toggles the matched entity (light/switch/input_boolean)
|
||||
# - Optionally blinks light if it's already on (idle timeout feature)
|
||||
#
|
||||
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
|
||||
# =============================================================================
|
||||
|
||||
blueprint:
|
||||
name: "Custom: MQTT Button Control"
|
||||
description: Control a Zigbee2MQTT device with multiple actions, that allows to toggle lights and switches and store entity identifier of last interructed switch/light.
|
||||
description: Control a Zigbee2MQTT device with multiple actions, that allows to toggle lights and switches and store entity identifier of last interacted switch/light.
|
||||
domain: automation
|
||||
input:
|
||||
|
||||
|
||||
@@ -1,3 +1,24 @@
|
||||
# =============================================================================
|
||||
# MQTT Generic Control Blueprint
|
||||
# =============================================================================
|
||||
# A flexible blueprint that triggers custom actions based on MQTT messages.
|
||||
# Supports up to 8 different action IDs, each with its own callback.
|
||||
#
|
||||
# Features:
|
||||
# - Listen to up to 4 MQTT topics simultaneously
|
||||
# - Map up to 8 action IDs to custom callback actions
|
||||
# - Works with any Zigbee2MQTT device that sends action payloads
|
||||
# - Fully customizable actions for each trigger
|
||||
#
|
||||
# How It Works:
|
||||
# - Listens for MQTT messages on configured topics
|
||||
# - Extracts the `action` field from the JSON payload
|
||||
# - Matches action against configured action IDs
|
||||
# - Executes the corresponding callback action sequence
|
||||
#
|
||||
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
|
||||
# =============================================================================
|
||||
|
||||
blueprint:
|
||||
name: "Custom: MQTT Generic Control"
|
||||
description: >
|
||||
|
||||
@@ -4,6 +4,8 @@
|
||||
# Cycles through a list of lights using MQTT button events (up/down/remind).
|
||||
# The selected light flashes to provide visual feedback, then returns to its
|
||||
# original state. Selection is persisted in an input_text helper.
|
||||
#
|
||||
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
|
||||
# =============================================================================
|
||||
|
||||
blueprint:
|
||||
|
||||
@@ -3,6 +3,8 @@
|
||||
# =============================================================================
|
||||
# Controls a media player using an MQTT-connected rotary encoder/knob.
|
||||
# Supports customizable action IDs to work with various MQTT devices.
|
||||
#
|
||||
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
|
||||
# =============================================================================
|
||||
|
||||
blueprint:
|
||||
|
||||
Reference in New Issue
Block a user