Two files meet. Your playlist lists channels, each optionally tagged with a tvg-id. Your guide is an XMLTV document in which every channel element carries a required, unique id attribute, and every program entry references one of those ids. A player builds the guide by string-matching one against the other. There is no fuzzy logic and no name matching by default, so ChannelOne.us and channelone.us are different strings to most players. That single fact explains the three symptoms people describe as IPTV EPG not working: nothing at all, the wrong shows, or a guide that exists but sits a few hours out. Knowing which one you have decides everything you do next.

Check the source field before anything else. In most players the EPG URL is a separate setting from the playlist URL, and if it is empty the player has nothing to download, a detail that costs people entire evenings. If a URL is present, force a manual update rather than waiting, because guide refreshes are scheduled rather than on-demand, and a player set to refresh every twelve hours will happily show yesterday's blank until its next window. Every six to twelve hours is a reasonable interval. If a manual update still returns nothing, open the same login in a second player. Blank in both means the source itself is down.

Because the identifiers matched, just not the way you wanted. Two different real-world channels can share a plausible id string, so the player confidently attaches the wrong schedule. This happens more with generic ids than with the DNS-style names the XMLTV specification recommends. Fix it at the player rather than in the file: TiviMate and similar apps let you remap a channel to a different guide entry by hand, which takes seconds per channel and survives playlist reloads. If dozens of channels are wrong rather than a handful, the mapping problem belongs to the source and is worth reporting instead of editing one by one.

A timezone offset, and it is fixable in a minute. XMLTV timestamps look like 20260501100000 +0000, where the trailing offset tells the player how to convert to local time. When a source omits the offset, most players assume UTC, so an Eastern viewer sees everything four or five hours out depending on the season. Two settings resolve it. First confirm the device clock and timezone are correct, because a wrong device timezone shifts the entire guide uniformly. Then apply the player's EPG time-shift setting to match the error you see: a guide running five hours late needs a shift of minus five.

Guide completeness is. No player setting invents data that was never published, and a service carrying 54,000+ live channels across 190+ countries will not have equally deep guide data for every one of them. Regional and niche feeds are where gaps show up, which is often exactly where people notice. The honest framing is that the guide is a separate deliverable from the stream, and a service should be able to tell you how far ahead its guide runs and how often it refreshes. Ask that before you pay, then check it inside the 7-day money-back window on your own channels rather than on a demo list.