Restructure repository: organize blueprints into folders

Each blueprint now has its own folder containing:
- blueprint.yaml: The automation code with a short header
- README.md: Detailed documentation extracted from headers

Updated CLAUDE.md with repository structure guidelines.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
2026-02-01 02:38:52 +03:00
parent 26019b1c0c
commit 7b00899903
38 changed files with 843 additions and 615 deletions

View File

@@ -0,0 +1,22 @@
# 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
1. Receives MQTT messages with action IDs from Zigbee buttons
2. Maps action ID to corresponding entity by index position
3. Toggles the matched entity (light/switch/input_boolean)
4. Optionally blinks light if it's already on (idle timeout feature)
## Author
Alexei Dolgolyov (dolgolyov.alexei@gmail.com)

View File

@@ -1,24 +1,8 @@
# =============================================================================
# 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)
# Controls lights and switches using Zigbee2MQTT button devices.
# See README.md for detailed documentation.
#
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:
name: "Custom: MQTT Button Control"

View File

@@ -0,0 +1,21 @@
# 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
1. Listens for MQTT messages on configured topics
2. Extracts the `action` field from the JSON payload
3. Matches action against configured action IDs
4. Executes the corresponding callback action sequence
## Author
Alexei Dolgolyov (dolgolyov.alexei@gmail.com)

View File

@@ -1,23 +1,8 @@
# =============================================================================
# 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
# Triggers custom actions based on MQTT messages with up to 8 action callbacks.
# See README.md for detailed documentation.
#
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:
name: "Custom: MQTT Generic Control"

View File

@@ -0,0 +1,22 @@
# MQTT Light Control Blueprint
Provides extended light control functionality via MQTT devices (typically Zigbee controllers through zigbee2mqtt).
## Features
- Control multiple lights via MQTT topics
- Sequential and "all at once" turn on/off actions
- Brightness control (increment, hold, list-based, min/max)
- Color temperature control (increment, hold, list-based)
- RGB/Hue control (increment, hold, list-based)
- Preset list support (JSON format) for quick scene switching
- Scene activation support (up to 4 scenes)
- Light group and area targeting
- Configurable transition duration for smooth changes
- Alternative light support (control secondary lights when primary are off)
- Persistent state storage via input_text entity
- Custom action callbacks for extending functionality
## Author
Alexei Dolgolyov (dolgolyov.alexei@gmail.com)

View File

@@ -1,25 +1,8 @@
# =============================================================================
# MQTT Light Control Blueprint for Home Assistant
# =============================================================================
# This blueprint provides extended light control functionality via MQTT devices
# (typically Zigbee controllers through zigbee2mqtt).
#
# Features:
# - Control multiple lights via MQTT topics
# - Sequential and "all at once" turn on/off actions
# - Brightness control (increment, hold, list-based, min/max)
# - Color temperature control (increment, hold, list-based)
# - RGB/Hue control (increment, hold, list-based)
# - Preset list support (JSON format) for quick scene switching
# - Scene activation support (up to 4 scenes)
# - Light group and area targeting
# - Configurable transition duration for smooth changes
# - Alternative light support (control secondary lights when primary are off)
# - Persistent state storage via input_text entity
# - Custom action callbacks for extending functionality
# MQTT Light Control Blueprint
# Extended light control via MQTT devices with brightness, color temp, and RGB support.
# See README.md for detailed documentation.
#
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:
name: "Custom: MQTT Light Control"

View File

@@ -0,0 +1,22 @@
# MQTT Light Selector Blueprint
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.
## Features
- Navigate lights with up/down actions
- Remind action flashes the currently selected light
- Visual feedback via configurable flash pattern
- Persists selection in an input_text helper
- Optional state persistence across restarts (JSON storage)
- Optional "remind on idle" - up/down acts as remind if idle too long
## How It Works
1. Press up/down to cycle through the light list
2. Selected light flashes N times to confirm selection
3. Light returns to its original on/off state after flashing
## Author
Alexei Dolgolyov (dolgolyov.alexei@gmail.com)

View File

@@ -1,12 +1,8 @@
# =============================================================================
# MQTT Light Selector Blueprint
# =============================================================================
# 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.
# Cycles through lights using MQTT button events with visual feedback.
# See README.md for detailed documentation.
#
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:
name: "MQTT Light Selector"

View File

@@ -0,0 +1,23 @@
# MQTT Knob Media Controller Blueprint
Controls a media player using an MQTT-connected rotary encoder/knob.
## Features
- Play/Pause toggle (button press)
- Volume up/down (rotation)
- Mute toggle (optional)
- Next/Previous track (optional)
## Volume Step Behavior
- If your device sends `action_step_size` in the MQTT payload, it will be used
- Otherwise, the configured default step size is applied
## Configuration
Action IDs can be customized to match your specific MQTT device.
## Author
Alexei Dolgolyov (dolgolyov.alexei@gmail.com)

View File

@@ -1,11 +1,8 @@
# =============================================================================
# MQTT Knob Media Controller Blueprint
# =============================================================================
# Controls a media player using an MQTT-connected rotary encoder/knob.
# Supports customizable action IDs to work with various MQTT devices.
# See README.md for detailed documentation.
#
# Author: Alexei Dolgolyov (dolgolyov.alexei@gmail.com)
# =============================================================================
blueprint:
name: "MQTT Knob Media Controller"