New Channels Tags Starting with zero

Ian Jones · 2024-07-06T09:17:00+00:00

I have a number of IPTV networks with approx 10,000 channels. When a new channel tag is created (or channel group), it appears in tvheadend with a default "...

DeltaMikeCharlie

Ian Jones Sorry I means the full command line syntax if the specific tag has been identified?

Did you read the examples in the API documentation?

https://docs.tvheadend.org/documentation/development/json-api/examples

Ian Jones

I did but I couldn’t see a way of writing the sort order to the tag unless I’ve missed something. There is a channel category. Maybe I’m not competent enough to work it out. Sorry

DeltaMikeCharlie

Find the UUID of the Channel Tag that you want to modify.

http://[TVH_IP]:9981/api/channeltag/grid

You can even fine-tune the query to only return Channel Tags that have a sort index of zero.

http://[TVH_IP]:9981/api/channeltag/grid?filter=[{"field":"index","type":"numeric","value":"0"}]

Update the Channel Tag object with the index value that you want.

http://[TVH_IP]:9981/api/idnode/save?node={"uuid":"[INSERT_UUID_HERE]", "index":"[INSERT_SORT_INDEX_HERE]"}

Chris G

Just wanted to let you guys know that my issue appears to be fixed after updating to (the yet to be officially released) OSMC/Kodi 21.
Seems like it was a Kodi issue and 21 fixed it.

DeltaMikeCharlie

Chris G Seems like it was a Kodi issue and 21 fixed it.

Thanks for letting us know.

Ian Jones

DeltaMikeCharlie I've upgraded but need to wait until channel changes so I can see what happens

Ian Jones

I can't get the filtering to work and also how would you add multiple contains, i.e. enabled and index 0? Sorry!

DeltaMikeCharlie

Ian Jones how would you add multiple contains

I don't know, I would have to work it out by trial and error, as I did with the last example that I provided you.

Have a look at the API documentation. It seems that the filter is a JSON array, perhaps you could add a second filter definition to that array.

https://docs.tvheadend.org/documentation/development/json-api/api-description/common-parameters

Ian Jones

Hi Mike - Kind of sorted it. The syntax is a bit fiddly but here is one example with a filter and a sort:

http://<UID>:<PWD>@<TVH-IP?:9981/api/channeltag/grid?filter=[{"field":"index","type":"numeric","value":"100","comparison": "LT"}]&start=2&limit=5&sort=index&dir=desc

The issue was that the API does not show items from the GUI that are not ENABLED. Not sure if there is any way of changing this. Once an item is disabled, then the API will not show it. So if I disable something I will not be able to re-enable it!

davep

Untested, but from the API docs:

A TVH user can only see via the API those channels which have been enabled and to which access has been allowed. However a user with ADMIN privilege can use the parameter all=1 to see details of every channel, channeltag and category even if they do not have access to them.

Ian Jones

So I can now find the entries, but I cannot update them!!!!

Get all channel with sort index 0.....
http:/<TVH_IP>:9981/api/channeltag/grid?filter=[{field:index,type:numeric,value:0,comparison:%20LT}]sort=index&dir=desc&all=1

Update sort index - not working...can anyone help please!!!!
http://[TVH_IP]:9981/api/idnode/save?node={"uuid":"[INSERT_UUID_HERE]", "index":"

example trying to set 0db0a382618ef6707ff74d63eaab3a58 to sort index 0.....
http://tvh.lan:9981/api/idnode/save?node={"uuid":"0db0a382618ef6707ff74d63eaab3a58", "index”:”0”}[INSERT_SORT_INDEX_HERE]"}

Ian Jones

Ian Jones Can anyone help with the syntax to update a UUID with a new sort index?

davep

Ian Jones Hmmm... I've tried to edit a channel tag and every attempt has ended in a 400 error. Unfortunately the built-in debugging tools don't cover the api functions so it would be necessary to trace through a debug build to find out where the failure is occurring.

DeltaMikeCharlie

davep I've tried to edit a channel tag and every attempt has ended in a 400 error.

Ian Jones I had a similar issue.

I wonder if it is a permissions issue. Does the API call work if you launch TVH with --noacl?

Ian Jones

I had a similar issue. If anyone can help it would be really appreciated. Out of curiosity using a single line in the chrome browser what was your API call?

davep

Got it.

There is an old post https://tvheadend.org/d/7176-angularjs-webinterface/79 which suggests that the api call must be made as "x-www-form-urlencoded" I'm not certain that is correct (and the fact that I didn't update the api docs at the time suggests that I found otherwise), however checking the format of my api calls on the wire using tcpdump showed that they were being corrupted by the shell.

