Trakt configuration error

[karmic sonnet]

Hi, I have a trakt configuration in my config.yml, but it doesn't seem to be working as the log returns an error every time.

The config:

  client_id: [...]
  client_secret: [...]
  pin:
  force_refresh: true  
  authorization:
    # everything below is autofilled by the script
    access_token: 
    token_type: 
    expires_in: 
    refresh_token: 
    scope: public
    created_at: ```

[errant canopy]

Welcome @karmic sonnet!

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.

📝 If you want to review this again, buurmanjuan:
: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> 📝

**User Info**

Author of Linked Message: Badjas Man
Person who Invoked the Command: Badjas Man
File Name: message.log

Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation ❌
Page 05: Rec 01 - ❌🛠️ INCOMPLETE LOGS
Page 06: Rec 02 - ❌ TO BE CONFIGURED ERROR
Page 07: Rec 03 - Error: Plex scheduled time is missing.
Page 08: Rec 04 - Error: Memory value not found in content.

Page 1/8

[rocky rivet]

You need to either:

1. get a PIN and enter it into your config as described here:
   https://kometa.wiki/en/nightly/config/trakt/
   Kometa will use that PIN to complete the auth and fill in the rest of the authentication block.

OR
2. go to https://utilities.kometa.wiki, go through the Trakt auth process, and paste the full authentication block into your config, as discussed here:
https://kometa.wiki/en/nightly/config/authentication/

[rocky rivet]

What's happening in your case is that you have only the ID and secret configured; at runtime Kometa is displaying a URL, and you are supposed to follow that URL, get a PIN, and paste it in.

However, you are not running Kometa in an interactive context where it can wait for that PIN, which causes Input Failed.

You can use one of the methods above to sidestep that interactive component.

[stuck galleon]

antwanchild used !aenh

@karmic sonnet, 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.