I have a synology with a docker container running navidrome. It doesn’t happen all the time, but when my device is playing a list of songs (e.g. a record) it doesn’t wait for a song and it immediately skips to the next one. This can happen several times - please check the logs I uploaded for an example.
Upload description: dictummortuum
Subsonic
You give absolutely no details and the logs starts as far as:
2023-09-20 17:57:12.433 Verbose Logger Information: vayu_eea/vayu/31/12/M2102J20SG/POCO/0/true/124/126/1
2023-09-20 17:57:12.434 Verbose Logger Information: 5.8.0 (1100[arm64-v8a,armeabi-v7a,armeabi]) - DisplayMetrics{density=2.75, width=1080, height=2179, scaledDensity=2.3375, xdpi=391.885, ydpi=395.844} - FS:0.85 - AS:1.0 - (en_US) 2323b52928504dd8
Near the end you cast to Chromecast but I do not see any error and you do not tell the name of the songs or anything to know what is happening.
Can you please provide more details?
@Tolriq I’ve uploaded new logs with an identifier of “dictummortuum2”.
I started playing a record, played the first song called “flowers in your hair”, skipped near the end of the song and let it autoplay the next one.
It skipped the whole record, one song at a time, very fast. Because I have the option to continue playing after finishing a record, it did so, I suspect it skipped a bunch of songs there as well and at the end it started playing a song named “thinkin’ on a woman”.
Hope this is enough information for you to help me.
Ok so I can see the issue now, but no idea how you reached that.
Can you try to stop casting.
Enable logs, select your renderer, wait a little then stop casting. then upload the logs just for that?
Then try to reboot the chromecast and the phone and do the same and provide the new logs ?
Thanks.
Hello Tolriq,
Sorry for the delay, I wasn’t near the device to conduct the test.
So I’ve uploaded the logs: dictum3 is the test before the restart and dictum4 is the one after the restart.
Regards,
Dimitris
Ok so can you confirm that the issue is fixed after both reboots?
The logs now looks normal, the Chromecast API no more sends hundreds of // sessions data.
I tried it multiple times and it didn’t skip, so I guess it’s fixed.
The chromecast was built in my wiim pro plus, which is sleeping after a period of inactivity. I had in symphonium the option to automatically play on the chromecast, which needed some time to wake up I guess, hence the multitude of sessions.
Anyway, closing - I’ll reopen if it happens again!
The session should be closed and reopened and in the logs it was the same id, so really strange.
Logs reproducing may show something, but hopefully it won’t happen again 
Update: managed to reproduce the issue, it was solved again by restarting both devices.
If chromecast is sleeping and I have the “remember last renderer” option set, then the “play on” button turns to red for a while. If I press on it to check the renderers, then the list is flooded with multiple renderers that are actually the same.
I’m guessing that the renderer announces itself multiple times while its waking up and the list doesn’t group the renderers by a unique ID, but that’s just guesswork.
Please provide logs when it occurs.