jellyfin / jellyfin-plugin-kodisyncqueue

https://jellyfin.org
GNU General Public License v2.0
44 stars 13 forks source link

Plugin keeps disabling itself #15

Closed cryptobank closed 3 years ago

cryptobank commented 4 years ago

I have to keep going Dashboard -> Plugins -> Kodi Sync Queue -> Enable Plugin and tick Items To Track.

Anyone with the same issue? Its really annoying.

KaXaSA commented 4 years ago

So... this is probably related to this Jellyfin issue: Unable to save settings #1881 They are working on a fix: #2008

Right now you can try to:

phob commented 4 years ago

#2008 was finished with 10.4.2

This is another bug I think with the plugin itself. This only happens with docker(on linux).

To fix it you have to go into the container and edit the file yourself. Not very pleasant.

Also the title should be changed in Jellyfin.Plugin.KodiSyncQueue is not saving the settings.

CoderMaurice commented 4 years ago

I have the same problem. What is the purpose of this plugin, the video I played on KODI, progress will not be synchronized to jellyfin, is this plugin used to handle it?

jfml commented 4 years ago

Same problem here, running Jellyfin 10.4.3 via Docker on a Synology, using Kodi addon 0.4(.1?) 😿

FallenLeave91 commented 4 years ago

Same here. Thought it was related to the new version of the Kodi Sync Client 0.5.0 but i got the same error with 0.4.1.

mcarlton00 commented 4 years ago

Is anybody still encountering this issue? I believe it was mostly a UI quirk in the server where some existing settings wouldn't be loaded properly, but mine seems to be staying enabled now when I check on it recently.

@CoderMaurice this plugin is used for incremental syncs during Kodi's startup. When you start Kodi it does the updates right away, that relies on this plugin. Playback reporting and updates while Kodi is running are handled through different mechanisms

jfml commented 4 years ago

@mcarlton00 I've since switched to MPV-Shim, so I can't say, sorry.

oddstr13 commented 3 years ago

This has been an issue server-side (in web iirc) a couple of times, so closing this now. Comment here, reopen or create a new issue if you still encounter this issue.