Bug #4931

Ziggo: No epg data at all with latest master head

Added by bas t 8 months ago. Updated 8 months ago.

Status:FixedStart date:2018-02-10
Priority:NormalDue date:
Assignee:Adam Sutton% Done:

0%

Category:EPG
Target version:-
Found in version:4.3-1049~g088be1abe Affected Versions:

Description

With newest master head (4.3-1049~g088be1abe) I don't get epg data anymore.
Version 4.3-1022~g7710304cd still works as expected.

I did --trace eit,epg but no traces get logged. I do get this: ERROR]:config: unkown subsystem 'eit' But not a single line with [ TRACE]:epg:
This ERROR]:config: unkown subsystem 'eit' entry is in the tracelog of 4.3-1022~g7710304cd too, but then lots of trace entries for epg appear and the epg is filled correctly

Please let me know if I can do anything helpful.

tvheadend4.3-1049.log - master head, not working (30.8 KB) bas t, 2018-02-10 12:48

tvheadend4.3-1022.log - working version (2.83 MB) bas t, 2018-02-10 12:48

tvheadend.log (72.6 KB) bas t, 2018-02-10 18:52

tvheadend-tbl-eit-tbl-base.log (53.4 MB) bas t, 2018-02-11 08:22

new-trace.log (44.7 MB) bas t, 2018-02-11 18:44

nit.png (13.2 KB) Pim Zandbergen, 2018-02-12 20:52

Associated revisions

Revision 1d2374ae
Added by Jaroslav Kysela 8 months ago

dvb psi: add nit network id filter for EIT NIT callback (Ziggo), issue #4931

History

#1 Updated by bas t 8 months ago

Upload the logs.

#2 Updated by Andy Gardner 8 months ago

My EPG has also been empty for the last few days after I did a tvheadend upgrade.

I notice there are new EIT grabber modules for Freeview NZ.

In the repository /data/conf/epggrab/eit/config file:

##

"nz_freeview2": {
"name": {
"eng": "New Zealand: Freeview Local"
},
"nit": {
"Freeview ": {
"onid": 8746,
"nbid": [ 13313, 13314, 13315, 13316 ],
"tsid": [ 26, 27, 28, 31, 32 ]
}
},
"prio": 5,
"conv": "huffman",
"hacks": {
"svc-net-lookup": 1
}
},

"nz_freeview1": {
"name": {
"eng": "New Zealand: Freeview Base"
},
"nit": {
"Freeview ": {
"onid": 8746,
"nbid": [ 13313, 13314, 13315, 13316 ]
}
},
"prio": 1,
"conv": "huffman"
},

##

The TSID's showing in my MUX list for Christchurch NZ are 28 32 33 34 and 35

So those are different from the ones showing in that config file.

#3 Updated by saen acro 8 months ago

What Input you use?
it work for me in DVB-T-C-S

#4 Updated by Hanspeter Müller 8 months ago

It's not limited to NZ, all EIT seems to be affected (xmltv works), i've reverted to 4.3-1006 where it still works...

#5 Updated by bas t 8 months ago

@sean acro: Lucky you.
It does not work for me anymore.
BTW: I'm on cable (DVB-C) in the Netherlands with Ziggo as a provider.

#6 Updated by bas t 8 months ago

I did a bisect and I think I've found the offending commit:

6dcdd5dfa33e241ddc5e2a0821cf043417674152

The previous commit:

78f63ac18458e75147fc9680b7ae5dfa95d180d5

still works.

I'm not much of a coder so I don't know what part of the offending commit is to blame.

Cheers,
Tycho.

#7 Updated by Jaroslav Kysela 8 months ago

Show '--trace tbl-eit' .

#8 Updated by bas t 8 months ago

Will do. But tomorrow, as tvheadend is recording some shows atm and I don't want to interupt.
Cheers,
Tycho.

#9 Updated by bas t 8 months ago

So I had another look at what shows are recording atm. I decided that solving the issue is of greater importance to me.
Added --trace tbl-eit log.

