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
http_api [2020/07/14 05:39] – nedshttp_api [2026/07/14 22:55] (current) – neds
Line 5: Line 5:
 The list of available channels can be queried using the following URLs: The list of available channels can be queried using the following URLs:
  
-     http://<device ip>/lineup.json +     http://hdhomerun.local/lineup.json 
-     http://<device ip>/lineup.xml+     http://hdhomerun.local/lineup.xml 
 +     http://hdhomerun.local/lineup.m3u 
 +\\ 
 +//**Note:** "hdhomerun.local" can also be replaced by the deviceID.local or the IP address of the HDHomeRun.// 
 +\\
 \\ \\
- 
 The following information is returned for each program: The following information is returned for each program:
   * "GuideNumber" (virtual channel number). For ATSC the number will be "n.n" format. For all other systems the number will be "n" format.   * "GuideNumber" (virtual channel number). For ATSC the number will be "n.n" format. For all other systems the number will be "n" format.
Line 65: Line 68:
   * Example channel 5 is RF 14, which is 473MHz and would be written as <code>http://192.168.0.100:5004/auto/ch473000000</code>   * Example channel 5 is RF 14, which is 473MHz and would be written as <code>http://192.168.0.100:5004/auto/ch473000000</code>
  
-If the channel has sub-channels, you can use the program number to specify the channel with a dash. For example, channel 5.3 might be -3 (program numbers are not always sequential or starting with 1), +  * If the channel has sub-channels, you can use the program number to specify the channel with a dash. For example, channel 5.3 might be -3 (program numbers are not always sequential or starting with 1), it would be written as, <code>http://192.168.0.100:5004/auto/ch473000000-3</code> 
 + 
 +</WRAP> 
 +====Specifying a tuner==== 
 +<WRAP indent> 
 + 
 +The "/auto/" portion of the URL will select the first available tuner. Replacing this with a tuner identifier will force use of a specific tuner. For example: 
 +  * tuner0 - the first tuner 
 +  * tuner1 - the second tuner 
 +  * tuner2 - the third tuner (if you have a 3 or 4 tuner model) 
 +  * tuner3 - the fourth tuner (if you have a 4 tuner model) 
 + 
 +The URL for using the second tuner might look like this: 
 + 
 +<code>http://192.168.0.100:5004/tuner1/v5.1</code>
  
 </WRAP> </WRAP>
Line 93: Line 110:
  
 </WRAP> </WRAP>
 +</WRAP>
 +=====Discover=====
 +<WRAP indent>
 +
 +<code>http://hdhomerun.local/discover.json</code>
 +
 +//**Note:** "hdhomerun.local" can also be replaced by the deviceID.local or the IP address of the HDHomeRun.//
 +
 +Basic information about the HDHomeRun unit can be accessed via this URL:
 +  * Network friendly name
 +  * Firmware version
 +  * Device ID
 +  * DeviceAuth (mainly used for [[:DVR]])
 +  * Base URL
 +  * Lineup URL
 +  * Tuner count
 +
 +Example:
 +
 +<code>{"FriendlyName":"HDHomeRun FLEX 4K","ModelNumber":"HDFX-4K","FirmwareName":"hdhomerun_dvr_atsc3","FirmwareVersion":"20260326","DeviceID":"10AFFFFF","DeviceAuth":"sfqnCjyZhgyqkBr2oFvclmWF","BaseURL":"http://hdhr-10afffff.local","LineupURL":"http://hdhr-10afffff.local/lineup.json","TunerCount":4}</code>
 </WRAP> </WRAP>
 =====Client requirements for live TV===== =====Client requirements for live TV=====
  • Last modified: 2020/07/14 05:39