technicalkiwi/lighting-controller
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Sync pattern shortnames with LED bar firmware

Browse Source 
- Add 'on' and 'off' pattern mappings to match LED bar
- Document that PATTERN_NAMES must match led-bar/src/patterns.py
- Keep backend-specific patterns (sequential_pulse, alternating_phase) separate
- Ensures frontend can use the same pattern names as LED bar expects
This commit is contained in:
Pi User
2025-10-03 21:28:28 +13:00
parent aa9f892454
commit 9c9ca53664
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/control_server.py
View File

@@ -31,7 +31,10 @@ SOUND_CONTROL_HOST = os.getenv("SOUND_CONTROL_HOST", "127.0.0.1")
SOUND_CONTROL_PORT = int(os.getenv("SOUND_CONTROL_PORT", "65433")) SOUND_CONTROL_PORT = int(os.getenv("SOUND_CONTROL_PORT", "65433"))
# Pattern name mapping for shorter JSON payloads # Pattern name mapping for shorter JSON payloads
# These must match the shortnames defined in led-bar/src/patterns.py
PATTERN_NAMES = { PATTERN_NAMES = {
"on": "on",
"off": "o",
"flicker": "f", "flicker": "f",
"fill_range": "fr", "fill_range": "fr",
"n_chase": "nc", "n_chase": "nc",
@@ -40,9 +43,10 @@ PATTERN_NAMES = {
"rainbow": "r", "rainbow": "r",
"specto": "s", "specto": "s",
"radiate": "rd", "radiate": "rd",
"segmented_movement": "sm",
# Backend-specific patterns (not sent to LED bars)
"sequential_pulse": "sp", "sequential_pulse": "sp",
"alternating_phase": "ap", "alternating_phase": "ap",
"segmented_movement": "sm",
} }