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