@DiGiTALY-LiVE said:

@illustratedfish said:

Can you post your settings for Media Elch on a different forum, in German, and post the link here?

Sorry, but why should I do this?

You: “I came here to find help ... but there is no help here via TMDB or from WD. This is disappointing from both sides”

Me: “Can you share your results for a workaround?”

You: “Why? I can’t benefit from this in any way”

lol thanks

@DiGiTALY-LiVE said:

@illustratedfish said:

Can you post your settings for Media Elch on a different forum, in German, and post the link here?

Sorry, but why should I do this? And where? I cannot jump or choose "just another" forum and start a thread to put in a complete workaround.

To make this understandable I think you need at least 2 hours to write everything down an make some helpfull screenshoots - and after this you had to answer questions when somebody don't understand something or makes a mistake (in syntax e.g.). I think I don't can benefit in this in any way...

I came here to find help ... but there is no help here via TMDB or from WD. This is dissapointing from both sides - but maybe you look and try Media Elch for yourself - it is really possible to get a working .xml file.

Hi, Kannst Du mir helfen mit Media Elch. Ich bekomme zwar die Infos eingelesen, aber WD TV kann sie nicht lesen. Danke

So I opened an account with TMDB and got an API key. I also found a sample meta -source xml file for WDTV on a forum. I modified the xml sample file to reflect the new API key and I went into the WDTV setting under "add new meta-source" and I chose the xml file, however, it is not working. Either the API key (for developers) only works with apps, or the sample file doesn't have the correct format. Any suggestions how to resolve this is very much appreciated.

Can anyone here advise me how to access the meta-source manager that is currently installed on all our WDTVs? I got a developer API key from TMDB so I'm assuming that if I took the existing code and updated it to use the new API key and added it as a new meta-source manager then it should work. If anything I'm saying doesn't make sense then please let me know as I'm not an expert on this sort of application but if this does work then it may be a solution for everyone.

I think I'm starting to get my head wrapped around this and may be getting closer to a solution. The tmdb.xml is located in the firmware updates. For some reason I can't seem to find the most recent tmdb.xml file though. I've located the most recent firmware update, 2.02.32, but when I extract the files from the .bin file the tmdb.xml file seems to be referencing the API 2.1 architecture instead of the API 3 architecture that it should be. I note from someone else's post from a few months ago when we first discovered that WD had deleted their account, the request to TMDB that was getting rejected as invalid api_key was referencing the API 3 architecture. I'm not sure if anyone has a copy of the tmdb.xml file that is currently on the WD TVs or know what firmware version it is located in but if we can get our hands on that then we should be able to modify the file and create a working metadata scraper for TMDB using a new api_key that you can get from TMDB. Any feedback would be great.

@ercolepatata said:

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.

Can you tell me what firmware version you are on as I can see in the code above that it is referencing the API 3 coding but when I pull up the xml file from the firmware updates it is still using the API 2.1 coding so I'm not sure how to update the old coding. If I can figure out which firmware version your file is from I should be able to get it working again.

Same issue here. With no support from either TMDB or WD, I'm exploring how to install an alternate Meta Source. Anyone else have thoughts on how to best do this?

@AussieTMDB said:

Same issue here. With no support from either TMDB or WD, I'm exploring how to install an alternate Meta-Source. Anyone else have thoughts on how to best do this as TMDB API updates have broken the last firmware version from WD.

Noting that it only affects Movies using TMDB, as I still get TV Show metadata automatically populated and working fine on WD TV Live Streaming Media Player version 2.03.20 with TVDB as the Meta-Source.

Manually installing .jpg images (as the metathumb) and edited XML data still works, but this is a real pain and not sustainable for large collections.

@ercolepatata said:

I contacted wd and the question is on the table of wd senior team.

73 days or 2 and a half months later is what only happened - it moved directly from the table of the WD senior team in San Jose to their Waste container where they burried the device.

@DiGiTALY-LiVE said:

@ercolepatata said:

I contacted wd and the question is on the table of wd senior team.

73 days or 2 and a half months later is what only happened - it moved directly from the table of the WD senior team in San Jose to their Waste container where they burried the device.

Keep the pressure on WD. I'm trying to. If we can get the copy of the xml file currently installed on the devices, it is easy to modify it with an active API key to fix the problem. I'm also trying to figure out how to access the files in the WD too as then we don't even need WD for anything. If anyone can help get that file it can fix it for everyone.

@Scooby1965 said:

@DiGiTALY-LiVE said:

@ercolepatata said:

I contacted wd and the question is on the table of wd senior team.

73 days or 2 and a half months later is what only happened - it moved directly from the table of the WD senior team in San Jose to their Waste container where they burried the device.

Keep the pressure on WD. I'm trying to. If we can get the copy of the xml file currently installed on the devices, it is easy to modify it with an active API key to fix the problem. I'm also trying to figure out how to access the files in the WD too as then we don't even need WD for anything. If anyone can help get that file it can fix it for everyone.

Someone must have that file because it used to be on the WD website for download for people who wanted to add a new meta-source. It was under "meta-source sample". I found the article explaining how to add a new meta-source, but the link and the WDTV website is dead.

@Terra1226 said:

@Scooby1965 said:

@DiGiTALY-LiVE said:

@ercolepatata said:

I contacted wd and the question is on the table of wd senior team.

73 days or 2 and a half months later is what only happened - it moved directly from the table of the WD senior team in San Jose to their Waste container where they burried the device.

