mirror of
https://github.com/gesellix/Bose-SoundTouch.git
synced 2026-08-18 08:36:13 +00:00
The migration pre-flight "Reachability check (passive observer)" reported a timed-out no-inbound as a hard failure, so the panel showed "N of M checks failed" and forced a Proceed Anyway. That outcome is usually just timing: the speaker's swUpdate daemon dials out on its own slow schedule and a reboot after Apply validates the fan-out. One reporter wrongly suspected custom service ports were to blame (#471, Leeto001). Introduce a proper non-blocking `warn` status (amber, no fail count) and downgrade the no-inbound case to it, with a message that explains the timing and states it is not a port or config problem and is safe to proceed. The pre-flight summaries now surface a warning count alongside the passed/skipped counts and keep auto-proceeding; genuine probe errors still fail. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>