POST API Requests Return 204 Success But Don't Execute Commands on Client Devices #14416
Unanswered
Calmantras
asked this question in
Q&A
Replies: 1 comment
-
|
Ah, I just found your post—I have a similar question in #15857 Did you ever make any progress here? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Trying to get this to work. Can someone please share some insigth on working with the api to control client playback. Sending messages to the client would be also really nice.
Description of the bug
POST requests to Jellyfin's API endpoints for remote control commands (mute/unmute, pause/play/seek, display messages) return HTTP 204 Success responses but do not produce any visible effects on client devices. GET requests work perfectly, indicating network connectivity and authentication are functioning correctly.
Reproduction steps
POST /Sessions/{sessionId}/Command/{command}(for mute/unmute)POST /Sessions/{sessionId}/Playing/{command}(for pause/seek/play)POST /Sessions/{sessionId}/Message(for display messages)What is the current bug behavior?
What is the expected correct behavior?
POST requests should execute the requested commands on the target client devices (mute/unmute audio, pause/play/seek media, display messages on screen).
Jellyfin Server version
10.10.7
Specify version number
10.10.7
Specify the build version
10.10.7
Environment
Jellyfin logs
Client / Browser logs
Tested on multiple client types:
Some clients show
"SupportsRemoteControl": trueand"SupportsMediaControl": truein their session info, others don't.Additional information
Beta Was this translation helpful? Give feedback.
All reactions