Tvheadend

Post path in github
https://github.com/tvheadend/tvheadend/pull/new/master

saen acro wrote:

Post path in github
https://github.com/tvheadend/tvheadend/pull/new/master

This patch should not be commited to mainstream, it's for troubleshooting only (to understand some extra lines in my logfile).

I see it has been a year since this issue has been opened. I wanted to add that this problem is somewhat important for anybody using Oscam via newcamd and Irdeto card with Tvheadend. I had the same problem with same provider in Netherlands. I had to reverse the commit and then build Tvheadend, otherwise my smartcard was not updating and all of the entitlements expired. I am assuming anybody using Ziggo with Oscam and Tvheadend since the commit will have this problem and will not be able to update their card.

I just wanted to reply to this issue to raise the awareness.

No such problems when using tvh with oscam and Ziggo (with local cards) using dvbapi.
Why do some people prefer newcamd or cccam over dvbapi?
Is not dvbapi the preferred interface?

Since I do know know or understand how updates to smartcards are done, I do now know how newcamd or dvbapi work. I set up the system by following workshop made by hardware.info website which they posted in 2015 (specific instructions for Ziggo, Tvheadend, and Oscam). Per those directions newcamd was used for descrambling and updating the smartcard together with tvheadend. So using newcamd is essential for me.

Can you explain how to set up descrambling and updates to smartcard using dvbapi and tvheadend? Can you point me to a web site? Is using dvbapi better/faster/more efficient?

Hmm, this site is for tracking bugs.
The forum would be a better place for your request.

I was merely trying to point out that there is workaround for something that might indeed be a bug.

For my reference: #5048

The change in commit 25dfdb64f3005a47823db320a77a4bf964ceb3b1 is that the provider ID is used instead shared address. Try to print the ra structure (ra->sa and ra->provid).

It's very easy to misconfigure oscam. It happened to me.
The dvbapi user in oscam.conf did not match a user in oscam.user.
And it's the user in oscam.user that needs to have au=1.

As a result, EMM updates were not being sent to my cards, even though everything else just worked.

I have the same issue. It used to work without issues. With newcamd I did not get any EMM at all. With DVBAPI the global and unique ones get written and the shared ones skipped somehow.