mirror of
https://github.com/gesellix/Bose-SoundTouch.git
synced 2026-09-07 15:07:17 +00:00
A rejected or unrecognised command response aborted the sequence with "read back and reconcile all four URL fields before rebooting", leaving the user to do by hand what the service can do in one read-only command. That advice also assumes the write failed, which the reply shape does not prove. A telnet console is a shared stream and firmware echoes vary: an interleaved log line, a normalised URL, or a banner arriving late all produce a response the parser does not recognise, for a write that landed. This is the same class as the earlier parser reporting HTTP 500 when all four writes had succeeded, just narrower. The abort itself is kept, so no further write is sent and a rejected sequence cannot spread. Before returning, `getpdo CurrentSystemConfiguration` now runs and the reported error carries what the device actually holds. Nothing is claimed to have succeeded on ambiguous evidence; the user simply gets the evidence. The two tests asserting that nothing at all follows a rejection now assert the property that matters, that no further command CHANGES the device, since a read-only read-back does not. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>