OTT Navigator distinguishes a guide linked to a provider from a general user-provided guide. The developer documents different matching behaviour for those routes. If the source belongs to one provider, configure it in the intended provider context rather than assuming every EPG entry point behaves identically. Choose the route according to who supplied the guide and how its entries should associate with the source. A valid schedule file is not a universal mapping for every similarly named channel in a merged list.
Preserve the source relationship
A provider-linked guide can use information associated with that source. A general guide added elsewhere may not have the same context for matching channels. The FAQ describes provider-linked matching using both names and guide identifiers, while a general user-provided guide uses name matching. That difference can explain why the same guide behaves differently after being entered elsewhere. Keep the supplied relationship intact and compare a known channel before deciding the file is wrong or manually renaming large parts of the playlist to fit it.
Avoid duplicate confusion
Adding the same guide through several routes can make it harder to understand which source supplied an entry. Start with the documented provider configuration and add another source only for a clear reason. Record the current guide locations before changing them, including which provider owns each one. If removing a duplicate route, preserve the source address privately so it can be restored if needed. Change one entry point at a time and reload to compare. Repeatedly adding the same file through more routes can conceal which configuration fixed a channel association or introduced a conflicting programme row.
Verify with a known channel
After reloading, inspect a channel whose programme information you recognise. Check both the channel association and the time before concluding that the guide is correct. Inspect programme title, channel identity and displayed time together after the reload. A familiar title at the wrong hour or attached to a regional variant is not a correct result. Compare another known entry before making broader changes. If retrieval succeeds but association fails, focus on the matching context and identifiers; if the whole guide fails to process, investigate that earlier stage first.
A practical sequence
0 of 3 steps completed on this page.
An example to work through
A guide intended for one provider should not be treated as a generic global schedule merely because it uses an XMLTV-style file. Place it in the documented provider context, reload and inspect a known channel's title and time. If it previously loaded elsewhere without matching, the configuration context may matter more than downloading another copy of the same file.
Questions about this topic
Are all EPG settings interchangeable?
No. The developer documents different matching context.
Does a programme title alone prove the correct channel match?
No. Verify the channel association and schedule time.
