This add-on is currently a work-in-progress and cannot be installed yet from the Kodi add-on manager.
This is a simple Kodi service add-on that syncs (bi-directional) settings to a Dropbox folder. It is still heavily in development. I will release a very early alpha version as soon as some basic tests are completed. Want to help testing? Let me know I will make sure a test version is made available.
Backups! Yes, you need them
This add-on can seriously mess up your Kodi’s addon_data folder. Before you continue to use this add-on, please, please, please, backup those folders on all machines and Kodi profiles you are going to run the sync with.
You will need to have the following in order to make this all work:
- Full backups of your addon_data folders (yes, again a reminder!)
- Kodi Krypton (or higher) installed on either Linux, Windows or Android.
- A Dropbox account with some storage available.
- A Dropbox Developer App API Key:
- Currently this add-on does not (yet) provide OAuth authentication. So you will need to create your own app to make it work.
- Head over to Dropbox.com’s App Console.
- Create a new app there with the Dropbox API.
- Select the “App Folder” access option.
- And give the app an appropriate name.
- Then go into the app’s settings and select “Generated access token“.
- Configure that token in the Kodi Add-on settings for the Dropbox.
- Think of a nice name for sync group
How it works
Within the add-on settings for this add-on you specify a Sync Group. All sync add-ons with the same Sync Group configured will sync the full addon_data folder with Dropbox and thus with each other. You can create multiple Sync Groups that group different Kodi installs or even Kodi logins into different Sync Groups. However, you can only sync each instance of the add-on to a single Sync Group.
Depending on the situation files will update uploaded or download. The following table describes what happens in what scenario:
|Local \ Remote||Added||Existing||Non-Existing||Deleted|
|Added||Sync most recent.||Should not happen but if then we sync the most recent.||Upload local file.||Upload local file.|
|Existing||Should not happen but if then we sync the most recent.||Sync most recent, or if no changes then don’t sync.||Upload local file.||Was the local file updated after the last sync? Yes, then upload, else delete locally.|
|Non-Existing||Download remote file.||Download remote file.||No action (Duh!)||No action.|
|Deleted||Download remote file.||Was the remote file updated after the last sync? Yes, then download, else delete remotely.||No action needed.||No action needed.|
Let’s look into some examples:
- A file exists both locally as remote. This will lead to Sync most recent, or if no changes then don’t sync and thus the add-on will check what he most recent version. If the local one is newer, it will be upload. If the remote version is newer, that version will be downloaded. If they did not change, nothing will happen.
- What if I add a new add-on locally? The settings for that add-on are Added locally an Non-Existing remotely: so they will be uploaded.
- In the previous case, other instances of Kodi will see the setting files as Added remotely and Non-Existing locally and they will thus be downloaded.
- What if you a new Kodi instance? Then some files might exist in both locations and the most recent ones will be synced and all missing files will be downloaded.