Trex IPTV and the programme guide: why the EPG breaks, and how to fix it
Of every support message an IPTV provider receives, a surprising share are not about video at all. The picture is perfect. The channels load. The programme guide is simply empty, or worse, populated with the wrong programmes at the wrong times. Anyone evaluating Trex IPTV — or any service — will hit this eventually, and the fix is almost never the one people try first.
The guide is not part of the stream
This is the detail that explains everything else. The video and the guide arrive by completely separate routes. The stream is a continuous transport of compressed video. The guide is XMLTV: a plain XML document listing programmes, their start and end times, and which channel each belongs to. Your player downloads that file separately and stitches the two together on your screen.
Because they are separate, they fail separately. A blank guide next to a flawless picture is not a contradiction — it is exactly what you would expect when one of two independent things has gone wrong.
tvg-id is where it lives or dies
The join between the two is a single attribute. Each channel in the playlist declares a tvg-id. Each programme in the XMLTV file declares the channel id it belongs to. When those two strings match exactly, the guide appears. When they do not, you get silence.
And they mismatch easily. BBCOne.uk and bbc.one.uk and BBC One are three different strings as far as the matching is concerned. A provider that rebuilds its channel list, or a guide source that revises its naming, can break every channel at once without touching a single stream.
This is why "the guide stopped working" reports so often arrive in a cluster from many customers at the same time, and why they resolve at the same time too. It is a data alignment problem, not a delivery problem.
The three-hour shift
The second most common report is a guide that is right but uniformly wrong: every programme showing three hours early, or two hours late, consistently across every channel.
That is a time zone problem and it is in your player, not the guide. XMLTV timestamps carry an offset — a programme is recorded as starting at a specific moment in a specific zone. Your player converts that to your local time using whatever region it thinks it is in. Set the device to the wrong zone, or leave a player's own timezone override at a default, and everything shifts by a constant amount.
The tell is the consistency. A guide that is wrong by a fixed number of hours across the board is a conversion issue. A guide that is wrong on some channels and right on others is a mapping issue.
What a well-run service does about it
Maintaining guide data is unglamorous, continuous work. Channel line-ups change, broadcasters rename services, regional variants split and merge. A provider that treats the EPG as something set up once and forgotten will drift within months. One that treats it as a maintained dataset keeps the ids stable even when the underlying sources move around.
It is a reasonable thing to judge a service by, precisely because it is invisible when done well. The Trex IPTV apps ship with the guide already mapped, which removes the most common failure mode before a customer ever sees it — not because the technology is different, but because the mapping has been done rather than left to the player to guess.
A short diagnostic
Work through it in this order and you will find the cause in a couple of minutes.
Does the picture play? If yes, the stream and your credentials are fine, and nothing you do to them will help the guide. Is the guide empty on every channel, or only some? Every channel points at the guide file failing to load or a wholesale id mismatch; only some points at those specific channels being unmapped. Is the guide present but shifted? That is the timezone, in your player's settings. Did it work yesterday? Then something changed at the source, and it is worth a message to support rather than an evening of reinstalling apps.
Why it is worth caring about
A guide is not decoration. It is the difference between browsing television and hunting through an alphabetical list of six hundred channel names. When it works, nobody thinks about it. When it does not, the whole service feels broken even though every stream is delivering perfectly. That gap between the technical reality and the experienced reality is worth understanding, because it will save you from replacing hardware that was never the problem.