Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
dvr:xmltv [2026/04/14 22:20] – [Example] nedsdvr:xmltv [2026/10/01 21:50] (current) – [Additional requirements] neds
Line 6: Line 6:
 </WRAP> </WRAP>
  
-<lead>14 day XMLTV guide data is available for HDHomeRun customers to use with third party apps. At least one HDHomeRun tuner and a paid [[:DVR:activation|HDHomeRun DVR guide subscription]] is required to use this API.</lead>+<lead>XMLTV guide data is available for HDHomeRun customers to use with third party apps.</lead> 
 + 
 +  * No account is required for access to 3 days of guide data. 
 + 
 +  * A paid [[:DVR:activation|HDHomeRun DVR guide subscription]] is required to access 14 days of guide data.
  
 ====API URL==== ====API URL====
Line 18: Line 22:
  
 ^ Parameter ^ Type ^ Description ^ ^ Parameter ^ Type ^ Description ^
-| DeviceAuth | string | Concatenation of the DeviceAuth strings from all HDHomeRun tuners. |+| DeviceAuth | string | Concatenation of the DeviceAuth strings from all HDHomeRun tuners. This can be found from http://hdhomerun.local/discover.json and changes every 8 hours. |
  
 OR OR
Line 30: Line 34:
 <WRAP indent> <WRAP indent>
  
-  * The HDHomeRun device(s) must be associated with a paid HDHomeRun DVR account to access XMLTV guide data. 
   * The HTTP client must accept gzip encoding.   * The HTTP client must accept gzip encoding.
   * The DeviceAuth changes regularly and is valid for 16-24 hours. If using the DeviceAuth access approach the DeviceAuth must be read from the HDHomeRun tuner(s) to get the latest value each time this API is invoked.   * The DeviceAuth changes regularly and is valid for 16-24 hours. If using the DeviceAuth access approach the DeviceAuth must be read from the HDHomeRun tuner(s) to get the latest value each time this API is invoked.
  • Last modified: 2026/04/14 22:20