#10 Updated by Jaroslav Kysela 8 months ago

Add 'tbl-base' to traces, too. (--trace tbl-eit,tbl-base)

#11 Updated by bas t 8 months ago

Here it is. It's huge.

#12 Updated by Jaroslav Kysela 8 months ago

It appears that the issue is in the base SI table code. Could you try latest? v4.3-1051-gade772d1f

#13 Updated by Alister Kunga 8 months ago

same problem no epg 4.3-1051 ~ gade772d

#14 Updated by bas t 8 months ago

@Jaroslav Kysela
What kind of trace log do you need to debug this some more?

#15 Updated by Jaroslav Kysela 8 months ago

Like the last one.

#16 Updated by bas t 8 months ago

Here you go..

#17 Updated by Jaroslav Kysela 8 months ago

It seems that there's another bug which ignores NIT table 0x40 - could you upload 30 seconds of MPEG-TS data? Use play URL from the mux grid as source for wget or curl.

#18 Updated by bas t 8 months ago

Does it matter witch version I use? I'm running 4.3-1029~g78f63ac18 right now.

Also, can't I just use kodi to record 30 secs of mpeg-ts data? I'm not sure what you mean by "Use play URL from the mux grid as source for wget or cur".

#19 Updated by bas t 8 months ago

Ah, got it.
But I get a 'error' while trying to upload the data

#20 Updated by bas t 8 months ago

Hi, I uploaded to wetransfer.com. Using a browser, you can get it at:

https://wetransfer.com/downloads/b697ad5682ed8c031d9495501b369b9220180211195555/d84c56

#21 Updated by Pim Zandbergen 8 months ago

Running HTS Tvheadend 4.3-1051~gade772d1f

EPG for DVB-S is fine (Astra 1, 2, Hotbird, Thor)
EPG for DVB-C is missing (Ziggo Den Haag)

#22 Updated by Pim Zandbergen 8 months ago

Note that both bas t and myself use Ziggo

#23 Updated by Pim Zandbergen 8 months ago

There's a nice online analyzer for Ziggo at http://www.dtvmonitor.com/nl/

#24 Updated by Jaroslav Kysela 8 months ago

It works here. Perhaps, you have set wrong 'Network ID' in the network settings. Reset this value to zero, or describe the reason, why you set this value.

#25 Updated by bas t 8 months ago

Setting a specific value is mandatory when you have Ziggo as a provider in the Netherlands.
Usually it is 5555 (I used this value up until today), but after some googling I found that in some cases 4444 has to be used. I first tested this value with 4.3-1029~g78f63ac18 to check that it works and it did.
But using 4.3-1051~gade772d1f, I still don't get any epg data.

I recorded another 30 secs, this time using 4.3-1051~gade772d1f, hoping it will shed some light on the matter.

https://wetransfer.com/downloads/5e96db7981d3433715ac74b65c6ea7d820180212094202/b6ce18

#26 Updated by Jaroslav Kysela 8 months ago

The right value is 0x600 or 1536 decimal.

2018-02-12 09:09:50.926 [  TRACE]:tbl-base: nit: pid 10 tableid 40 extraid 0000000000000600 len 923
2018-02-12 09:09:50.926 [  TRACE]:tbl-base: nit:  section 1 last 4 ver 4 (ver 255 st 0 incomp 1 comp 0)
2018-02-12 09:09:50.927 [  TRACE]:tbl-base: nit:  dtag 5F dlen 4
2018-02-12 09:09:50.927 [  TRACE]:tbl-base: nit:    private 00000602
2018-02-12 09:09:50.927 [  TRACE]:tbl-base: nit:  dtag D2 dlen 22
2018-02-12 09:09:50.927 [  DEBUG]:tbl-base: nit: network 0600 (1536) []

#27 Updated by Jaroslav Kysela 8 months ago

And grep shows that there are not other network ids, so you can set this filter to zero:

