hostname:9981 :: ref_01 :: ref_02 :: ref_03
Hardware (capture card):
lspci
or dmesg | grep dvb
to check for presence/recognition of cardFedora:
dnf install tvheadend
openSUSE:
zypper in tvheadend
Updating /etc/sysconfig/tvheadend …
==> IMPORTANT: Post configuration tasks;
==> 1. Start the tvheadend service (to create home directory).
==> 2. Run tvheadend_super to set default username and password.
==> 3. Restart tvheadend service.
==>
==>
==> All further configuration is maintained through the web interface:
==>
==> http://localhost:9981/
==>
Grant tcp access to tvheadend ports
firewall-cmd --permanent --add-port=9981/tcp
firewall-cmd --permanent --add-port=9982/tcp
firewall-cmd --reload
systemctl enable tvheadend
systemctl restart tvheadend
/etc/sysconfig/tvheadend:
#Configuration file for the tvheadend service.
MALLOC_ARENA_MAX=4
OPTIONS="-c /var/lib/tvheadend/config -u tvheadend -g video -6 -C --http_port 9981 --htsp_port 9982"
Run as daemon, and see realtime logging:
systemctl stop tvheadend
tvheadend -c /var/lib/tvheadend/config -u tvheadend -g video -6 -C --http_port 9981 --htsp_port 9982
systemctl restart tvheadend
!! Must stop the service before changing any config files !!
usermod -aG smbgrp tvheadend
#gives tvheadend access to alt storage pathusermod -aG video <username>
#add tvheadend, cyril, & kodi to video grouptvheadend looks at a grab_file to determine where to get its epg data.
The grab_file may:
looking at it another way:
EPG data from the interwebs is compiled into a xmltv.xml file, which is referenced by the grab_file that tvheadend is pointed to.
installation
tvheadend
Following the recommended path in the wiki, I did initial setup through kodi (password is in the clear!), tells me access denied.
found github issue instructing to run http://YOUR.IP.ADDRESS:9981/api/mpegts/service/grid
this request was denied until I used a tvheadend account with administrative privilege.
On the kodi device, a successful setup&scan generates settings & configuration files in a userdata folder under:
~/.kodi/userdata/../addon_data
or
~/.var/app/tv.kodi.Kodi/data/userdata/addon_data
Migrating the setup to be managed by a (headless) tvheadend backend/server involves two steps:
<setting id="tvhurl">dubserv</setting>
in settings.xml, be sure that dubserv
is defined in /etc/hosts, and that the appropriate network range is configured for the kodi user via the tvheadend web interface.ln -s
(or copy) to /usr/bin/. tv_grab_zap2epg
Systemctl restart tvheadend
#make tvheadend notice grabber additions/changesssh -A -t kodi@kodibox scp -r /home/kodi/.kodi/addons/script.module.zap2epg cyril@192.168.0.13:/home/tvheadend/
ssh -A -t kodi@kodibox scp -r /home/kodi/.kodi/userdata/profiles/kids/addon_data/script.module.zap2epg/* cyril@192.168.0.13:/home/tvheadend/script.module.zap2epg/
userdata/profiles/kids/addon_data/script.module.zap2epg/*
Seems nice
First, from web-interface:
configuration > channel/epg > epg grabber modules
on left side, lots of red circles, look for:
internal: XMLTV: Schedules Direct JSON API
present? then check the parameters for the grab_file path, grab some terminal:
sudo -u tvheadend /path/to/tv_grab_zz_sdjson –configure
follow the prompts, then restart tvheadend
systemctl restart tvheadend
go back to the web-interface > modules menu, disable the OTA module, enable the appropriate schedules direct JSON, [save], profit.
try the %C thing :: ref_01 :: ref_02 :: ref_03
works:
Configuration > General > Base
great source of logo png (& svg) images:
https://logos.fandom.com/wiki/