#Trying to Get Add Missing to Radarr Working
1 messages · Page 1 of 1 (latest)
📝 If you want to review this again, wdpaynter:
: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> 📝
Welcome @maiden dune!
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.
I am trying to take advantage of adding missing movies from collections to Radarr. I have the following added in config:
radarr:
url: http://192.168.0.116:7878
token: (redacted by Luma)
add_missing: True
add_existing: false
upgrade_existing: false
monitor_existing: false
root_folder_path: /data/media/movies
monitor: true
availability: announced
quality_profile: HD-1080p
tag: kometa
search: true
radarr_path:
plex_path:
But something in my config file is causing an error on run (full config file and log attached). Now I can';t even start the Kometa docker. Any help would be appreciated. Thx
you are using a tab
@maiden dune you are using a tab, you need to use spaces instead of a tab
i mean, the log tells you what the issue is and where to find it. just trying to be helpful
From where in the wiki? If there's a tab on the wiki that should be fixed.
he copied / pasted the radarr section, but i don't think that's a tab before the url
Are you talking about INVALID YAML?
i've copy / pasted that same section, and not had a tab issue
ok, looks like no "http:"
yes, i'm talking about invalid yml. the log tells you yaml YAML Error: while scanning for the next token | | found character '\t' that cannot start any token | | in "//config/config.yml", line 23, column 3
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
There's a tab on line 23 in your config. The ^ is pointing at it.
would recommend using a yml aware editor to help with this
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):
The error above has nothing to do with that.
I edited it and am reposting the config
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
Thanks. Running it now. takes several hours
Do you all turn off collections after they are created to speed up the scheduled Kometa run (mine is nightly)
Did I do that wrong?
see my above screenshot of your config. the red means there is an issue
You can if you want. There's no one single right answer to that.
you don't have enough spaces
how many is standard?
Two per level is typical
I thought i used 3
right, 2 for the radarr, then 2 for the level below
The specific number of spaces doesn't matter; it's the consistency. Pick one and stick with it.
I may need to fix all the rest, but here is latest. Hoping to use bot to analyze
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
the bot won't analyze your config, nothing more than the above "yaml passed..."
will analyze your log file
Antwan, how did you get it to show the errors/red formatting problem?
you are the bot? 😅
by using vscode with the recommended extensions which i tagged earlier
I can look at it, but haven;t a clue what that is. Sorry
I'm not very literate in these topics (as you've learned over the last several posts
I'm trying
what is the issue still?
I'm not sure there's an issue. I ran Kometa again, but it takes several hours to complete
Hoping it'll will add missing movies from the collections. Then I will get on wiki to figure out how to change dates to have seasonal collections show up all year
It is running
Thank you!
This is covered on the seasonal default collections page.
I will wait to close (or continue) once it has finished
Ran Kometa last night after the "add missing to Radarr" changes and changing the dates on the Seasonal Collection and neither worked. Attaching logs and config file in hopes y'all might point to my error(s). Thx
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
📝 If you want to review this again, wdpaynter:
: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> 📝
❌ TO BE CONFIGURED ERROR
You are using a builder that has not been configured yet.
This will affect any functionality that relies on these connections. Review all lines below and resolve.
In the Kometa discord thread, type !wiki and search for more information
For more information on configuring services, [https://kometa.wiki/en/latest/kometa/logs/?h=[error]#error]
10 line(s) with to be configured errors. Line number(s): 68212-68213, 68271-68272, 68439-68440, 73310, 73313, 73317, 73378
I have reviewed the errors provided by Luma and they seem to pertain to my TV library not entered properly (intentional while testing movies) and not having Trakt configured (I don;t have/use Trakt). I didn't know some of the default collections were dependent on it. I only use TMDB (and IMDB). I changed the run time of Kometa (though I am concerned it will run during time Plex is used)
went through config file to ensure spacing was correct (though I am not certain of all formatting rules). New version attached
config file passed validation, but trying to run it again seems to have caused an error and stopped Kometa container
Here is cleaned up version of config
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
seems to have fixed the add to Radarr. Will see about the Seasonal Collections after it finishes. Closing this post and will open new if Seasonal needs tweaking. Thank you all
That last log doesn't contain any changes to the default seasonal dates:
...
- default: based
- default: seasonal
- default: decade
...
and so none of the seasonal collections are created during a run on August 28th:
| Seasonal Collections Collection in Movies |
| Collection 🎊 New Year's Day Movies not scheduled to run and could not be found to delete |
| Collection 💘 Valentine's Day Movies not scheduled to run and could not be found to delete |
| Collection ☘ St. Patrick's Day Movies not scheduled to run and could not be found to delete |
| Collection 🐰 Easter Movies not scheduled to run and could not be found to delete |
| Collection 🤱 Mother's Day Movies not scheduled to run and could not be found to delete |
| Collection 🪖 Memorial Day Movies not scheduled to run and could not be found to delete |
| Collection 👨 Father's Day Movies not scheduled to run and could not be found to delete |
| Collection 🎆 Independence Day Movies not scheduled to run and could not be found to delete |
| Collection ⚒ Labor Day Movies not scheduled to run and could not be found to delete |
| Collection 🎃 Halloween Movies not scheduled to run and could not be found to delete |
| Collection 🎖Veteran's Day Movies not scheduled to run and could not be found to delete |
| Collection 🦃 Thanksgiving Movies not scheduled to run and could not be found to delete |
| Collection 🎅 Christmas Movies not scheduled to run and could not be found to delete |
| Collection 🌊🌺 Asian American & Pacific Islander Heritage Month Movies not scheduled to run and could not be found to delete |
| Collection ♿ Day of Persons with Disabilities Movies not scheduled to run and could not be found to delete |
| Collection ✊ 🏿 Black History Month Movies not scheduled to run and could not be found to delete |
| Collection 🏳️🌈 LGBTQ+ Pride Month Movies not scheduled to run and could not be found to delete |
| Collection 🪅 Latinx Heritage Month Movies not scheduled to run and could not be found to delete |
| Collection 🚺 Women's History Month Movies not scheduled to run and could not be found to delete |
This:
- default: seasonal
template_variables:
schedule:
years: range(01/01-12/31)
valentine: range(01/01-12/31)
patrick: range(01/01-12/31)
easter: range(01/01-12/31)
mother: range(01/01-12/31)
memorial: range(01/01-12/31)
father: range(01/01-12/31)
independence: range(01/01-12/31)
labor: range(01/01-12/31)
halloween: range(01/01-12/31)
veteran: range(01/01-12/31)
thanksgiving: range(01/01-12/31)
christmas: range(01/01-12/31)
aapi: range(01/01-12/31)
disabilities: range(01/01-12/31)
black_history: range(01/01-12/31)
lgbtq: range(01/01-12/31)
latinx: range(01/01-12/31)
women: range(01/01-12/31)
Is incorrect syntax.
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
You probably took that from the list at the bottom of the page, where it says this is not how you change those things.
The example shows how to do this:
libraries:
Movies:
collection_files:
- default: seasonal
template_variables:
use_independence: false
schedule_thanksgiving: range(10/01-10/30) # <<< HERE
And if you want to change all the schedules make them all visible at all times you can use a single schedule as shown in the template variables section:
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
Your config could be corrected and simplified to:
- default: seasonal
template_variables:
schedule: daily
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
@maiden dune move to this thread, please
I have edited my config since the currently running Kometa instance was started
Is the one from the other thread still current or has it changed since then?
How about the way I have settings split to (3) different areas?
It's hard to say anything about a moving target.
it has changed
Then there's no way for anyone to comment on it.
changed some to get it running, ran Kometa, and manually changed some code while it is running
I'm not going to waste time looking at a config that isn't the one you're using.
ok
You ask for help and then change it after, without letting anyone know
I posted the config file. I did not know that was upsetting
But you just said it has been changed since you posted it.
The topic of this thread was resolved
It is upsetting when you post it, ask for help, and then change it without telling anyone
If you look above, I posted everything I was doing and got it working
But then you created a new thread that was still partially covered in this thread, without first fixing your config
The config in that log above and the config that follows it are different. Then you apparently posted yet another modified config. Which config are you seeking help with? Post that config, then stop changing it.
My new thread was mainly asking about how the formatting (especially "settings") was supposed to be
I will wait till Kometa is done running. I apologize. I am nmew to all of this (including this Discord- and even Discord itself really)
There is no need to wait until it's done running.
You have a config you want comments on, right?
post that config and then leave it alone until we are able to provide some comments.
Ok
The current log, if Kometa is running, will have an old config.
We don't want the old config.
We want the config as it is now with the changes that have been made while Kometa has been running.
I have a copy of the config you posted in the other thread. Have you changed it since then?
I posted the config above at 10:46 am EST
It has not been changed since
10:47
here it is
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
@maiden dune I would recommend changing your seasonal to this #1278135110574542869 message
done. thx
hell of a lot easier!
No need for this:
remove_overlays: true
This is broken as described above:
- default: seasonal
template_variables:
schedule:
years: range(01/01-12/31)
...
Some of these are the default values which aren't changing here, so you don't need them
settings:
asset_directory: /media/movies
prioritize_assets: true # << NOT NEEDED
show_missing_assets: false # << NOT NEEDED
asset_folders: true # << MOVE THIS TO TOP-LEVEL SETTINGS
Empty template variables attribute not needed:
collection_files:
- git: bullmoose20/tv_refresh
template_variables: # << NOT NEEDED
- default: network
Some of these are the default values which aren't changing here, so you don't need them
settings:
asset_directory: /media/tv
prioritize_assets: true # << NOT NEEDED
asset_folders: true # << MOVE THIS TO TOP-LEVEL SETTINGS
asset_depth: 1 # << MOVE THIS TO TOP-LEVEL SETTINGS
create_asset_folders: false # << NOT NEEDED
This is in the wrong place. operations needs to be under each library, so this needs to be duplicated and indented correctly under each library.
operations:
split_duplicates: false
assets_for_all: true
# mass_user_rating_update: mdb_tomatoes
mass_critic_rating_update: imdb
mass_audience_rating_update: tmdb
mass_genre_update: tmdb
# mass_content_rating_update: mdb_commonsense
mass_originally_available_update: tmdb
mass_imdb_parental_labels: none
mass_poster_update: tmdb
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
The remove overlays was in there after testing a small library and me not wanting ANY overlays. Thx
I will look at the others
Thank you! I beleive I did all of the above:
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
remove_overlays: true # Set to true if you want to remove overlays
Forgot that one
operations still wrong.
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
Think I should interrupt Kometa and run this new config?
...actually, with it adding missing movies to Radarr, I think I should let it finish
config seems fine