Perfectly reasonable explanation. I will enable the rest when I get home later tonight and let you know. Curious, why only check the enabled channels? Why not use all channels to determine zipcode?

Thanks!
Gary

jasonl wrote: ↑

Wed Dec 11, 2019 1:38 pm

Need a device ID.

10414B48 and 10417180.

Same results.

No, actually these are brand new for the area and appeared after the frequency swap thingy. It used to be just 21.1 (HSN) on UHF 21, it changed to UHF 35 early this year, and then about a month and a half ago, we got 21.2 (QVC), 21.3 (HSN2), 21.4 (QVC2), 21.5 (QVC3), and 21.6 (DABL). For a while, I ...

Not sure what you are asking. The channels I listed above are the virtual numbers... physically they are on UHF 35.

I have an interesting one. I have 4th gen connects, so I can select favorites and "disable" channels. I also have a group of fairly new channels for this area; 21.2, 21.3, 21.4, 21.5, and 21.6. The interesting thing is, guide data availability for those channels can be made available/unavailable dep...

Added series-id tag (non-standard) and star-rating tag (standard). Nick I was actually grabbing star ratings from the movie description since it is embedded at the end of it. Added my code to get it from the new star-rating element and it fell flat. Star-rating isn't compliant to the dtd... should ...

Actually, it works great... both as a stand-alone and as an addition to EPG123. Here is a comparison of current capabilities: http://epg123.garyan2.net/downloads/guideComparison.png At the moment, the 2-week HDHR2MXF cannot identify sporting events but hopefully that will happen soon if SiliconDust ...

I was creating schema from the XMLTV DTD, which states: Each channel has one id attribute, which must be unique Which is why I opted to include all channel numbers a station was broadcast on in the <display-name> elements of a single <channel> for EPG123... it was my compromise on file size and com...

There's been a little discussion on this already. I must say, I am fundamentally against creating unique IDs for each channel and instead use the unique ID for the station assigned to the channel. This makes the XMLTV file more efficient for simply not repeating the same schedule 2, 3, or even 4 tim...

I'm basically in the same situation. My CW station is almost exactly 180 degrees from all the other stations.

I use the Lava Omnipro HD-8008. Works very well... the 360 coverage isn't perfectly symmetric, but it does a good job and is VHF as well as UHF.

I do have an old document from TMS laying out the schema for their XTVD documents. It has a slew of genres/categories in it for reference. I'm sure over the years some new ones have been added, but it will probably give you a 90% answer. If you're not aware, TMS was bought/merged/whatever with Grace...

Just to add this here for those looking at the XMLTV file and seeing the dd_progid for the first time. The pieces of the dd_progid mean something. The prefixes are “MV” for movies, “SH” for shows, “EP” for episodes, and “SP” for sports. I have never seen dd_progid defined for the XMLTV, but it has a...

@nickk I only have 2 remaining requests. 1) can you include the entityType and subType values from Gracenote in the categories. This way I can properly identify sporting events. 2) related to above is a Live indicator. Though not part of the DTD, it has become somewhat accepted to include <live /> t...

Example (of what you service may need to return, one set of tuner numbers per group): <channel id="US16604.hdhomerun.com"> <display-name>JTV</display-name> <display-name>1037 JTV</display-name> <display-name>1037</display-name> <icon src="https://img.hdhomerun.com/channels/US16604.png" width="360" ...