mirror of
https://github.com/gesellix/Bose-SoundTouch.git
synced 2026-09-07 15:07:17 +00:00
Tobias GesellchenandClaude Opus 5
c46bc4898a
Migration was refused whenever the rendered account held more than one device. One account holding every speaker in the household is the normal Bose arrangement, so this blocked most setups, and there was no override: the check runs unconditionally at the top of MigrateSpeaker. It also misfired on genuinely single-speaker setups. handleDiscoveredDeviceFallback writes a second device directory keyed by the host address under the same account whenever /info momentarily fails, and its cleanup only runs when d.SerialNo is set, which discovery never populates. A stale entry left behind by a DHCP lease change then blocked migration permanently. The evidence does not support a hard block either. Issue #614 concluded the shared-account preset wipe is empirical rather than a proven mechanism, with the root cause still open, and the troubleshooting entry added there is labelled a workaround. The guide's own remediation was unreachable in normal use, since discovery re-adds the other devices. The check now reports it as a warning, naming the device count, carried into the migration log the UI already shows alongside its other "Warning:" lines. The provable checks (persisted snapshot present and valid, presets equal across snapshot, live /presets and rendered /full) still refuse. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>