I think something is intermittent. For your first scan did you see these and try and play them? It looks like the LCN wasn't being read so the Linux library gave them these bogus names but the 560-575
Code:
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#560] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#561] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#562] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#563] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#564] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#565] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#566] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#567] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#568] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#569] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#570] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#571] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#572] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#573] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#574] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [226.50MHz#575] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [219.50MHz#1585] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [219.50MHz#1587] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [219.50MHz#1588] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [219.50MHz#1589] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [219.50MHz#1590] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [219.50MHz#1591] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [219.50MHz#1592] (not found in most recent scan)
2025-10-22 07:41:00.187 [DEBUG][27] ...using existing tuning for [219.50MHz#1593] (not found in most recent scan)
TBH I've tried a lot of things. Many scans using the existing entires to see if it was a temp reception thing (we're having some weather here at the moment...).
I can currently see both the ABC names and those bogus ones in adapter0-DVB-T-channels.conf
I will likely nuke the container once I have things working and re-set up from scratch with the 'known-good' path. But for now I have the channels and guides there ok, and layback (CPU) works.
I am now on to trying to work out why VAAPI with my Meteor Lak iGPU doesn't work...although, realistically, I will barely need it as we pretty much only ever watch live TV through Kodi and that doesn't need transcoding...it's only testing in the browser that seems to need it.
That's exactly what is supposed to happen They aren't really bogus, the Linux API couldn't get the LCN in one of the scan but we don't have the earlier logs but NextPVR doesn't try an match them other than name.
The entries without the "name" are actually bad because the TSID and ONID aren't being returned either. This is all Linux API stuff really out of NextPVR control.