Over-the-air channels with Yahoo/API

[jldet5]

Code:

I guess this doesn't work for ATSC. Analog only?

Send me a copy of your OverTheAir.ini file and I will look into it

Thanks!

[jdonth]

It appears that all the providers for zip code 60102 are returning 0 bytes in the schedule zip file. :mad:

Code:

I am using the following call to the Yahoo servers:

  Agent = 'Mozilla/3.0 (compatible)';
  URL = 'http://api.digitalhomeservices.yahoo.com/V0_1/tribune' +
                   '?mode=schedule&provider=' + Provider + '&country=us'

where Provider is the Provider ID (such as IL63463).

It works for my zip code, 76020, and has worked for several other developers.

Does anyone know if there are geographic restrictions to accessing the Yahoo servers via the API? If so, this approach is doomed.:confused:

[jldet5]

It appears that all the providers for zip code 60102 are returning 0 bytes in the schedule zip file. :mad:

Code:

I am using the following call to the Yahoo servers:

  Agent = 'Mozilla/3.0 (compatible)';
  URL = 'http://api.digitalhomeservices.yahoo.com/V0_1/tribune' +
                   '?mode=schedule&provider=' + Provider + '&country=us'

where Provider is the Provider ID (such as IL63463).

It works for my zip code, 76020, and has worked for several other developers.

Does anyone know if there are geographic restrictions to accessing the Yahoo servers via the API? If so, this approach is doomed.:confused:

That sparked an idea. I changed the zip code to 60601 and I got data. 60102 is a NW suburb of Chicago. May still be hope Gonna look at the data now.

[jdonth]

I tried 60601 and am still getting zero bytes. Any idea if they are blocking by IP or do I need to add some additional header info in the HTTP call like HOST to get them to "like" the call?

In my excitement to get this working from -OZ's previous work, I forgot to ask, where did the Yahoo API call data come from?

I assumed that we are allowed to use it. Can anyone shed any light on this?

[jldet5]

I tried 60601 and am still getting zero bytes. Any idea if they are blocking by IP or do I need to add some additional header info in the HTTP call like HOST to get them to "like" the call?

In my excitement to get this working from -OZ's previous work, I forgot to ask, where did the Yahoo API call data come from?

I assumed that we are allowed to use it. Can anyone shed any light on this?

Now it doesn't work:mad: I got one good XML file and it now seems to be blocked?:confused:

[jldet5]

It started working again. Seems to be hit or miss. 60603 worked also.

Can you change the program to not wipe out the XML file when it returns zero bytes?

[jdonth]

I posted a new version (0.7.7.14) that should not delete the XML file if the new one is going to be zero bytes.

http://www.donth.com/ota.zip

Let me know if this works, OK?

[jdonth]

Ok, more information on the Yahoo API empty Schedule file issue.

It seems that the Yahoo servers check the location of your IP before delivering a ProviderID's schedule.

I tried to get a schedule for zip code 33410 (I live in 76020) and received a zero byte file. I had my brother, who lives in 33410, try the same thing and he received a valid data file.

Can anyone confirm or comment on this observation?

[jldet5]

Ok, more information on the Yahoo API empty Schedule file issue.

It seems that the Yahoo servers check the location of your IP before delivering a ProviderID's schedule.

I tried to get a schedule for zip code 33410 (I live in 76020) and received a zero byte file. I had my brother, who lives in 33410, try the same thing and he received a valid data file.

Can anyone confirm or comment on this observation?

I think there is something else going on. I was just able to get 92101 Analog listings. Digital listings are the ones that seem to trip it up.

[whurlston]

I think there is something else going on. I was just able to get 92101 Analog listings. Digital listings are the ones that seem to trip it up.

It usually times out on the first download attempt. Even through the Go 4 TV app. I don't know if the listings are being build on the fly or what. That is why my app has a "retry" built into it. Hope this helps.