SoundTouch 10 push issue

[Dishwasha]

SixBack firmware version

0.8.6

ESP32 hardware variant

ESP32-S3 (recommended, PSRAM)

Bose speaker(s) involved

SoundTouch 10, FW 27.0.6.46330.50

What happened?

Seeing the following error when trying to push to any slot on either of 2 devices:
✗
verify hardware /presets reflects the change
hardware did not save after retries (Bose-side issue or name-normalization)

What did you expect to happen?

Verification should pass

Steps to reproduce

No response

Logs / screenshots / diagnostic snapshot

No response

[JeyP91]

Looks like the same issue as #10. Is it?

[tostmann]

Confirmed — same root cause as #10. A speaker that isn't migrated to SixBack yet has no bound TUNEIN source, so the speaker's /select returns 500 UNKNOWN_SOURCE_ERROR and the push aborts, which the WebUI reports as "hardware did not save". Reproduced on both ST10 and ST20 — not model- or chip-specific.

Workaround: migrate the speaker first (Migrate on the speaker card → wait for migrated), then push the presets.

Fixed in v0.8.7 (just released): the push is now refused up front with a clear "migrate this speaker first" message instead of the confusing error. Full details in #10.

Could you confirm the two ST10s were still un-migrated when you pushed?

[Dishwasha]

Both show migrated

[tostmann]

@Dishwasha this is very likely the same root cause as #10: a SoundTouch that's migrated to SixBack but never got an account bound to it (empty margeAccountUUID) registers none of the SixBack sources, so every push fails with /select=500.

v0.8.8 (just released) auto-detects and re-binds this on the periodic status check — no manual step. Could you update (Firmware update → Install, or Force re-install), give it ~1–2 minutes, and try pushing a preset again? Let me know if it works on your two ST10s — happy to dig in further if not.