Hello everyone,
I’m experiencing a very peculiar issue with my Kodi (CoreELEC) setup and Jellyfin, and I’m hoping to get some insights from the community.
The Problem: Kodi (running on CoreELEC) consistently sends a “playback stopped” or “resume point updated” signal to my Jellyfin server, indicating that a movie has stopped playing, while the movie is still actively playing on Kodi without interruption. This leads to incorrect playback status in Jellyfin (e.g., marking a movie as stopped when it’s still ongoing, or showing the wrong resume point if I actually pause/stop it later).
My Setup:
- Kodi Device: CoreELEC on Minix U22-XJ Max
- Kodi Version: 21.2-Omega (Amlogic-ng.arm)
- Jellyfin for Kodi Add-on Version: 1.0.7
- Jellyfin Server: Ubuntu Server Jellyfin on docker container.
- Jellyfin Server Version: 10.10.7
- Network: Wired Ethernet connection for both Kodi device and Jellyfin server.
- Router: MikroTik RB2011UiAS-2HnD running RouterOS 7.6 (stable).
Observed Behavior (Logs & System Info):
I’ve gathered some logs and system statistics, which seem to indicate everything is functioning normally, yet the issue persists:
- Kodi Log Snippet (when the “stop” event occurs):
2025-06-22 18:58:39.287 T:21385 info <general>: JELLYFIN.jellyfin_kodi.objects.movies -> DEBUG::jellyfin_kodi/objects/movies.py:376 New resume point 88c5816b1c3e2171d589ea7136e059d5: 589.0 2025-06-22 18:58:39.290 T:21385 info <general>: JELLYFIN.jellyfin_kodi.objects.movies -> DEBUG::jellyfin_kodi/objects/movies.py:379 USERDATA movie [222/81] 88c5816b1c3e2171d589ea7136e059d5: Karalienės sesuo ... (database updates and library scans follow) ... 2025-06-22 18:58:41.426 T:4906 info <general>: JELLYFIN.jellyfin_kodi.monitor -> INFO::jellyfin_kodi/monitor.py:45 --<[ kodi scan/video ]This indicates Kodi successfully updated the resume point (e.g., at 589 seconds) and processed it internally. - Jellyfin Server Log Snippet (corresponding to the above Kodi event):
[18:58:35] [INF] Started user data sync [18:58:36] [INF] Saving playback tracking activity in DB [18:58:36] [INF] User Data Sync: User neoromancer (...) posted 2 updates [18:58:36] [INF] Finished user data sync, taking 00:00:00.7352848 [18:58:36] [INF] Playback stop tracker found, processing stop : (...) [18:58:36] [INF] PlaybackTracker : Adding Stop Event : 06/22/2025 18:58:36This confirms Jellyfin received and processed a “stop” event, correctly identifying the user and the item. - MikroTik Router Statistics (
/system resource printand/interface ethernet print stats):
- Uptime: 16+ weeks (stable)
- RouterOS Version: 7.6 (stable, build-time Oct/17/2022) - Note: I’m aware this is not the latest and plan to update soon, but the issue persists.
- CPU Load: 5% (very low)
- Free Memory: 76.7MiB / 128.0MiB (sufficient)
- Ethernet Interface Stats: No
errors,drops,collisions,overflows, or other physical layer issues on any interface (ether1,ether2show clean traffic over 16 weeks). - Connection Tracking (
/ip firewall connection print count-only): Only 62 active connections (very low, no overload). - ARP Table (
/ip arp print): Healthy, mostlyDC(dynamic complete) entries, no widespreadincompleteissues. - Firewall Rules (
/ip firewall filter print): Standard, secure configuration. No rules actively block or interfere with LAN-to-LAN traffic (between Kodi and Jellyfin server) or established connections. “FastTrack” is enabled.
My Analysis so far:
Based on the logs and router stats, the MikroTik router is performing exceptionally well, with no signs of network instability, packet loss, or resource bottlenecks that would explain this behavior. The physical network layer appears solid.
Both Kodi and Jellyfin logs indicate successful communication regarding the playback status and stop events. However, Kodi continues to play the video on screen, despite reporting a stop to Jellyfin.
Seeking help with:
- What could cause Kodi to send a “playback stopped” event to Jellyfin while the video is still playing locally?
- Are there any specific Kodi or Jellyfin for Kodi add-on settings I should scrutinize that might lead to this?
- Could this be a very subtle bug in a specific version combination of Kodi, Jellyfin for Kodi, or Jellyfin server that isn’t immediately obvious from logs?
- Any advanced debugging steps for Kodi or the Jellyfin add-on that might shed more light on the internal playback state?
Any ideas or similar experiences would be greatly appreciated!
Thank you!