[Claude] - Add author and missing description to blueprints headers.

This commit is contained in:
2026-01-22 03:26:10 +03:00
parent 565cde77f6
commit c4a9db9c17
14 changed files with 98 additions and 2 deletions

View File

@@ -10,6 +10,8 @@
# - Debounce timer to prevent false alarms from brief sensor triggers
# - Optional melody and volume selection for alarm devices
# - Automatic alarm turn-off when all sensors clear
#
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:

View File

@@ -21,6 +21,8 @@
# - Time of Day options: ["Night", "Morning", "Afternoon", "Evening"]
# - Scenes: [scene.night, scene.morning, scene.afternoon, scene.evening]
# - When time is "Morning" and control is ON -> scene.morning activates
#
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:

View File

@@ -9,6 +9,8 @@
#
# The result is stored in an input_boolean helper that other automations
# can use to determine if someone is likely home.
#
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:

View File

@@ -34,7 +34,7 @@
# - input_text entity for persistent state storage
# - Target light and/or switch to control
#
# Author: Custom Blueprint
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:

View File

@@ -1,3 +1,24 @@
# =============================================================================
# Refrigerator Express Mode Control Blueprint
# =============================================================================
# This blueprint monitors refrigerator temperature and automatically enables
# express/turbo cooling mode when the temperature drifts too far from target.
#
# How It Works:
# - Monitors the temperature sensor and compares to target temperature
# - If difference exceeds threshold (and door is closed), enables express mode
# - Sends notification when express mode is activated
# - Automatically disables express mode when temperature normalizes
#
# Requirements:
# - Door sensor (binary_sensor) to detect if door is open
# - Temperature sensor reporting current fridge temperature
# - Climate entity with target temperature attribute
# - Switch entity to control express/turbo mode
#
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:
name: "Custom: Refrigerator Express Mode Control"
description: >

View File

@@ -19,6 +19,8 @@
# - Commands: ["/status", "/lights_on", "/lights_off", "/arm"]
# - Answers: ["Status checked", "Lights turned on", "Lights turned off", "Alarm armed"]
# - Each command has its own callback action
#
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:

View File

@@ -20,6 +20,8 @@
# Callback Data Format:
# Each button sends callback data: /<keyboard_id>_<button_index>
# Example: /my_keyboard_0 for first button of keyboard "my_keyboard"
#
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:

View File

@@ -25,6 +25,8 @@
# - States: ["Night", "Morning", "Afternoon", "Evening"]
# - Times: [00:00, 06:00, 12:00, 18:00]
# - At 14:30, the state would be "Afternoon" (last threshold passed)
#
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:

View File

@@ -20,6 +20,8 @@
# The blueprint assumes sensors follow the pattern: sensor.<name>_power
# and the corresponding switch is: switch.<name>
# Example: sensor.coffee_maker_power -> switch.coffee_maker
#
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:

View File

@@ -1,3 +1,17 @@
# =============================================================================
# MQTT Multi-Topic Listener Blueprint (Test)
# =============================================================================
# A simple test blueprint that listens to multiple MQTT topics and creates
# persistent notifications when messages are received on matching topics.
#
# Use Cases:
# - Debugging MQTT message flow
# - Testing topic subscriptions
# - Monitoring specific MQTT topics
#
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:
name: MQTT Multi-Topic Listener
domain: automation

View File

@@ -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:

View File

@@ -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: >

View File

@@ -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:

View File

@@ -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: