Multi-controller support (spec §16.3) #13
Labels
No labels
area/ai
area/backend
area/frontend
area/infra
area/scheduler
area/wled
good-first-issue
priority/high
priority/low
priority/medium
type/bug
type/chore
type/ci-cd
type/docs
type/feature
type/qa
v1.0.0
v1.1.0
v1.2.0
v2.0.0
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
rbrooks/Iris-WLED#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Manage more than one WLED controller, each with its own segment configuration, scheme assignments, and push schedule; controllers may share or independently configure schemes.
Design (from spec §16.3)
controller_idFK tosegments,schemes,schedule_log, andsettings.WLEDControllerclass was already abstracted to make this possible without rewriting the integration layer — instantiatecontrollers: dict[str, WLEDController]in place of the singleton.Why it was deferred
The entire v1 data model is single-controller; supporting multiple controllers is a significant schema migration and UI rework. This is the one v2 item that already shaped v1 code (the
WLEDControllerabstraction).Acceptance criteria
controller_idacross the relevant tablesDeferred v2 item carried over from the spec.