Bug #2745
No access to channel at autostart
0%
Description
Setup: Openelec 5.0.6, Tvheadend addon 3.9.2496
Observation: LiveTV is set to start automatically with the last viewed channel after boot. Sometimes the channel does not start. "No access" message appears on the screen.
Recovery: Select any other channel then switch back.
Frequency: 2-4 of 10
The attached service-log shows that no input source is available for "Discovery ID" channel. Last notice at 17:36:30.000.
At 17:36:31.849 another channel is selected.
At 17:36:36.415 "Discovery ID" channel selected again without any problem.
An additional comment that "No access" message appears in completely different cases. When no appropriate card is present for descrambling, when the DVB service is disabled for any reason and also in this case. I think these cases should result different messages to be distinguishable by user.
Files
History
Updated by C vH over 9 years ago
Updated by You could try a more recent version of TvH for OE 5 -> http://goo.gl/833OO2
/addons/tvheadend/3.9.2656/*.zip
Updated by Akos Sz over 9 years ago
Updated by I did not know that you published more recent TVH addons as well.
The latest one has been installed. Test is ongoing.
Updated by Akos Sz over 9 years ago
The problem is still present with TVH 3.9.2662 and Openelec 5.0.7.
It is strange that a second client can subscribe to the same channel which is permanently not accessible for the first one.
See screenshot.
Updated by Jaroslav Kysela over 9 years ago
Updated by 
This does not look good.
capmt: Oscam DVBAPI2 tcp: Removing CAPMT Server from service "Discovery ID" on adapter 0
Could you provide output for '--debug all'. Ideally, it would be nice to compile tvh with --enable-trace and provide output for '--debug all --trace service,subscription".
Updated by Akos Sz over 9 years ago
Does it work if the arguments line in the start script is changed like this:
TVHEADEND_ARG="-B -C -u root -g video -c $ADDON_HOME --debug all"
Updated by Akos Sz almost 9 years ago
The problem has not been seen for a long time after upgrading the components. The issue can be closed.