hearty lodgeBOT
Welcome @runic vector!
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.
hearty lodgeBOT
You can press the "Close Post" button above or type `/close` at any time to clos...
HI
After a recent server crash and appdata issues i have found kometa is now shoving duplicate posters in Library and Collections in TV.
I have spent hours trying to fix it but cannot stop it doing it.
Movies:
remove_overlays: true
collection_files:
- file: config/Movies.yml
collection_visibility: collections_only
TV:
remove_overlays: true
collection_files:
- file: config/TV.yml
collection_visibility: collections_only
playlist_files:
- default: playlist
template_variables:
libraries: TV, Movies
settings:
run_order:
- operations
- metadata
- collections
- overlays
cache: false
cache_expiration: 60
asset_directory: config/assets
asset_folders: true
asset_depth: 0
create_asset_folders: false
prioritize_assets: false
dimensional_asset_rename: false
download_url_assets: false
show_missing_season_assets: false
show_missing_episode_assets: false
show_asset_not_needed: true
sync_mode: append
minimum_items: 1
default_collection_order: alpha
delete_below_minimum: false
delete_not_scheduled: false
run_again_delay: 2
missing_only_released: false
only_filter_missing: false
show_unmanaged: true
show_unconfigured: true
show_filtered: false
show_options: true
show_missing: true
show_missing_assets: true
save_report: false
tvdb_language: default
ignore_ids:
ignore_imdb_ids:
item_refresh_delay: 0
playlist_sync_to_users: all
playlist_exclude_users:
playlist_report: true
verify_ssl: true
custom_repo:
overlay_artwork_filetype: jpg
overlay_artwork_quality:
refresh_all_collections: true
webhooks:
error: notifiarr
version: notifiarr
run_start: (redacted by Luma)
run_end: (redacted by Luma)
collection_changes: (redacted by Luma)
delete:
runic vector
runic vector
If i post my config.yaml will the api's get redacted by the bot ?
i have tried and tried to stop the posters in library on tv nothing works 😦
runic vector
runic vector
runic vector
page 4 does not make any sense
red dragon
FIrst, this:
collection_visibility: collections_only
Is nothing that has ever been a part of Kometa. No idea where that came from.
If you never want collections shown in the Library view, the simplest thing is to tell Plex not to do that. With this setting Plex will not put collections in the library tab unless you use Kometa to enable it for specific collections.
red dragon
page 4 does not make any sense
What host folder is mapped into the Kometa container as /config?
You can control where collections are visible individually with:
visible_library
visible_home
visible_shared
In the collection definition:
https://kometa.wiki/en/nightly/files/updates/
alpine widget
page 4 does not make any sense
Kometa doesn't see that path. Kometa sees however you have your path mapped in docker container
red dragon
I suspect that in the container config you have:
/mnt/local/appdata/kometa/config mapped to /config
So that the host assets folder that can't be found is actually/mnt/local/appdata/kometa/config/assets not /mnt/local/appdata/kometa/assets
But your container config will show whether that theory is correct.
runic vector
You can control where collections are visible individually with:
```
visible_lib...
i added the folder manually becaus eit said it was missing
alpine widget
So your assets path is /config/assets
red dragon
This is not correct:
asset_directory: /mnt/user/appdata/kometa/assets
Since Kometa has no visibility into the host filesystem without a map into the container, which doesn't appear to exist unless you cropped it off of the unraid screenshot.
That;'s reflected here:
[WARNING] | Config Warning: Path does not exist: /mnt/user/appdata/kometa/assets
Since Kometa, inside the container, cannot see /mnt/user/appdata/kometa/assets on the host. [this is standard Docker stuff, nothing Kometa-specific]
As mentioned that should be:
asset_directory: config/assets
Same as you have here:
- file: config/Movies.yml
Another issue you'll have to deal with:
| 6 | IMDb Error: URLs with https://www.imdb.com/search/ no longer works with imdb_list use imdb_search.
Due to IMDB changes, this:
imdb_list:
url: https://www.imdb.com/search/title/?title_type=feature,tv_movie,documentary,short
limit: 40
Will no longer work and will need to be changed to use the imdb_search builder:
https://kometa.wiki/en/nightly/files/builders/imdb/#imdb-search
You have 6 of those in a YAML file.
runic vector
runic vector
runic vector
red dragon
[INFO] | 2 | Collection Error: imdb_search groups attribute not supported
[INFO] | 1 | Collection Error: imdb_search release_date.gte attribute not supported
The available attributes for the imdb_search builder are shown here:
https://kometa.wiki/en/nightly/files/builders/imdb/#imdb-search
Presumably your YAML contains somethign like this:
Top Rated:
imdb_search:
type: movie
groups: top_250 ### where did this come from?
limit: 100
Oscars:
imdb_search:
type: movie
groups: oscar_winner ### where did this come from?
limit: 100
Latest Releases:
imdb_search:
type: movie
release_date.gte: datetime.date(2023, 1, 1) ### where did this come from?
sort_by: release_date.desc
limit: 50
I don't know where some of that stuff came from.
hearty lodgeBOT
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
red dragon
Should be something like:
Top Rated:
imdb_search:
type: movie
imdb_top: 250 # change this if you want some other number
limit: 100
Oscars:
imdb_search:
type: movie
event.winning: oscar_picture # change this if you want other winners
limit: 100
Latest Releases:
imdb_search:
type: movie
release.after: 2023-01-01 # change this date if you want
sort_by: release_date.desc
limit: 50
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
hearty lodgeBOT
✅ 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
red dragon
Those just show the same thing I said above. These in Movies.yml don't work, as reported in the log and discussed above:
Top Rated:
template: { name: Chart, num: 4 }
imdb_search:
type: movie
groups: top_250 ### << INVALID
limit: 100
tmdb_top_rated: 100
summary: Top Rated Movies across the internet
Oscars:
sort_title: "!00_Oscars"
template: { name: Chart, num: 5 }
imdb_search:
type: movie
groups: oscar_winner ### << INVALID
limit: 50
summary: Oscar Winning Movies
You made one of the changes I suggested but ignored the other two.
Where did this groups thing come from?
hearty lodgeBOT
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
red dragon
This:
Emmy Winners:
imdb_search:
type: tv_series
limit: 50
summary: Award-winning TV shows that have received Emmy recognition.
template:
name: Chart
num: 1
Has no "emmy-winning" criteria, so it's just going to be 50 series, no idea which.
hearty lodgeBOT
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
red dragon
There is no difference between these two:
Popular TV Series:
imdb_search:
type: tv_series
sort_by: popularity.desc
limit: 50
summary: TV shows that are currently popular across the world.
template:
name: Chart
num: 2
Trending TV Series:
imdb_search:
type: tv_series
sort_by: popularity.desc
limit: 50
summary: Trending TV shows that are currently being talked about.
template:
name: Chart
num: 4
They will contain the same things.
hearty lodgeBOT
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
red dragon
Nothing ensuring "top-rated" here:
Sci-Fi and Fantasy TV:
imdb_search:
type: tv_series
genre: sci-fi,fantasy
limit: 50
summary: Top-rated Science Fiction and Fantasy TV series.
template:
name: Chart
num: 7
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
red dragon
What am I supposed to be looking at?
runic vector
you say its not working in movies but this pops up when i run the script
the tv collections shows this
red dragon
Your log contains the following errors;
[INFO] | 2 | Collection Error: imdb_search groups attribute not supported
[INFO] | 1 | Collection Error: imdb_search release_date.gte attribute not supported
So three collections are not working due to those errors.
The failing collections are:
| Top Rated | 0 | 0 | 0 | 0:00:00 | Kometa Failure
| Collection Error: imdb_search groups attribute not supported
|
| Oscars | 0 | 0 | 0 | 0:00:00 | Kometa Failure
| Collection Error: imdb_search groups attribute not supported
|
| Latest Releases | 0 | 0 | 0 | 0:00:00 | Kometa Failure
| Collection Error: imdb_search release_date.gte attribute not supported
You will note that these three collections are not in your screenshot since they are failing. The rest are there, but not these three.
There's nothing in the TV yaml that won't work, I'm jsut pointing out that they aren't creating the colelction that you may expect.
runic vector
are there any examples i can look at
red dragon
You have this described as "emmy-winning"
Emmy Winners:
imdb_search:
type: tv_series
limit: 50
summary: Award-winning TV shows that have received Emmy recognition.
template:
name: Chart
num: 1
There is nothing in there that has anything to do with "emmy-winning". Sure, it will create a collection, but that collection will not contain exclusively shows that have won Emmys.
red dragon
are there any examples i can look at
the wiki is full of examples.
There's a community config repo that is full of examples of variable utility.
runic vector
not really bothered about that are there any good example on the movies and tvs ?
red dragon
See my previous message.
runic vector
See my previous message.
Do you meab config-showcase ?
red dragon
No, there are lots of examples in the wiki.
There is also the community configs repo:
https://github.com/Kometa-Team/Community-Configs
Those are maintained [or not] by their authors and may or may not work, but they can provide ideas.
There are the Kometa defaults:
https://www.kometa.wiki/en/latest/defaults/guide/
Things you are doing manually may be possible using the defaults.
For example, if you want collections of oscar and emmy winners, you can just add this to your config:
libraries:
Movies:
collection_files:
- default: oscars
- default: emmy
And you'll get these:
https://kometa.wiki/en/nightly/defaults/award/oscars/
https://kometa.wiki/en/nightly/defaults/award/emmy/
runic vector
cheers
gusty prawnBOT
chazlarson used !aenh
@runic vector, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.