From eab5241e6dfc40bae9f6f68f395aac4630a2a5a8 Mon Sep 17 00:00:00 2001 From: Tobias Gesellchen Date: Sat, 27 Jun 2026 19:30:13 +0200 Subject: [PATCH] docs: fix doc links flagged by markdown-link-check (refs #521) - radio-browser.md: correct the relative path to the troubleshooting section (../guides/TROUBLESHOOTING.md#..., not ../../guides/.../). - TROUBLESHOOTING.md: drop a same-page fragment link to the emoji "Getting More Help" heading (github-slugger anchor was unstable); reference the section in prose instead. Co-Authored-By: Claude Opus 4.8 --- docs/content/docs/guides/TROUBLESHOOTING.md | 2 +- docs/content/docs/reference/radio-browser.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/docs/guides/TROUBLESHOOTING.md b/docs/content/docs/guides/TROUBLESHOOTING.md index 9fab706..b2dcb5d 100644 --- a/docs/content/docs/guides/TROUBLESHOOTING.md +++ b/docs/content/docs/guides/TROUBLESHOOTING.md @@ -477,7 +477,7 @@ If `soundtouch-cli source content --source TUNEIN ...` returns `1005` on a reset **Cause:** -Not fully understood. After an in-place migration the firmware does not activate the radio source **types** in its runtime, even though the entries exist in the speaker's persisted `Sources.xml`. This is firmware behaviour and we have not confirmed the exact trigger. (If you hit this, an [encrypted diagnostic report](#getting-more-help) taken **before** you reset the speaker is very helpful — it now includes the speaker's on-device `Sources.xml`.) +Not fully understood. After an in-place migration the firmware does not activate the radio source **types** in its runtime, even though the entries exist in the speaker's persisted `Sources.xml`. This is firmware behaviour and we have not confirmed the exact trigger. (If you hit this, an encrypted diagnostic report taken **before** you reset the speaker is very helpful, and now includes the speaker's on-device `Sources.xml`. See the "Getting More Help" section below.) **Workaround (confirmed by users):** diff --git a/docs/content/docs/reference/radio-browser.md b/docs/content/docs/reference/radio-browser.md index 730785f..ea0338f 100644 --- a/docs/content/docs/reference/radio-browser.md +++ b/docs/content/docs/reference/radio-browser.md @@ -43,7 +43,7 @@ curl -v -X POST http://:8090/notification \ Replace `` with your speaker's IP address and `` with its device ID (visible in `/info`). After this call the speaker re-fetches its sources from the service. Step 2 (source-type registration) still requires a reboot. -> **If a reboot doesn't help after an in-place migration:** on some speakers the radio source types (`LOCAL_INTERNET_RADIO`, `TUNEIN`, `RADIO_BROWSER`) never activate after an in-place migration, even though the entries are present in the device-local `Sources.xml` and you have rebooted and sent `sourcesUpdated`. The cause isn't fully understood; the confirmed remedy is a factory reset + re-migrate. See [Troubleshooting: Radio sources never activate after an in-place migration](../../guides/TROUBLESHOOTING/#radio-sources-after-migration). +> **If a reboot doesn't help after an in-place migration:** on some speakers the radio source types (`LOCAL_INTERNET_RADIO`, `TUNEIN`, `RADIO_BROWSER`) never activate after an in-place migration, even though the entries are present in the device-local `Sources.xml` and you have rebooted and sent `sourcesUpdated`. The cause isn't fully understood; the confirmed remedy is a factory reset + re-migrate. See [Troubleshooting: Radio sources never activate after an in-place migration](../guides/TROUBLESHOOTING.md#radio-sources-after-migration). ### Search for stations