Thanks for the reply.
Assuming I have enabled the debugging correctly, I don't seem to be getting any more info than I did before:
2024-10-24 17:19:31.892 bouquet: 28.2E/11426H/{PMT:0}: mapped service from 28.2E
I got that by deleting all channels with "PMT" in the name for this particular network, then doing a force scan on the network created bouquet.
Here is the service from the api:
{
"sid": 10549,
"lcn": 0,
"lcn_minor": 0,
"lcn2": 0,
"srcid": 0,
"dvb_servicetype": 0,
"dvb_ignore_eit": false,
"prefcapid": 0,
"prefcapid_lock": 0,
"force_caid": 0,
"pts_shift": 0,
"created": 1728426160,
"last_seen": 1729786018,
"enabled": true,
"auto": 0,
"priority": 0,
"s_type_user": -1,
"verified": 0,
"pcr": 0,
"pmt": 0,
"stream": [],
"uuid": "4d840711a2be4fb78bac97618e855b34"
},
Some networks have way more of these "PMT" channels mapped than others.
I picked this network because it doesn't have many, and it has more tuners.
Hopefully finding the cause will be faster, and I can apply the fix to all networks after.