Tvheadend

You can automatically add channels with bouquets.

C K wrote:

You can automatically add channels with bouquets.

I was looking for a way to suggest a feature whereby you can access the tvheadend backend from the kodi interface. There aren't any bouquets built for US ATSC (and to be honest, our channel system is in transition so it may not be that helpful).

TVs and DVRs in the US have a simple system that rescans the frequencies (muxes), adds the found channels (services) and pulls in their PSIP data for a guide. I'm trying to build a simplified system like this us the tvheadend backend - but to be simple enough for the US consumer, it will need to be able to be run from the kodi frontend. Similar to the VDR configure program (addon) that was built.

I guess I should put this in the forums, I thought there was a system for feature requests through the issues system - but I was wrong.

BTW - I appreciate all the hard work that goes into this software and thank those of you that are continually updating the code!

Jaroslav, why did you reject this?

it would be good to be able to rescan channels and add/delete channels once you have a working network/mux setup.

For pvr.hts being able to do this, tvheadend's htsp api needs to be extended. I guess, this is the actual tvheadend feature request the submitter wants to make. pvr.hts could then pick up and support the new tvh htsp api.

The HTSP protocol in recent TVH have "api" method which redirects the request to HTTP API. So the HTSP clients can do everything like HTTP clients (webui) including such configuration and they can also use the wizard.

Jaroslav Kysela wrote:

The HTSP protocol in recent TVH have "api" method which redirects the request to HTTP API. So the HTSP clients can do everything like HTTP clients (webui) including such configuration and they can also use the wizard.

That is great to hear. While I am new to coding...this is exactly the type of thing I would like to dig into. I'll take a look - as I am sure there are plenty of other items on most of the team's plate!!

Jay M wrote:

Jaroslav Kysela wrote:

The HTSP protocol in recent TVH have "api" method which redirects the request to HTTP API. So the HTSP clients can do everything like HTTP clients (webui) including such configuration and they can also use the wizard.

That is great to hear. While I am new to coding...this is exactly the type of thing I would like to dig into. I'll take a look - as I am sure there are plenty of other items on most of the team's plate!!

i'm extending the python htsp client at the moment (where every entity is an python object) that make use of some api calls.

>>> client = HTSPClient('localhost')
>>> client.connect()
>>> client.authenticate('user', 'pass')
>>> networks = client.get_networks()
>>> networks
[<TVHNetwork Astra 19.2E >, <TVHNetwork Hotbird 13.0E >, ]
>>> astra = networks[0]
>>> astra.force_scan()

could be a possible six-liner