TheTVDB agent - v4 update

The folks over at TheTVDB have been hard at work on a new version of their API and as of today we will start rolling out an updated agent which uses this new API to users on PMS 1.24.5 and higher.

This change is only applicable to anyone still specifically using “TheTVDB” agent for their TV libraries. This announcement is not applicable to you if you’re using the new “Plex TV Series” agent.

This will be done in a staged rollout so it will not be enabled for everyone right away. If you do wish to get access to test this early however you can drop a comment in this thread to request access and somebody will add you to the list.

Once you are using the new agent you should hopefully not notice any changes, things should continue to work as they always used to. If you notice issues please report these as you would normally by creating a post in the appropriate forum section and providing details on the issue along with server logs.

2 Likes

I would love to test to fix my office episodes :slight_smile:

Added.

Please note that you will have to restart your server for the change to be picked up.

I am seeing v4 working for the old tvdb agent - using dvd order the first four episodes of the fourth season of the office (which are all double episodes) are pulling the correct single episode metadata and are working great - is there a tv shows agent coming down the line too for things like the double episode as a single episode in dvd order?

Hello I would really like to test this update and hope to help with a lot of TV shows I’ve go in my library

Added you to the test group. Restart your server to pick up the change :+1:

I also would like to test the new API.

Added. Please remember to restart your server.

Nice move… any “inconveniences” expected for non-English libraries / metadata?
Anything not working as expected at this stage of the new agent develpment which was working in the “past/current” edition of your TVDB agent?

It should work exactly like it did previously.

One issue that existed with their previous API with DVD orders (some episodes being missing) should work now as they have fixed this in the v4 API.

Will this also include other TVDB episode sorting like, for instance, Netflix order of Money Heist?

No. Feature-wise the update doesn’t change anything.

  • Do we get any notification once the updated agent has been rolled out to our servers for a restart?
  • Is there any indication whether we are using the older or the new version of the agent?
  • I assume the updated agent will stay across version upgrades?
  • Will there be a version released in the future that already has the updated agent by default?

No, it will just switch over in the background when the logged-in account has been told it should use the new one.

The only real indication would be to look in the plugin logs and see which endpoints it’s hitting.

Yes, as long are you’re on 1.24.3 or higher, downgrading a server below this will return to the agent using the previous api.

It will be the default tvdb agent, just not for everyone yet - but it will be soon. But there will probably be a server update that removes the old agent code entirely at some point.

1 Like

I thought the v3 api cutoff date is tomorrow.

Does that mean that the (old) tvdb agent will stop working tomorrow for all users who have not upgraded to the new “Plex TV Series” agent or have not requested access to the v4 api here?

So the requirement for a server restart is only applicable when we have requested access to the new agent here? It will automatically switch over to the new agent otherwise without needing a server restart?

Quick update.

A change to the TVDB API was made today with how they return translations, this in turn exposed a bug in our code that handles these translations (when they don’t exist).

This has led to metadata refreshes failing for anyone using the updated agent. We will be temporarily disabling the rollout and anyone who has already received the update will revert back to the previous agent on their next restart.

Apologies for this, we’ll be rolling out an update to fix this in the next PMS release.

The v4 api is enabled again for users on 1.24.5. Staged rollout still in effect.