fondberg / spotcast

Home assistant custom component to start Spotify playback on an idle chromecast device as well as control spotify connect devices
Apache License 2.0
683 stars 98 forks source link

device_name empty even after using entity_id #420

Open t-abraham opened 9 months ago

t-abraham commented 9 months ago

Bug Ticket

Describe the bug

The service always looks for device_name even after providing the entity_id. It was working great till yesterday and then after the recent updates of both HA and the spotcast to the latest 3.7.1 something broke. I cant confirm if its HA or spotcast.

Troubleshooting

Make sure to validate all the elements before submitting the ticket (Exception to the steps marked as optional)

Environment

Configuration

# please remove any sensitive information like cookies and token keys
<insert configuration here>

Service Call

If relevant, provide a yaml of the service call or explain the action taken to replicate the issue.

service: spotcast.start
data:
  account: home_assistant
  limit: 20
  force_playback: false
  random_song: true
  repeat: true
  shuffle: true
  offset: 0
  ignore_fully_played: false
  uri: spotify:playlist:7KvP5E4IuBi6ctxgA9goAS
  entity_id: media_player.bathroom_speaker
  start_volume: 5

Logs

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:301
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 8:44:19 PM (7 occurrences)
Last logged: 8:57:44 PM

[139814657054400] Error handling message: device_name is empty (home_assistant_error) Tahasanul Ibrahim from xxx.xxx.xxx.xxx (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0)

Additional context

spotcast

fcusson commented 5 days ago

Hi @t-abraham can you check if you still have the issue with v4.0.0. The schema marks the device_name as an optional field, so that shouldn't be a problem