I have to admit I have no idea what this new interface is supposed to do? It's nice looking and all, but usually I just want to watch (and typically delete) programs we've recorded. If we are far behind on a program, there is a great deal of clicks/scrolling involved to get to the earliest one. What ...

Nick, there no longer seems to be an attribute that contains the HDHomeRun Series ID for movies anymore:

<programme start="20230318210000 +0000" stop="20230318230000 +0000" channel="US105723.hdhomerun.com">
<title>The Last Cowboy</title>
<desc lang="en">A young woman (Jennie Garth) and her ...

I'm seeing no new XMLTV guide data for the last six days - the downloaded XML file is empty (0 bytes). I'm using a bash script that downloads the XML file every day. My subscription is still valid (#609046). The HDHomeRun app (Mac) is showing guide data two weeks out. I've checked the device auth ...

Didn't mean to tweak you here; I was just trying to point out that the XMLTV specification is rather weak in nature and SD adheres to it just fine. One might argue that it would be better for the data consumer to assume that a lack of a <new> tag in the data can be meant to assume <previously-shown ...

Personally, I also see nothing wrong with the SD XMLTV data here given the provided sample. The XMLTV specification is not extremely strict and providers have a lot of wiggle room as to how they implement/deliver the data. To my eyes, I agree that this a problem that Plex and/or Emby need to deal ...

Did you download and install the v5 OS HDHomeRun NAS package afterwards? I literally just finished this upgrade (EX 4100), and that was the only manual action I needed to take; everything else was quite seamless here.

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 ...

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 ...

It is handled as a set so I think the category output is in alphabetical order.

I might be able to add an attribute - let me check...

Nick


They appear to be in genre priority, from least to most specific (generally). garyan2 linked me to and old TMS document (also found at another site), the ...

Added progType to category list. This give you Sports event, Series, etc.


This one dorked me up a little, will the second <category> element now always be the TMS-style genre string? These types of things are my main problem with XMLTV, too many multi-valued child elements without attributes to ...

nickk wrote: Wed Dec 11, 2019 5:46 pm Added lcn element to indicate the virtual channel number.

Nick

Thanks! Adapted. Saves iterating the list of <display-name> elements. Every millisecond counts

It really didn't turn out to be a problem for me. I just had to add a level of indirection to go through the channels to get to the listings instead of iterating the listings directly. No big deal in the end!

I agree in principal. It's just a different mindset than before and can be worked with easily enough. Instead of having programming relating back to a single channel it can now relate back to multiple channels. If the data is stored (even if temporarily) and can be referenced it wouldn't be ...

First, thank you for adding <series-id> for Movies :)

I've run into a problem with the <channel> elements ... There is a duplicate id attribute in the data retrieved for my authorization codes. I see "US86442.hdhomerun.com" twice, which will ultimately associate all listings for the second channel ...

Added series-id tag (non-standard) and star-rating tag (standard).

Nick


Thank you Nick!

It looks like Movies (MV) aren't being assigned a <series-id> tag, is that expected? It appears on the surface this can be generated by simply removing the "." from the dd_progid value for these items ...