2018-02-12 09:09:50.927 [  DEBUG]:tbl-base: nit: network 0600 (1536) []
2018-02-12 09:09:51.963 [  DEBUG]:tbl-base: nit: network 0600 (1536) []
2018-02-12 09:09:53.034 [  DEBUG]:tbl-base: nit: network 0600 (1536) []
2018-02-12 09:09:54.071 [  DEBUG]:tbl-base: nit: network 0600 (1536) []
2018-02-12 09:09:54.780 [  DEBUG]:tbl-base: nit: network 0600 (1536) [Ziggo Network]
2018-02-12 09:09:55.750 [  DEBUG]:tbl-base: nit: network 0600 (1536) []

#28 Updated by bas t 8 months ago

Tested with value 0 and it works. Of course this violates all online documentation of Ziggo, but who cares, as long as it's working...
Thanks a million and cheers,
Tycho.

#29 Updated by bas t 8 months ago

Hmmmm...
I spoke too soon, most of it works, but there are quite a few channels that show some epg data, but mostly 'no information availabel'.
So there's more to it, it's not fixed yet. Maybe this strange network id settings from Ziggo are required after all.

#30 Updated by bas t 8 months ago

Setting the network id to 0 also messed up my muxes, I have to regenerate them right now, so 0 is wrong.

#31 Updated by Richard K 8 months ago

I had the same EPG problem on the Ziggo network.
Always used Network ID 4444, but now I needed to change it to 1536 to start receiving EPG data again.
Not sure if this is caused by a change in the Ziggo network or if something changed in Tvheadend (upgraded this weekend to Build: 4.3-1049)

#32 Updated by bas t 8 months ago

I'll try that setting as soon as I regenerated all muxes and services. Thanks for the heads up.

#33 Updated by bas t 8 months ago

Still no luck, it's even worse than setting it to 0.
Now I know that Ziggo uses numerous network configs, depending on your location.
I'm in Hoogeveen, that's original Ziggo network and not the merged UPC network.
There are quite a few differences between the two. It's a nightmare...

#34 Updated by bas t 8 months ago

Anyhow, version 4.3-1029~g78f63ac18 still works as it should with network id 5555

And somewhere this year I'll get a fiberglass connection with another DVB-C provider, they can't possibly do it as wrong as Ziggo.

#35 Updated by Pim Zandbergen 8 months ago

Before the Ziggo/UPC merger, network ID's used to be different for each region.
But now, to quote the Ziggo website:

De frequentie en het netwerk-ID voor deze Ziggo CI+ Module is in heel Nederland hetzelfde. Gebruik de volgende gegevens:

Frequentie: 47400, 474000 of 474
Netwerk-ID: 5555 of 05555
Modulatie: 64-QAM
Symboolsnelheid: 6875

#36 Updated by Pim Zandbergen 8 months ago

according to http://www.dtvmonitor.com/nl/ziggo-denhaag , 1536 is "NIT-actual", and 5555 is one of "NIT-other" values.

#37 Updated by Jaroslav Kysela 8 months ago

OK, I see. The actual network should be tagged as 0x40, but it seems that your broadcaster just "don't care to create proper muxes for all locations" so we must force to use the other NIT. I'll do a fix.

#38 Updated by Jaroslav Kysela 8 months ago

Retest with master (with the network id set as before).

#39 Updated by Pim Zandbergen 8 months ago

The only exception to network ID 5555, according to Ziggo, is for all Philips TV's built in 2010, and Philips TV's from the 6000 Series built in 2011.

Supposedly, they can not remember the channels under network ID 5555.

They should use a different ID, that differs for each region. In The Hague, they should use 43186.

#40 Updated by Pim Zandbergen 8 months ago

You fixed it again Jaroslav!

#41 Updated by Jaroslav Kysela 8 months ago

  • Subject changed from No epg data at all with latest master head to Ziggo: No epg data at all with latest master head
  • Status changed from New to Fixed

#42 Updated by bas t 8 months ago

Confirmed fix.
Thanks a lot.

Also available in: Atom PDF