@travisbell said:

"TMDB Support" is and always has been me, and there's nothing I have ever done related to IP's or location.

OK, but think about ANY maybe little changes in any way happend in February?! There must be something happened on your/TMDB side because on the other side -WDLIVETV- nothing happened since years and I think never will again....

I remember ~2 years ago my WDlive devices (I have 5 of them) started in a boot loop - and I was tricky to get the device get back working normaly - the problem was an app called "Accu Weather" who makes changes and causes the trouble.

Hi guys,

I was already hoping to find a solution to the problem here. I'm from Germany and I have the exact same problem with my WDTV that no more content can be found by the TMDB. About two or three weeks ago, it went without any problems.

Unfortunately, I'm not a network specialist either and don't know how to read the data traffic. Unfortunately, there is no way to change any settings on the WDTV, because this is a closed system and you can only access a simple web frontend via the IP address.

I'm still trying to figure something out, but WD support is definitely not helpful here.

Hi guys,

Yes same here, long time WD TV Live user. I'm experiencing the same issue, since about a month or two ago I can no longer fetch new movie metadata.

The only thing I can think of, for the time being, is to modify an existing .xml file for a different movie which has metadata. Once the .xml file is open, switch the text and links for the new movie. I'm no IT expert so tell me if that idea is completely off the mark!

It looks like the WD does get movie images and backdrops through the web as I cannot find any images stored locally. Maybe that's a good sign if there is still some sort of database connection?

I have had the same setup for the last 10 years now so it would be a real shame if no fix is found.

I'm in the UK

I'am a step further now.

After testing "tiny media manager" and "Media Elch" and some other programs I think that Media Elch gives me as a user of the WDLIVETV device the option to scrapp & get all the Metadata I need. It takes a few modifications, work and testing but now I had cover, actors, lengh and text like before. The only thing not working so far is loading backdrop pictures from the movie - but it is something that is OK for me.

Don't understand me wrong - I still hope that a fix will repair the feature on the device (!) - but like it seems noone will do this at least at the moment... So the Media Elch option is far more easy that editing the xml file manually for each new movie and nearly as compfortable as the former option on the device itself beacause it scrapps everything you need by a simple click.

Note from me. Personaly. It is a shame a big company don`t give a f##k like WD did with their device. The "support" page on their website and their "experts" there are not helpful in any way. Even when a device (and many were sold all over the world and still active) is no longer sold. Yes, it is a closed system - and they know what happend inside.

Normaly this should make a difference when you buy a product from a well known company like WD or get a cheap unkown android device from china. Normaly. Just my 2 Cents.

Can you provide the info for how you modified the WDLIVETV to use Media Elch, it would be much appreciated

Hello.

using a managed switch, with port mirroring function, and wireshark as sniffer, i found the request and response

this is the request:

http://api.themoviedb.org/3/search/movie?api_key=*&query=xwv&language=it&year=

the key "api_key" contains a value that is the same for every film i searched, it is not like a kind of url's sign, so i don't know if i can publish the value of api_key.

In this case, i tried a film called "xwv".

the response is long, the most important parts are this ones:

[Path with value: /status_message:Invalid API key: You must be granted a valid key.]
[Member with value: status_message:Invalid API key: You must be granted a valid key

    Source Address: 99.86.159.68
Hypertext Transfer Protocol
    HTTP/1.1 401 Unauthorized\r\n
        [Expert Info (Chat/Sequence): HTTP/1.1 401 Unauthorized\r\n]
            [HTTP/1.1 401 Unauthorized\r\n]
            [Severity level: Chat]
            [Group: Sequence]
        Response Version: HTTP/1.1
        Status Code: 401
        [Status Code Description: Unauthorized]
        Response Phrase: Unauthorized

putting the request in a browser, i had the same response in json

{"status_code":7,"status_message":"Invalid API key: You must be granted a valid key.","success":false}

Thank you for support.

@gilboski64 said:

Can you provide the info for how you modified the WDLIVETV to use Media Elch, it would be much appreciated

I don't modified the WDLIVE - there is no way you can do this. I make some preferences in Media Elch so that you get an .xml file with all about the movie (year, lengh, actors, description, genre) and also a movie cover metathumb - both that is located on your PC in the folder of the movie. When you connect the storage device the data is already where the WDLIVE device can read it. You do the scrapping on the PC like before from the WDLIVE.

Media Elch is free to download for Linux, Windows and MacOS. Without making some changes it seems working with KODI easily, but there is a way to get scrapping data readable for the WD.

@ercolepatata Probably best not to share the API key here, but can you email me at travis [at] themoviedb.org with the API key that is being used? I can then check as to why it's been disabled.

@travisbell said:

@ercolepatata Probably best not to share the API key here, but can you email me at travis [at] themoviedb.org with the API key that is being used? I can then check as to why it's been disabled.

Hello.

i sent an email with a link to this thread.

Sincerly.

Thanks @ercolepatata, I was able to see the API key this device is using and after a bit of digging I can now tell you what happened.

Western Digital deleted their account on TMDB sometime in early February. This explains why I can't find them with any of their domains like I mentioned earlier in this thread. Their account is gone, and I can tell you with 100% certainty it was Western Digital's doing.

is it not possibile keep the api_key activated without an account?

Thanks.

No, we cannot. Every API key must belong to an account.

But even still, the problem is bigger than that. It's not my (or TMDB's) place to intervene or get in the middle of an action taken by Western Digital and one of their products. I realize that this product is EOL'd but it's not ours. When a user deletes an account, it is very clear that they are deleting everything (including API keys) so you can assume they knew what they were doing.

There's also another very important element to this which is that Western Digital may have taken this step on purpose to properly terminate any relationship or liability they feel they may have had by having one of their products continue to use TMDB. I'm hoping you can appreciate these aspects which is why our hands are pretty much tied.

If you have the ability to SSH (or otherwise terminal) into the box, you can probably find the file that holds the original API key and update it with something new. If you don't, then their integration with TMDB might be over.

@travisbell said:

No, we cannot. Every API key must belong to an account.

Question: Can't you (or someone else) simply "create" a new account compatible with API key for the device?

Or: Like I said before - deep in the menu the device has an option to load a configuration file for a "new" metadata source ("new" could be TMDB again). That was also done a few years ago by a user when WD makes a FW Update and the scapping was not working....

@DiGiTALY-LiVE said:

Question: Can't you (or someone else) simply "create" a new account compatible with API key for the device?

I explain in a fair bit of detail with my reply above as to why we will not be doing that.

Or: Like I said before - deep in the menu the device has an option to load a configuration file for a "new" metadata source ("new" could be TMDB again). That was also done a few years ago by a user when WD makes a FW Update and the scapping was not working....

Sure, but that's something you guys will have to figure out. That won't involve us (other than you or somebody else requesting a new API key and using it as the new key). That's what I suggested above.

Good morning.

if I convince WD to open a new account, are you able to connect the old api_key to the new account?

Sincerly.