mirror of
https://github.com/gesellix/Bose-SoundTouch.git
synced 2026-09-07 15:07:17 +00:00
Tobias GesellchenandClaude Sonnet 5
66eedeefd3
A speaker's own firmware self-reports its group create/rename/teardown to whatever Marge backend it's configured with -- that's the entire reason HandleMargeAddGroup/HandleMargeModifyGroup/HandleMargeDeleteGroup exist, they're only ever called by speakers, never by us. Coordinator cleanup/rename proactively pushing the same update to an external (non-local) Marge target duplicated that self-report against a backend we generally can't authenticate to anyway (real Bose cloud, another instance, ...), for zero benefit. The one part of the external path with a real, distinct purpose -- preflight's read-only check for a dangling stale generation before a new Create -- stays, but its failure (network error, wrong credentials, an unreachable backend) no longer blocks Create. It's a best-effort safety net on top of the coordinator's own physical preflight (capability/zone/reachability checks against the live speakers), not the primary guard, and the live speakers' own state is the authoritative signal either way. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>