Activate what? You said you got it installed but it won’t play. I’m asking for logs that would hopefully show the reason why it doesn’t play.
This is the error:
error: [ytmusic] Innertube support service: PayloadTooLargeError: request entity too large
at readStream (file:///data/plugins/music_service/ytmusic/node_modules/raw-body/index.js:163:17)
at getRawBody (file:///data/plugins/music_service/ytmusic/node_modules/raw-body/index.js:116:12)
at read (file:///data/plugins/music_service/ytmusic/node_modules/body-parser/lib/read.js:113:3)
at jsonParser (file:///data/plugins/music_service/ytmusic/node_modules/body-parser/lib/types/json.js:88:5)
at Layer.handleRequest (file:///data/plugins/music_service/ytmusic/node_modules/router/lib/layer.js:152:17)
at trimPrefix (file:///data/plugins/music_service/ytmusic/node_modules/router/index.js:342:13)
at file:///data/plugins/music_service/ytmusic/node_modules/router/index.js:297:9
at processParams (file:///data/plugins/music_service/ytmusic/node_modules/router/index.js:582:12)
at next (file:///data/plugins/music_service/ytmusic/node_modules/router/index.js:291:5)
at file:///data/plugins/music_service/ytmusic/node_modules/body-parser/lib/read.js:171:5
Quick check on stackoverflow - I activated Yt-Dlp, now it plays. Still don’t understand, tho.
There should be safeguard against PayloadTooLargeError, so I don’t know why it gets triggered in your case. When you activate yt-dlp, the plugin will use that to get streams, bypassing the code that triggered PayloadTooLargeError. yt-dlp is less efficient so it should be used as fallback.
When the plugin gets released in the plugin store, perhaps you could try installing that and see if you still get PayloadTooLargeError.
Yes, I’m aware of it not being the best solution. I’m watching the plugin. At least I already updated volumio to 4.1.xxx.
Thanks!
Can now get the Cookie to take and authenticate. Can elect songs but will not play. They will show in the Now playing screen after a delay but no audio.
Could you try the version from the plugin store (v2.5.1)? It’s in the beta channel now. Remember to restart after installing.
I’ve just installed v2.5.1 from the Volumio plug in area. I had to uninstall the previous version, prior to doing this I copied and pasted my cookie to save getting a new one. Restarted and pasted the cookie back in and all seems to working fine now, thank you!
Yt-Dlp turned off.
1 Like
Yes, it’s working again. Remember, I had to install yt-dlp and turn it on in my setup.
Setup:
Latest Volumio
YT plugin v 2.5.1
yt-dlp enabled
I uninstalled the 2.5.0 plugin
restart volumio
installed from the test mode the 2.5.1 plugin, activated
restarted
got the cookie
restarted
payload error.
Turned on Yt-Dlp
playing music.
That’s odd that for some people it seems to be working. Don’t know whether that’s important, my volumio is running on a lenovo computer in a proxmox engine.
Regarding the payload error, please try v2.5.2.
Hi Patrick, does the plugin also still work without cookie? I dont need the cookie, but the plugin till the last ytmusic 2.5.2, doesnt play anything.
You don’t need cookie. Did you restart after updating? Also provide logs.
Do you also have to change your cookies every hour or half hour?
No. Most likely you didn’t obtain the cookie in a fresh, private (incognito mode) browser window, then closing it right after you’re done.
1 Like
I did restart it and now its working
Volumio: 4.119 (x86_64)
yt-music: 2.5.2
yt-dlp: 2026.03.17
The plugin plays some titles not to the end.
Plays fine here.
It plays! With Yt-Dlp off! Yay!
At the first try it broke down after 2/3 of the song, I had a deja vu and panicked, but at the second my test-track (it’s always the same 3 songs I play as a test)) played till the end. Phew. Hopefully that was just a glitch. I keep monitoring.
Thanks, Patrick!
@codevoid reported some tracks not playing till the end. But no logs are provided so I can’t diagnose. Playback is fine in my case; 10+ tracks with no early cut-off.
It broke off. That’s what my log logged (I started after pressing “play”):
Sorry, I didn’t realize it’s that long, I guess full of unecessary information, maybe that’s the culprit? I didn’t push anything just stared at the monitor…
Note my trial:
Song 1: break-off, playing till the end
Song 2: break-off, playing till the end
Song 3: playing till the end
Song 1: break-off (that’s where this log is from)
So at a first glance it doesn’t seem song-specific but more random.
info: [ytmusic] (AutoplayManager) MPD 'stop' event received
info: [ytmusic] (AutoplayManager) Check if autoplay needed
info: [ytmusic] (AutoplayManager) Autoplay not configured or there is no previous played "ytmusic" track
FULL LOG START:
info: Listing playlists
info: CoreCommandRouter::volumioGetState
info:
---------------------------- MPD announces state update: player
info: ControllerMpd::getState
info:
---------------------------- MPD announces state update: player
info: ControllerMpd::getState
info: ControllerMpd::getState
info:
---------------------------- MPD announces state update: player
info: ControllerMpd::getState
info: sendMpdCommand status took 6 milliseconds
info: sendMpdCommand status took 6 milliseconds
info: sendMpdCommand status took 6 milliseconds
info: sendMpdCommand status took 6 milliseconds
info: ControllerMpd::pushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: CorePlayQueue::getTrack 0
info: CoreStateMachine::syncState stateService stop
info: CoreStateMachine::syncState currentStatus play
info: CoreCommandRouter::volumioPushState
info: CoreStateMachine::stPlaybackTimer
info: ControllerMpd::pushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: CorePlayQueue::getTrack 0
info: CoreStateMachine::syncState stateService stop
info: CoreStateMachine::syncState currentStatus stop
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
info: No code
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
info: [ytmusic] (AutoplayManager) MPD 'stop' event received
info: [ytmusic] (AutoplayManager) Check if autoplay needed
info: [ytmusic] (AutoplayManager) Autoplay not configured or there is no previous played "ytmusic" track
info: [ytmusic] (AutoplayManager) Removed mpdStateListener
info: ControllerMpd::pushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
info: CorePlayQueue::getTrack 0
info: CoreStateMachine::syncState stateService stop
info: CoreStateMachine::syncState currentStatus stop
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
info: No code
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
info: ------------------------------ 30ms
info: ------------------------------ 30ms
info: ------------------------------ 30ms
info: CoreCommandRouter::volumioGetState
info: Listing playlists
info: Listing playlists
info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::volumioGetState
info: Listing playlists
info: Listing playlists