Robert,
again thank you for taking care of my inquire - I do appreciate it!
Reading your feedback I understood that the TVH file structures are similar (if not the same).
My "muxes" are also not a plain text in 4.0.x
I will change just few channel files from .hts/tvheadend/channel/config/ and see if the system does what I want.
This is a good hint, pointing to the JSON format. -I'm tending to create a python script (with a few lines) to do the job, as soon as the test will be successful.- [edit:] jq works perfectly and is available out of the box i will give it try.
Maybe someone can put more light to the dvb_eit_enable field successor.
best regards
Beny
Evening's update:
I found the service config files to be modified. The files are stored in: ~/.hts/tvheadend/input/dvb/networks/<network-ID>/muxes/<transponders>/
The script has to go transponder by transponder folder and modify all files the sub-folders.
In each file there are to fields:
"enabled" to be set to false in order to disable the service and
"dvb_ignore_eit" to be set to true in order to ignore epg data.
To disable the channels I used following bash script:
#!/bin/sh
for file in ls -1 -r ~/.hts/tvheadend/channel/config/* ; do
#[[ ! -e $file ]] && continue
echo "$file"
cat "$file" | jq '.enabled |= false | .epgauto |= false' | sponge "$file"
done
The script has to be started from the hts user (relative path ~ to chanel files)