Skip to content
This repository has been archived by the owner on Jul 4, 2020. It is now read-only.

502 error when transferring user playback #1575

Open
nigel opened this issue May 6, 2020 · 1 comment
Open

502 error when transferring user playback #1575

nigel opened this issue May 6, 2020 · 1 comment

Comments

@nigel
Copy link

nigel commented May 6, 2020

Issue found on May 6th, 2020. A quick google search found that issue #700 from three years ago had a similar issue.

I'm trying to activate a device remotely that's marked as inactive without having user intervention. #680 recommended to transfer user playback to the inactive device. Is there a better way to do so?

Endpoint(s):

  • PUT /v1/me/player

Scope(s):

  • user-modify-playback-state

Steps to reproduce:

  1. Get list of devices from GET /v1/me/player/devices
  2. Select a device with the following: is_restricted: false and is_active: false
  3. Use that device ID to call PUT /v1/me/player with the json payload:
    {"device_ids":[{device_id}],play:true}

Expected behavior:

The device should become active and I'm able to use web API to control that device.

Actual behavior:

502 Bad Gateway (consistently)

@njm222
Copy link

njm222 commented May 7, 2020

Also receiving the same error on initiating the player

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

No branches or pull requests

2 participants