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:
22
Zigbee/MQTT Button Control/README.md
Normal file
22
Zigbee/MQTT Button Control/README.md
Normal 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)
|
||||
Reference in New Issue
Block a user