What did work was:
curl --data-urlencode node=\{\"uuid\":\"0f812d7beab8713776f696029bcaaf10\",\"index\":1\} "http://user:pass@my.ip.addr:9981/api/idnode/save"
On the wire this looks like:

POST /api/idnode/save HTTP/1.1
Host: my.ip.addr:9981
Authorization: Basic redacted==
User-Agent: curl/8.9.0
Accept: */*
Content-Length: 80
Content-Type: application/x-www-form-urlencoded
node=%7B%22uuid%22%3A%220f812d7beab8713776f696029bcaaf10%22%2C%22index%22%3A1%7D

Alternatively using GET:
curl "http://user:pass@my.ip.addr:9981/api/idnode/save?node=\{\"uuid\":\"79980f0430f92ff5f11ab55cb8055ca5\",\"index\":1\}"

Ian Jones

davep Could you advise how to url encode the query and include the "sort=index&dir=desc&all=1"

So far I have it working like this but it ignores the sort, dir and all (which helps me include disabled channel tags).I'm not sure where to put those options using this format

`search='.entries[].uuid'
inc_disabled='1'

LIST=$(curl -s --data-urlencode filter=[{\"field\":\"index\",\"type\":\"numeric\",\"value\":\"${lookupsortindex}\",\"comparison\":\"EQ\"}]\&start=0\&sort=index\&dir=desc\&all=\"${inc_disabled}\" "http://$uid:$pwd@$host:$port/api/channeltag/grid" | jq -r "$search")`

Ian Jones

So I have it almost cracked!!!! ALMOST

#List zero value indices
curl -s --data-urlencode 'filter=[{"field":"index","type":"numeric","value":"0","comparison": "EQ"}]&start=0&sort=index&dir=desc&all=1' "http://UID:PWD@IP:9981/api/channeltag/grid"

#Update specific index
curl --data-urlencode 'node={"uuid":"a85d1ac0f895541e3686fc6a02fa234b","index":1}' "http://UID:PWD@IP:9981/api/idnode/save"

BUT....I need to run this on the docker host and when I do it access is denied

curl: (7) Failed to connect to <IP> port 9981: Connection refused

It works fine when I run it from a remote host. Is this being blocked by the webUI user even though it is set to 0.0.0.0/0 or is it docker blocking ports on the container from the local host. The container is running in a different subnet

docker-compose.yml (extracts)
tvheadend: image: lscr.io/linuxserver/tvheadend:latest container_name: tvheadend environment: - PUID=1000 - PGID=1000 - TZ=Europe/London - RUN_OPTS= #- RUN_OPTS=--bindaddress 192.168.5.201 --http_port 192.168.5.201:9981 --htsp_port 192.168.5.201:9982 #- RUN_OPTS=--http_port 9983 --htsp_port 9984 volumes: - /mnt/usbhdd/pvr/config:/config - /mnt/usbhdd/pvr/recording:/recording - /mnt/usbhdd/pvr/m3u:/m3u - /mnt/usbhdd/pvr/timeshift:/timeshift - /mnt/usbhdd/pvr/scripts:/scripts '# ports: '# - 9981:9981 '# - 9982:9982 '# - 192.168.5.201:9981:9981 '# - 192.168.5.201:9982:9982 networks: lanvpn: ipv4_address: "192.168.30.201" devices: - /dev/dvb:/dev/dvb privileged: true restart: unless-stopped

networks: default: ipam: config: - subnet: 192.168.0.0/24 lanvpn: driver: macvlan driver_opts: parent: eth0.300 ipam: config: - subnet: 192.168.30.0/24 gateway: 192.168.30.1

Im trying to access TV on 192.168.30.1 which is a local network on VLAN 300 (ports on the config are currenlly commented out

Ian Jones

I think the issue is more of a docker issue. My docker container sits on a different subnet and VLAN on IP 192.168.30.201 but the host sits on 192.168.5.201. I need to be able to connect to the container from the host when running a script, but for some reason I cannot. If I try to connect to the container from a normal client on the LAN, say from 192.168.5.100, then it connects fine.

I think the issue is that its is trying route via the local docker private network of 192.168.130.130 instead of via the gateway that connects the two networks.

root@pvr:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default router.lan 0.0.0.0 UG 202 0 0 eth0
default FriendlyWRT.lan 0.0.0.0 UG 484 0 0 eth0.300
link-local 0.0.0.0 255.255.0.0 U 312 0 0 veth87af8d1
link-local 0.0.0.0 255.255.0.0 U 316 0 0 veth5291032
link-local 0.0.0.0 255.255.0.0 U 318 0 0 vethe788551
link-local 0.0.0.0 255.255.0.0 U 321 0 0 veth6a07a3a
link-local 0.0.0.0 255.255.0.0 U 323 0 0 vethd79c34f
link-local 0.0.0.0 255.255.0.0 U 325 0 0 vethfd76b61
link-local 0.0.0.0 255.255.0.0 U 327 0 0 veth792529a
link-local 0.0.0.0 255.255.0.0 U 483 0 0 vethcefe2ce
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 br-2add0ff982d3
192.168.5.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0
192.168.30.0 0.0.0.0 255.255.255.0 U 484 0 0 eth0.300

Does this make sense as when I try to ping the correct IP address of 192.168.30.201, I get the following:
root@pvr:~# ping tvh.lan
PING tvh.lan (192.168.30.201) 56(84) bytes of data.
From tvhdocker.lan (192.168.30.130) icmp_seq=1 Destination Host Unreachable
From tvhdocker.lan (192.168.30.130) icmp_seq=2 Destination Host Unreachable
From tvhdocker.lan (192.168.30.130) icmp_seq=3 Destination Host Unreachable

root@pvr:~# traceroute tvh.lan
traceroute to tvh.lan (192.168.30.201), 64 hops max
1 192.168.30.130 3068.415ms !H 3071.839ms !H 3071.876ms !H

Ian Jones

Adding a static route for one host works, but is that the correct thing to do? And will the route persist on reboot?

ip route add 192.168.30.201 via 192.168.5.1 dev eth0

davep

Ian Jones If you're using curl and POST, the data parameters are specified separately:

LIST=$(curl -s --data-urlencode filter=[{\"field\":\"index\",\"type\":\"numeric\",\"value\":\"${lookupsortindex}\",\"comparison\":\"EQ\"}] -d start=0 -d sort=index -d dir=desc -d all=\"${inc_disabled}\" "http://$uid:$pwd@$host:$port/api/channeltag/grid" | jq -r "$search")`

See man curl.

« Previous Page