Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quality profile is not selected #148

Closed
DarkGreyCat opened this issue May 5, 2024 · 1 comment
Closed

Quality profile is not selected #148

DarkGreyCat opened this issue May 5, 2024 · 1 comment

Comments

@DarkGreyCat
Copy link

DarkGreyCat commented May 5, 2024

Hello, I keep restarting the container but for some reason it always adds the first available profile instead of the one specified in the config.
Have I made some mistake? I don't see anything related to "qualityProfile" in the logs, just the default configuration which defaults to

watchlistarr | sonarrQualityProfileId: 1
watchlistarr | radarrQualityProfileId: 1

compose:

watchlistarr:
image: nylonee/watchlistarr:latest
container_name: watchlistarr
environment:
- SONARR_API_KEY=XXX
- RADARR_API_KEY=YYY
- PLEX_TOKEN=ZZZ
volumes:
- D:\Docker\aars\Watchlistarr\config:/app/config
restart: unless-stopped
depends_on:
- sonarr
- radarr
- plex
networks:
- arrs

config .yaml:

sonarr:
qualityProfile: "HD-1080p" # If not set, will grab the first one it finds on Sonarr
radarr:
qualityProfile: "HD-1080p" # If not set, will grab the first one it finds on Radarr

debug log says this for the config

2024-05-05 23:00:33 22:00:33.743 [main] DEBUG c.FileAndSystemPropertyReader$ - Failed to read from config.yaml: null

@DarkGreyCat
Copy link
Author

Whoops, I've removed the spacing before qualityProfile making the yaml file invalid...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant