Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"next track" only works in app - not on web.... #204

Open
larhedse opened this issue Aug 3, 2023 · 0 comments
Open

"next track" only works in app - not on web.... #204

larhedse opened this issue Aug 3, 2023 · 0 comments

Comments

@larhedse
Copy link

larhedse commented Aug 3, 2023

So I know I am new to this (HA and Spotify), however this one I guess is a bit odd I have to say:

Running all the latest upgrades:
Home Assistant 2023.8.0 Supervisor 2023.07.1 Operating System 10.4 Frontend-version: 20230802.0 - latest

Now, I am running a multiple Spotify account setup (1 primary, 3 additional). What I am talking about here is "next track" on a spotify playlist. If I choose to press "next track" on the spotify-card on my Samsung Android tablet with the Home Assistant app installed this works like a charm. However if I open, on my laptop by the way (win10+firefox latest) this does NOT work. And the very strange thing is, even though the account is set in the YAML code for the lovelace spotify-card, that I get something I did not expect:

"Entity media_player.spotify_marhedse does not support this service."

Now, spotify_marhedse is my wifes spotify account in configure.yaml is "merhedse" - and then that is defined as expected as "Spotify Marianne" (which is spotify_marhedse). All fine there.

We basicly have two physical media players: vardagsrum and sovrum - they have there own accounts by the way. And in the yaml code for each spotify_card I have set the account to vardagsrum and sovrum as I expect that to kind of work. And it does that from the android app as mentioned.

Anyway, the web version on Home Assistant gives error when I click "next track". And why my wifes spotify account / media player is the one choosed from all 4 spotify accounts is a good one... Well she is the first account in the list after the primary of course (primary, marhedse, sovrum, vardagsrum) - but it could not be that simple? could it? and why only when I try "next track" (well I have not tested previous track yet) form the web GUI and well it works in the app...

I simply fail to understand what I am doing wrong here, well maybe except the way all 4 accounts are setup in configure.yaml:

spotcast: sp_dc: sp_key: country: SE accounts: marhedse: sp_dc: sp_key: sovrum: sp_dc: sp_key: vardagsrum: sp_dc: sp_key:

Some more from the log, if it helps:

2023-08-03 18:58:59.210 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547477040576] Entity media_player.spotify_marhedse does not support this service. Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 226, in handle_call_service await hass.services.async_call( File "/usr/src/homeassistant/homeassistant/core.py", line 1974, in async_call response_data = await coro ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2011, in _execute_service return await target(service_call) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 235, in handle_service return await service.entity_service_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 851, in entity_service_call raise HomeAssistantError( homeassistant.exceptions.HomeAssistantError: Entity media_player.spotify_marhedse does not support this service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant