Cable Channel Scan parameters

[mski]

Hi, All -

I'm looking to automate a bit around channel scanning. I've discovered the obvious end points:

Code: Select all

curl -v -X POST http://hdhomerun.local/lineup.post?scan=start
curl -v -X POST http://hdhomerun.local/lineup.post?scan=abort
curl -v -X GET http://hdhomerun.local/lineup_status.json
curl -v -X GET http://hdhomerun.local/lineup.json

I've found some parameters in github such as lineup.json?show=found, lineup.json?show=all, and lineup.json?tuning.

Is there documentation about these end points and their parameters?

Is the scan configurable? I'd like to only use a single tuner and leave the additional tuners available for use.

Thanks all!

[mski]

I found some official documentation:
https://info.hdhomerun.com/info/http_api
https://www.silicondust.com/hdhomerun/h ... opment.pdf
https://github.com/Silicondust/documentation/wiki


Found an end point to favorite and hide channels.

Code: Select all

curl -v -X POST http://hdhomerun.local/lineup.post?favorite=+3
curl -v -X POST http://hdhomerun.local/lineup.post?favorite=x3
curl -v -X POST http://hdhomerun.local/lineup.post?favorite=-3

[mski]

Is the scan configurable? I'd like to only use a single tuner and leave the additional tuners available for use.

I haven't tripped accross a HTTP endpoint that sets up server side single tunner scanning. As documented elsewhere, the thick configuration app supports per tuner scanning.

Code: Select all

~/libhdhomerun-master$ hdhomerun_config <id> scan <tuner>

I assume this "does the right thing" and updates the channel list for all tuners while used with a PRIME. I seem to recall some models had multiple inputs and per tuner multiple channel lists but haven't seen any documentation on that.

[NedS]

I'll have to check with our CTO, Nick, but I believe the command line tool is the only way to specify a specific tuner for scanning. I'll also see if we can update the info.hdhomerun.com page today to answer your other questions and also consolidate more of the documentation. I've been meaning to add something for the blacklist/favoriting, and a few other tricks that aren't currently properly documented, but now is as good of a time as any to get cracking on that.

[jasonl]

Single-tuner scanning doesn't exist, at least in a useful fashion for updating the website or xml/json data. The scan that updates the stored data on the device always uses all tuners, period. The hdhomerun_config scan doesn't update information stored on the device and is generally only useful for recording signal metrics and, excluding anything using a tuning adapter, which virtual channels are present on a given physical channel.

[mski]

I assume this "does the right thing" and updates the channel list

hdhomerun_config scan doesn't update information stored on the device

Thank you! This is an important tidbit of information.