This BUG is still present, more than a year after being reported on this forum for the first time.
Issue, cause and workaround have been documented in:
The problem and workaround were acknowledge by a Sonos rep more than 6 months ago. But the problem persists.
Would it be possible for Sonos to actually fix the bug in the next update?