Keep the pressure on WD. I'm trying to. If we can get the copy of the xml file currently installed on the devices, it is easy to modify it with an active API key to fix the problem. I'm also trying to figure out how to access the files in the WD too as then we don't even need WD for anything. If anyone can help get that file it can fix it for everyone.

Someone must have that file because it used to be on the WD website for download for people who wanted to add a new meta-source. It was under "meta-source sample". I found the article explaining how to add a new meta-source, but the link and the WDTV website is dead.

If you have the link, the internet archive may still have a copy. If you can post the link I will have a look for it and let you know.

@Scooby1965 said:

@Terra1226 said:

@Scooby1965 said:

@DiGiTALY-LiVE said:

@ercolepatata said:

I contacted wd and the question is on the table of wd senior team.

73 days or 2 and a half months later is what only happened - it moved directly from the table of the WD senior team in San Jose to their Waste container where they burried the device.

Keep the pressure on WD. I'm trying to. If we can get the copy of the xml file currently installed on the devices, it is easy to modify it with an active API key to fix the problem. I'm also trying to figure out how to access the files in the WD too as then we don't even need WD for anything. If anyone can help get that file it can fix it for everyone.

Someone must have that file because it used to be on the WD website for download for people who wanted to add a new meta-source. It was under "meta-source sample". I found the article explaining how to add a new meta-source, but the link and the WDTV website is dead.

If you have the link, the internet archive may still have a copy. If you can post the link I will have a look for it and let you know.

I will look for it. Meanwhile, I have the link for what is supposed to be this sample file http://www.mediafire.com/?5d9d74hqs6z85sa 280. Found it on a forum, I downloaded the xml file and changed the API Key to a developer key that I got from TMDB, but it doesn't work. Either the format is incorrect, or a developer key doesn't work for streaming devices? Maybe a developer key only works with apps?

@Terra1226 said:

@Scooby1965 said:

@Terra1226 said:

@Scooby1965 said:

@DiGiTALY-LiVE said:

@ercolepatata said:

I contacted wd and the question is on the table of wd senior team.

73 days or 2 and a half months later is what only happened - it moved directly from the table of the WD senior team in San Jose to their Waste container where they burried the device.

Keep the pressure on WD. I'm trying to. If we can get the copy of the xml file currently installed on the devices, it is easy to modify it with an active API key to fix the problem. I'm also trying to figure out how to access the files in the WD too as then we don't even need WD for anything. If anyone can help get that file it can fix it for everyone.

Someone must have that file because it used to be on the WD website for download for people who wanted to add a new meta-source. It was under "meta-source sample". I found the article explaining how to add a new meta-source, but the link and the WDTV website is dead.

If you have the link, the internet archive may still have a copy. If you can post the link I will have a look for it and let you know.

I will look for it. Meanwhile, I have the link for what is supposed to be this sample file http://www.mediafire.com/?5d9d74hqs6z85sa 280. Found it on a forum, I downloaded the xml file and changed the API Key to a developer key that I got from TMDB, but it doesn't work. Either the format is incorrect, or a developer key doesn't work for streaming devices? Maybe a developer key only works with apps?

I checked the link and it was using the old version that used the API 2.1 framework which is the file that I was able to access from the last firmware update. I can't figure out why the last firmware update includes the 2.1 framework instead of the 3 framework which is what appears to be used now. From what I can find in the forums, TMDB upgraded their structure back in September 2013. Someone in this thread posted their log from their router which included a query from the file showing that it was using API 3 so I'm pretty sure that is what the problem is. Here's the copy of the code which works if you manually enter it into your browser and insert your API key where the * is:

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

@Scooby1965 said:

@Terra1226 said:

@Scooby1965 said:

@Terra1226 said:

@Scooby1965 said:

@DiGiTALY-LiVE said:

@ercolepatata said:

I contacted wd and the question is on the table of wd senior team.

73 days or 2 and a half months later is what only happened - it moved directly from the table of the WD senior team in San Jose to their Waste container where they burried the device.

Keep the pressure on WD. I'm trying to. If we can get the copy of the xml file currently installed on the devices, it is easy to modify it with an active API key to fix the problem. I'm also trying to figure out how to access the files in the WD too as then we don't even need WD for anything. If anyone can help get that file it can fix it for everyone.

Someone must have that file because it used to be on the WD website for download for people who wanted to add a new meta-source. It was under "meta-source sample". I found the article explaining how to add a new meta-source, but the link and the WDTV website is dead.

If you have the link, the internet archive may still have a copy. If you can post the link I will have a look for it and let you know.

I will look for it. Meanwhile, I have the link for what is supposed to be this sample file http://www.mediafire.com/?5d9d74hqs6z85sa 280. Found it on a forum, I downloaded the xml file and changed the API Key to a developer key that I got from TMDB, but it doesn't work. Either the format is incorrect, or a developer key doesn't work for streaming devices? Maybe a developer key only works with apps?

I checked the link and it was using the old version that used the API 2.1 framework which is the file that I was able to access from the last firmware update. I can't figure out why the last firmware update includes the 2.1 framework instead of the 3 framework which is what appears to be used now. From what I can find in the forums, TMDB upgraded their structure back in September 2013. Someone in this thread posted their log from their router which included a query from the file showing that it was using API 3 so I'm pretty sure that is what the problem is. Here's the copy of the code which works if you manually enter it into your browser and insert your API key where the * is:

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

This is the WD support website: https://support-eu.wd.com/app/products/product-detailweb/p/186. It has a bunch of firmware upgrades available for download. Maybe one of these files has the API 3?