Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix Spotify: discoverability polish — surface integration in 'hermes setup', doc HA interop [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#15615•Fetched 2026-04-26 05:26:11
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
teknium1teknium1
Participants
teknium1teknium1
Timeline (top)
labeled ×3

Root Cause

Why now: Low severity because most users run hermes tools eventually. Still a discoverability miss — a new user who would have enjoyed Spotify may never find out it exists unless they go looking.

RAW_BUFFERClick to expand / collapse

Two small tidy-up items identified while rolling out the Spotify integration. Low-priority but straightforward; bundle together or ship separately.

A — hermes setup first-run wizard should list Spotify

Context: hermes setup (the initial guided setup a brand-new user runs) has a tool-category picker. Currently Spotify doesn't appear there — it's only reachable via hermes tools after setup completes. Same gap exists for Home Assistant and RL Training.

Why now: Low severity because most users run hermes tools eventually. Still a discoverability miss — a new user who would have enjoyed Spotify may never find out it exists unless they go looking.

Scope: Whatever pattern the first-run wizard uses for existing opt-in integrations (probably just adding an entry to the setup picker's opt-in list). If this needs new plumbing for 'opt-in integrations in first-run', that's a broader UX project — file a separate issue.

Non-goal: Don't make Spotify default-on in first-run. Stay opt-in.

B — Home Assistant interop docs note

Context: Spotify Connect already exposes HA-controlled speakers (Sonos, Echo, Nest, etc.) as Spotify devices automatically via the spotify_devices tool. The user doesn't need a Hermes-side HA↔Spotify bridge because Spotify itself handles the bridging at the device layer.

What to add: ~5-10 lines in website/docs/user-guide/features/spotify.md (new subsection under 'Using it' or within troubleshooting) explaining:

  • If you have Home Assistant managing speakers that support Spotify Connect, those speakers appear in spotify_devices list automatically
  • Target them by name via spotify.default_device_name (issue #15611) or by passing device_id explicitly
  • No extra config needed — this is Spotify's native behavior, not a Hermes feature

Why it's worth documenting: Users with HA assume they need a Hermes-side integration to route Spotify to HA-managed speakers. They don't, and saying so saves them a configuration rabbit hole.

Acceptance

  • A: Spotify appears in first-run setup picker; toggling it on runs the same wizard that hermes tools does
  • B: Docs page has a clear 'Home Assistant-managed speakers' subsection

Both are docs/UX polish — no core code changes expected beyond the first-run picker registration for A.

extent analysis

TL;DR

Update the hermes setup first-run wizard to include Spotify in the tool-category picker and add documentation for Home Assistant interop with Spotify Connect.

Guidance

  • For issue A, verify that the pattern used for existing opt-in integrations in the first-run wizard can be applied to Spotify by checking the setup picker's opt-in list configuration.
  • For issue B, add a new subsection to the spotify.md documentation page explaining how Home Assistant-managed speakers appear in spotify_devices list automatically and can be targeted by name or device ID.
  • Check the hermes tools behavior for Spotify to ensure it matches the expected behavior when toggled on in the first-run setup picker.
  • Review the documentation for clarity and accuracy to prevent user confusion about the need for a Hermes-side HA-Spotify bridge.

Example

No code snippet is provided as the issue does not imply any specific code changes beyond configuration updates.

Notes

The fixes are low-priority and primarily focused on improving user experience and documentation. No core code changes are expected, making this a relatively straightforward update.

Recommendation

Apply the workaround by updating the first-run wizard and documentation as described, as this will improve user experience and reduce potential support queries without requiring significant code changes.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#SSR setup#ISR setup#authentication setup#request error#file not found

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING