@nickk : were you able to capture the NZ and EU channels in the XMLTV file for the device? Has this been resolved?

You should not be seeing NZ stations in US data. What device ID? I will look into it. AU and NZ come from Gracenote but from a different system. Everything US/CA/EU/UK should use the Gracenote IDs you are familiar with. It looks like the device is 131125B5. Thanks for the info on NZ and AU. I'll up...

@nickk: I need to understand if I should expect non-Gracenote IDs in the dd_progid even for US stations like I exampled above. Also, Is this what the NZ programmes look like? Are they from a source other than Gracenote? If so, is there a way you could send me a larger sample so I can support them pr...

I'm getting some results back from some CC users and there's some interesting stuff in the XMLTV file. <channel id="NZ431677.hdhomerun.com"> <display-name>HGTV</display-name> <display-name>30 HGTV</display-name> <display-name>30</display-name> <lcn>30</lcn> <icon src="http://img.hdhomerun.com/channe...

From the first post... If you have more than one HDHomeRun unit pull the DeviceAuth from each and concatenate them together. Kinda unnecessary, but sure. I did that, but I limited it to tuner devices... not realizing that a Servio will give a blanket authorization to all other devices in the request.

So that was the root of my problem... I didn't include the deviceAuth from the Servio in the request.

Thank you very much, everyone.

So even though the Servio has no tuners, because its' DvrActive response is true, then all other devices in the deviceAuth string will have access to the XMLTV data? We only need a single device active to gain access to XMLTV?

Okay, so his DVR Service is with the SERVIO purchase. It appears his HDHR3-CC is not currently attached to the service though. Question, can he attach his tuner to the DVR Service? (I would assume so) Also, would the Servio deviceauth need to be included?

Quick one first - the URL should be api.hdhomerun.com not my.hdhomerun.com. I am looking into the 403. Edit - fixed the problem of the error message not displaying. It is reporting not-subscribed. Nick Okay, seeing the response now. Also, changed all URLs to be api.hdhomerun.com rather than my.hdho...

You should probably URL encode the DeviceAuth string to convert "/" to "%2F", but in practice that doesn't seem to matter much :) Not to speak for NickK, but I was online and a bit bored right now ... lol In this case, and I hope you don't mind (NOTE: you should probably remove the DeviceAuth strin...

I'm not seeing any message that would tell me what is wrong. On a somewhat related note, I have a user with a HDHR3-CC that continuously gets a 403 Forbidden error. I haven't found anything in the response to indicate what is wrong. I am providing the UserAgent and with the same code I can download ...

I am getting (403) Forbidden responses when trying to pull the XMLTV file using my program, but a manual request in a browser works. I noticed this late last night. Do we need header information for the requests, now? Your Accept-Encoding request header needs to have "gzip" in the list. Depending o...

I am getting (403) Forbidden responses when trying to pull the XMLTV file using my program, but a manual request in a browser works. I noticed this late last night. Do we need header information for the requests, now?

It can get exhausting sometimes, I feel you. Take a break, let the world burn for a bit, and enjoy life that doesn't involve this project. From the little I've seen of this, you deserve it.

Just my unsolicited advice.

Depending on the order of elements is risky, so I evaluate them all as a group. Having them is great for identifying what type of program it is. Knowing what the values could be allows us to filter them out from being reported as genres or such. showType: Feature Film, Short Film, TV Movie, Miniseri...