Collections wont add to Plex (Getting errors)

[harsh stream]

Please see below. Im not sure what im doing wrong.

[hollow mountain]

Welcome @harsh stream!

Someone from <@&938443185347244033> will assist when they're available.

Including meta.log from the beginning is a huge help. Type !logs for more information.

After attaching your log, do not forget to hit the green check boxes when prompted by our bot.

You can press the "Close Post" button above or type /close at any time to close this post.

[hollow mountain]

📝 If you want to review this again, supervillain0470:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

**Rec 10** - 💬💡️ **PLEX DB CACHE ADVICE**

💬💡️ PLEX DB CACHE ADVICE
Consider updating the Plex DB cache setting from 0.50 GB, to a value greater than 1 GB based on the total memory of 8.00 GB.
Setting db_cache: 1024 within the plex settings in your config.yml is effectively 1024MB which is 1GB. For more info on this setting: https://kometa.wiki/en/latest/config/plex#plex-attributes
NOTE:The number you choose can vary wildly based on a number of factors (such as the size and number of libraries, and the amount of files/operations/overlays that are being utilized).

Page 15/16

[hasty valve]

That error is caused by bad metadata in PLex for one particular movie.

It is worked around in the Kometa nightly release.

[harsh stream]

is there a guide on how to update the docker image to that release ?

[dusty mulch]

!branch

[wraith wyvern]

If you are looking for guidance on how to switch branches of Kometa, please type one of the following commands

!branchgit if you are running Kometa locally (i.e. you cloned the repository using Git)

!branchdocker if you are running Kometa within docker

!branchunraid if you are running docker on Unraid

Moving between branches of Kometa using Docker

NOTE: This is addressing changing from, for instance, latest to nightly.

replace TAG_HERE with latest, develop, or nightly; whichever you want to switch to.

The command to update/download the docker image is:

docker pull kometateam/kometa:TAG_HERE

Then recreate your container via whatever means you used to create it [docker run, docker-compose, etc.], setting the image as kometa-team/kometa:TAG_HERE

Thanks for using Kometa

[harsh stream]

trying it out right now. thank you guys.

https://metamanager.wiki/en/latest/config/trakt/#usage

i was trying to use this to get my pin

but i just get a erorr

[hasty valve]

there's a form on that page that makes it far easier. Just use that.

[harsh stream]

let me show you what i get

thank you

thats what i get when i click get pin

[hasty valve]

Probably you aren't entering the right ID or secret:

[harsh stream]

thank you.

I put the appbox external IP when creating the trakt API instead of the redirect URL

[hasty valve]

Is there anything that should change in the docs to prevent that mistake?

[harsh stream]

updating the image fixed the original issue as well

[harsh stream]

if you could add a note saying the device auth url should be copied and pasted in the "redirect URL" box

that would help

[hasty valve]

How should that change?

Just change it to say "copy-paste" instead of "enter"?

Seems like a subtle change, but sincerely if it makes it clearer that's a simple change.

[harsh stream]

nop thats and error on my end

where is the link to that page

[hasty valve]

It's the trakt page in the wiki

https://metamanager.wiki/en/latest/config/trakt/

[harsh stream]

yeah i just saw it

sorry. im an idiot

thats clear

i over read that

[hasty valve]

No worries, I just ask whenever something like this occurs.

[harsh stream]

yes makes sense. and i bet its annoying when people dont read the instructions you put in. I apologize.

when running the above in my config i get this message in my log

YAML Error: while parsing a block mapping

[dusty mulch]

that's an issue with spacing, you probably have a tab instead of spaces

what editor do you use? we recommend vscode with a couple of extensions

[wraith wyvern]

Recommended Text Editors

We highly recommend to use a decent editor software to manage Kometa's .yml files.

Standard text editors (such as Notepad and TextEdit) often save text in a rich-text format which can result in text formatted in a way that Kometa cannot read. But not only that, they also make it very hard to visually distinguish the formatting, such as indentation.
Kometa requires indents to always be multiples of 2 spaces, and not TAB stops. If you have one space too much, or too few, it is very hard to notice that with a editor like Notepad.
An editor that is more focused on editing code instead of text will automatically detect the .YML fileformat and adjust things to make it easier to work. They can also try to detect possible errors even before you actually run the .yml in Kometa.

This can save a lot of time and headaches.

Preferred:
Visual Studio Code (Windows/Mac/Linux, Opensource & Free) Website
Additionally, install the indent-rainbow by oderwat extension and the YAML by Red Hat extension and leverage our schema.json file by adding this to the top of your config.yml file: # yaml-language-server: $schema=https://raw.githubusercontent.com/Kometa-Team/Kometa/nightly/json-schema/config-schema.json

Other options:
Notepad++ (Windows only, Opensource & Free)
Website

Sublime Text (Windows/Mac/Linux, Paid)
Website

For further details and a short list of highly recommended extensions, you can also take a look here.

Here is an example of how Visual Studio Code works with indent-rainbow plugin and using our Kometa schema (Click on image to get a better view):

Thanks for using Kometa

[harsh stream]

I use regular notepad

so vcode does the spacing for you ?

[bold river]

use the above... you wont be disappointed

[dusty mulch]

no, but the rainbow indent and the other extensions help

[harsh stream]

sounds good thanks

so i am able to add collections to my tv show library

but get this errors with my movie library

[hollow mountain]

📝 If you want to review this again, supervillain0470:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

[dusty mulch]

see how this is red? that's part of what we are showing you

that error, i think was fixed in the latest nightly

you can switch to nightly branch

[harsh stream]

i am updated to nightly already

that was the first thing i was told to do in this thread

tv show library works fine

[dusty mulch]

no you are not updated to nightly

[harsh stream]

docker pull kometateam/kometa:nightly

is what i ran

[dusty mulch]

that log was not from nightly

[harsh stream]

oh damn

i didnt change over in docker

do i delete the other image in docker ?

when i type my run line into powershell it doesnt runs the "latest" version still

docker run --rm -it -v "C:\Users\USER_\kometa\config:/config:rw" kometateam/kometa

[dusty mulch]

cause you aren't telling it to run nightly

[harsh stream]

yes i figured lol. any tips on how to do that ?

im very new to this

[dusty mulch]

docker run --rm -it -v "C:\Users\USER_\kometa\config:/config:rw" kometateam/kometa:nightly

[harsh stream]

thank you

[harsh stream]

say i deploy another appbox..... can i use the same api token credentials for tvdb and trakt ? or it can only be used for one appbox at a time?

[dusty mulch]

should be able to use the same

[dusty mulch]

!afnh

[wraith wyvern]

Anything further needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.

[harsh stream]

Thank you for all the help guys I got everything up and running yesterday