jasonl wrote: ↑Tue Mar 16, 2021 6:37 pm Your cable provider apparently does not send channel numbers, so it won't work.

What methods are available to a cable provider to send guide name and guide number? Which methods does an HDHR respect?

I've bantered elsewhere that a deterministically generated guide numbers would enable OP and I's use case. When proper virtual channel numbers are unavailable, It would be great to fall back to a calculated guide number that is consistent and unique. Thought exercise: -> "5" - start the value with ...

Your cable provider apparently does not send channel numbers, so it won't work. Newer versions that have the channel scan function built in (EXPAND/CONNECT models) will generate fake channel numbers if the provider is not sending any, so they will work in the app. This turns out to be both a blessi...

For sure! That will work and we can come up with a hundred other ways of slicing this apple. I'd just preferred a more explicit result. When requesting ?transcode=mobile I'd much prefer a guarantee that I'm getting a transcoded stream up to 720 or nothing at all. I can accomplish this by first check...

I understand the point, this seemed like a simple/easy ask to introduce into all non-transcoding models. When I made the request I didn't understand that the EXTEND product was defunct. My hope was to have a single test suite for all product lines. It would sure make it easy to have a single test pl...

signcarver wrote: ↑Thu May 28, 2020 5:04 pm transcode is simply ignored

That is the current behavior.

nickk wrote: ↑Thu May 28, 2020 3:19 pmcan also use UPnP to discover tuners

Thanks for the pointer. Specifically, is the discovery method used the Simple Service Discovery Protocol (SSDP)?

Regarding (un)official methods, would you like me to avoid using the hosted API?

Please consider this minor request for increased consistency.

The EXTEND models appropriately issue an the 802 Unknown Transcode Profile error when the
?transcode parameter is used incorrectly. It’d be great if all other models always issued the 802 error when a transcode is requested.

Which device discovery methods are available to find HDHomeRun on the network?

I’ve found:
o http://ipv4-api.hdhomerun.com/discover JSON external API
o mDNS
— hdhomerun.local
— hdhr-xxxxxxxx.local (where xxxxxxxx is the device id)
— xxxxxxxx.local where xxxxxxxx is the device id
o others?

mski wrote: ↑Thu May 14, 2020 7:40 am I assume this "does the right thing" and updates the channel list

jasonl wrote: ↑Thu May 14, 2020 7:47 pm hdhomerun_config scan doesn't update information stored on the device

Thank you! This is an important tidbit of information.

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. ~/libhdhomeru...

I found some official documentation: https://info.hdhomerun.com/info/http_api https://www.silicondust.com/hdhomerun/hdhomerun_http_development.pdf https://github.com/Silicondust/documentation/wiki Found an end point to favorite and hide channels. curl -v -X POST http://hdhomerun.local/lineup.post?fa...

Hi, All - I'm looking to automate a bit around channel scanning. I've discovered the obvious end points: 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...