The tvg-id convention supplies a guide-matching identifier in a compatible channel playlist. Its value can connect an entry to the channel key used in XMLTV data. The friendly channel name is a separate field, so two labels that look identical may still need different identifiers.
Treat the identifier as a key, not a phrase to improve for readability. A local rename that makes the text look neater can break the relationship if the corresponding guide uses the original value. First establish the importer’s documented matching rules.
Follow the relationship end to end
In a fictional example, the playlist entry for “Harbor News East” might use a key such as harbor.east. The guide declares a channel with that key, and dated programme records refer to it. The important question is whether the values agree in the actual sources, not whether the key resembles a public website address.
Do not assume a guide key is globally universal. Different guide publishers can use different identifiers for the same broadcaster. A key that worked with one source may not match a replacement guide even when both sources use the same visible name. Record which guide dataset the mapping belongs to.
Check one missing listing methodically
If the guide contains no events for that channel and date, a matching key alone will not fill the grid. If events exist under a different key, a deliberate mapping can be appropriate. Those are distinct findings and should lead to different requests for correction.
- Identify the exact regional or language edition in the player.
- Inspect the playlist’s guide key without changing the private source address.
- Find the matching channel declaration in the intended guide source.
- Confirm that dated programme records refer to that same key.
- Use a documented manual mapping if needed, then verify a specific programme window.
Avoid accidental matches
A national channel, local affiliate and time-shifted edition may share recognizable branding while following different schedules. Borrowing whichever identifier produces listings can create a convincing but incorrect guide. Validate the programme timing as well as the channel name before accepting the change.
Keep manual associations documented because an override can outlive the original source problem. After a catalogue update, revisit the affected entry rather than stacking a second workaround on top of the first. A clear note should say which channel was mapped, to which guide key, and why.
For support, use a sanitized identifier example and describe the dated mismatch. Complete account endpoints are unnecessary for explaining a join between metadata fields. The intended outcome is a correctly identified channel with the right schedule, not simply a nonempty guide grid.
Useful answers
Should tvg-id be rewritten to look like the channel name?
Only change it as part of a verified mapping correction. It is a matching key, not merely a display label.
Can the same broadcaster have different keys in different guide sources?
Yes. Identifier schemes can be specific to the source.
Does a valid key guarantee programmes exist for today?
No. The source must also contain current dated events for that key.