IPTVGuides.net

Troubleshooting

Repair a blank, wrong or delayed IPTV programme guide

Classify the fault before making changes. This guide helps you check the guide source, match XMLTV channel IDs, resolve region and clock offsets, and verify that the repair survives a refresh.

5,117 words · About 24 min

Infomir MAG544 manufacturer illustration of the Ethernet connection
Infomir MAG544 manufacturer illustration of the Ethernet connectionImage source

Start with two channels and a known programme

Choose one affected channel and one that still seems to work. Open the failing channel first. Note whether sound and picture play, whether the player shows a blank guide row and whether it offers an error message for the guide source. Then open the control channel and record the programme playing at the current time. Use a recognised broadcast schedule or the provider’s official route to check the programme and edition. This gives you a known starting point without changing anything.

Write down the date and your local time zone. Programme listings describe events on particular dates, and a correct title can be associated with the wrong edition or time. Find the actual station or publisher schedule for the selected market. A broadcaster may show a city, region or local service name on the page. Save that name with the test, rather than relying on the channel’s short display name inside a player.

Make the first classification before acting. If every row in the grid is blank, investigate the guide source and import. If a single station is blank, concentrate on its feed identity or whether the schedule contains that channel’s programmes. If the whole grid appears one hour early or late, diagnose the time zone and source timestamp. If a few stations list different programmes, check regional mapping before applying a global shift.

Save a private copy of the working player settings if the app offers an approved backup, or record the guide source label and current mappings without the confidential address. Playlist URLs and EPG endpoints can contain account secrets. Keep those addresses in private storage and use fictional replacements when asking for help. A support post only needs real provider details through an appropriate private route when the provider requests them.

Once you can describe the fault in a sentence, follow the matching section below. “Live video works on both feeds, one guide row is blank, and a second local station has the right listing at 18:00” points to a specific class of problem. This is much easier to diagnose than a report that mixes video stops, guide data and an unverified clock setting.

See what the two sources do

A channel list tells the player which feed entries exist and can include labels, groups and identifiers. Programme guide data tells it which shows are scheduled for particular channels and times. They can come from the same provider. Each still has to reach the player, and the player has to join them in a way it supports. A stream that plays demonstrates that media reached the device. It provides little direct information about the separate schedule source.

XMLTV is one widely used way to supply programme information. Its format describes channels and programme entries. A channel element can have an id and one or more display names. A programme element refers to a channel by its channel attribute and carries the start time. Optional fields can include a stop time, subtitle, episode or other information specified by the source and supported by the app. A well-formed file can still describe a wrong, missing or old schedule.

In extended M3U lists, some players and providers use attributes such as tvg-id and tvg-name to identify and label channels. Kodi’s IPTV Simple Client documents the M3U and XMLTV roles for its supported versions. Other players can handle identity differently. Some offer manual association, and some use a provider’s internal catalogue without a user-editable XMLTV field. Follow the docs for your exact app and version before choosing a repair step.

Keep three labels in separate columns. Write what the viewer sees in the app, the ID in the source or playlist, and the schedule row used by the guide. Identical names can refer to several feeds. Two IDs may have a common prefix while differing by one regional suffix. In a provider app that does not expose these values, record the station edition and failing display dates, then ask its support for the mapping it expects.

A guide with only “No information” for one station is different from one with no programme data anywhere. If there are coverage gaps for a single window, compare its row with other current windows for the same station. You might find that today is empty and tomorrow is filled, or yesterday remains cached. Write the date coverage you observed before changing the whole guide source.

MegaOTT publisher photo composition for its app guide
An app-guide composition published by MegaOTT. Check the channel and guide behaviour in your own player.Image source

Check the source and import for an entirely blank grid

Open the player’s own guide settings and identify its approved schedule source. Check if it expects a URL, a file, a login-managed catalogue or a selected feed within the subscription. Look for the time of the last successful update if displayed. A server can respond without supplying usable guide data. A client can also show a remembered source label without having imported its current contents. Make the distinction in your notes.

Use the officially supported refresh operation. Wait for the import to finish or record the precise error. Inspect a known control channel and a second channel from a different group. Check both today and the next supported viewing window where the provider documents future listings. If every channel remains empty, find out if the responsible publisher can confirm a current source and whether any account conditions affect guide access.

For local files you are allowed to inspect, use a small redacted sample to see whether it contains XMLTV channels and programme entries. If you find a generic error page, an authentication notice or an empty response instead of schedule data, report that fact through the provider’s support. Share the response category and time. Keep the exact confidential address and credentials out of the report you make publicly.

Check whether the documented format matches the feature you are using. Some services supply a compressed source or an internal catalogue, and acceptance varies across clients. A file with an extension such as XML does not establish what the bytes contain, and a client that opens a stream address may have a separate rule for schedules. Compare against the provider’s supported app and the player’s official sources. If you can get an approved new source, keep the previous settings in a private backup while you test it.

If a client depends on your network for the guide import, check separately whether other approved resources open from that device. A playback stream from a different service says little about the guide origin. When the same source works on one approved player and fails on the other, write both app versions and what each showed. That is a better escalation than asking a service to rebuild its whole schedule based on one empty screen.

Repair one ID before editing a full playlist

Start with one row that you have confirmed belongs to the same intended station. Read the exact channel identifier from the playlist or source if the player and authorisation allow it. Locate the corresponding channel entry in the XMLTV schedule. In a typical setup, the schedule’s programme records refer to that saved channel id. Look for a record with a matching programme reference and an actual time in your viewing window.

Here is a small fictional example. Imagine a channel labelled “Field News East” in the player. Its playlist line contains tvg-id="field.news.east". The XMLTV channel id is field.news.east and a programme record’s channel attribute is field.news.east. That row lines up at all three points. A display name resembling “Field News” without the suffix does not prove that it belongs to the same edition.

Use a written comparison even when the mismatch seems obvious. The wrong guide mapping might use field.news.west, while video continues to come from the eastern feed. Morning schedules could look similar and diverge only on the evening news. Compare a programme that should differ and write the date. An apparent success on a network-wide replay may hide the regional problem until the next local broadcast.

If your app documents manual association, change only the affected channel first. Keep the original label or ID in your private notes. Apply the compatible mapping through the app, refresh, and compare today’s programme with the authorised schedule. Check a second time slot including the next scheduled programme. This isolates the one change you made.

If you maintain a legitimate local playlist, edit a copy. Keep the original line breaks, metadata and stream references intact. Change the specific identity field your player documents, then reimport the copy. It is easy to damage an otherwise functional line while doing an unplanned global replace. Avoid editing a provider-generated source that you cannot restore, and report mismatches upstream when its next update would overwrite your change.

Use the XMLTV mapping reference if you need a shorter description of the connection between the playlist, channel and programme. When the current instructions say which field the app supports, check the actual response. Some source feeds are intentionally duplicated for simulcasts that share a schedule. Other feeds use different records and require a separate match.

Recognise a missing schedule and a duplicate-looking feed

An exact ID match cannot supply a programme that is missing from the source. Check the time period covered by one programme for the failing channel. If the XMLTV record lists other days but no entries are available at the time you expect, describe that gap. It makes less sense to replace a correct association than to ask the guide supplier about coverage for that channel and date range.

Compare several programme IDs if a station changed its name, timeshift arrangement or region. A player may display the old label after a new channel was added. Use the official schedule around an event that is clearly different between the two feeds. Keep the provider’s current name and supported market in your own record so repeated fixes use the right identity rather than matching a familiar logo.

High-definition and standard-definition versions can carry the same programmes. It can be appropriate for two playable entries to share one schedule if they are actual simulcasts and the app supports it. A regional, alternate-language or delayed feed can need another guide ID or a documented time offset. Check the underlying schedule before treating a duplicate-looking row as an error. See the duplicate channel diagnosis for a case that isolates this issue.

Do a split-year test when daylight changes matter to your feed. Choose an ordinary weekday away from a clock change and a dated example close to the boundary. Compare the edition’s timetable for both. If only one of a pair deviates, capture the offset it actually used. The correct schedule for one city may differ from what appears on a similarly named national feed during a seasonal period.

If the lineup changed recently, obtain the current legal reference and refresh the playlist before forcing another EPG update. Some apps keep previous pairings or an import cache. A correct updated ID paired against an old programme cache can cause confusing results. Follow the refresh order documented for your app and confirm the channel identity after the playlist reload completes.

When only a few hours are missing, check the provider’s publication window and anything it labels limited. Some publisher data may be more complete for live broadcasts than for replay catalogues or temporary events. Ask about the specific channel and period that you measured. Giving the operator a date, local zone, affected edition and working control makes it possible to investigate without assuming the player’s whole guide is faulty.

Compare time, offset and date as three pieces of evidence

Start with a programme whose exact time is published by the broadcaster. Write its date and zone from the schedule. Look at the date the player displays along with the clock time. Choose another programme on a second channel. If the observed differences agree, test the device zone and documented EPG offset options before changing the association for any specific channel.

XMLTV timestamps can include an offset as part of the value. As a simple example, 20261115203000 +0000 represents 20:30 at offset zero on 15 November 2026. In a device displaying Asia/Karachi for that date, the local time is 01:30 on 16 November. The date changes with conversion. A viewer who compares only “20:30” and “01:30” in rows belonging to the same calendar date can make a good guide look wrong.

You can also compare two written timestamps that represent the same instant. A programme labelled 20261115233000 +0100 and another value written as 20261115223000 +0000 both convert to 22:30 UTC on the date shown. If the broadcaster and guide refer to this same point in time but the display differs, ask which zone the player is applying and whether a manual correction was previously entered. Keep the original values in the report without sharing a signed link that supplied them.

City or region rules can change with the date. Use IANA zone information for documented local conversion and test a date you can reproduce. A fixed example expressed as UTC plus one hour may be right for a seasonal period and different in another. On a clock change evening, two local times can appear with the same wall-clock reading. A timestamp that includes its actual offset can distinguish them. Take the exact date and offset to support when it matters.

Check what the player means by “Time shift,” “EPG offset” or any similar wording. A manual setting can apply to a channel, source or entire guide. Recording the actual starting value and scope is essential. If every station is one hour out, change one documented global preference only after you have checked the device’s zone and source timestamps. If one station differs, treat it as its own feed or association case. Verify two known events after any change.

Work through a whole-grid time shift

Imagine that two stations both show an evening programme at 19:00 and official schedules for the same market show 18:00. The app is receiving guide data, and a consistent difference gives you a clear first question. Confirm that both schedules really refer to the local market of the device and use the actual date. Then check whether the device zone was changed or a global correction remained from an earlier setup.

Check that the correct device zone and date are active using the device’s official settings path. A connected screen and an attached media box can have separate system settings. Verify the time used by the box or client that renders the guide. A TV’s own clock can be correct even when its separate HDMI app is following another zone. Record which device was checked before changing another household system.

If the device clock is correct, compare the source offsets for two entries where they are available. Note whether the provided instant is consistent with the official programme time for the intended edition. If a source has the correct times but the display consistently shifts both programmes, check the app’s documentation or report it to its publisher. If the actual source already shows the wrong times, evidence of both records belongs with the guide supplier.

Avoid leaving a temporary adjustment permanently enabled after the source is fixed. A global shift can make one set of events appear to line up during a single test day. It can cause false matches on other dates or when the source changes. Write down why you applied it and which schedules confirmed the result. Recheck following a service update and any daylight-saving transition that affects the places involved.

As a second control, open the vendor’s own approved client or the official broadcaster schedule. Compare relevant events at the same recorded local time on both. If only one app is off, send both versions and the two observations to its publisher. If all approved clients show the same offset from the broadcaster, send the source supplier the dated examples. The conflict is easier to investigate when the source, display and expected programme are all recorded.

Keep a stale import from looking like a missing guide

A guide can show yesterday’s rows after a new source is available. A player may store cached data between sessions. Depending on the app and its update interval, leaving and reopening the view may still show that stored copy. Check whether the last refresh completed successfully and whether the control station now has today’s data. Record what the screen says rather than assuming an update ran because you clicked a button.

If the lineup changed, use the app’s documented playlist update first. Confirm that the expected station is present and that you can identify its new row. Then refresh guide data. Check one known working station and one affected station after the refresh. If old rows still appear, see if the app has a documented way to clear or replace only the guide cache. Keep the service and retained favourites intact while you test.

Use the file’s content when you have permission to look at it. A filename or modification time can change without a new programme range appearing inside. Check a control station and record the first and last relevant times. The useful result is whether the guide covers today and expected future events. For a fresh source that still has yesterday’s records, the publisher may need to update its schedule rather than the playback app.

A careful side-by-side log could show “Guide updated at 09:14, player still shows yesterday’s programme at 19:00. Current approved file lists today for the same channel ID. Restarting the app without clearing the account did not change the display.” This is precise enough for the app provider to focus on import or cache. It gives the publisher more than “refresh is broken” while keeping personal playlist data out.

Some clients refresh on an interval or only on startup. Read the app’s official documentation for the version you actually installed. Avoid shortening a scheduled refresh aggressively without knowing the service’s limits and expected update rate. Check one intentional manual refresh if supported, and give it time to complete. The goal is to confirm one working update path that you can test after a lineup change.

Use the example records as a diagnostic exercise

This page includes a small fictional sample for a browser-local match check. It contains one correctly matched network feed, one feed with a renamed ID and one shared label with a different regional schedule. Use the example to see why the channel label alone is ambiguous. The check is deliberately narrow. It looks for exact identifier matches and counts associated programme entries in the text you give it. Your app’s import and mapping rules can differ.

Start with the labelled fixture. The correctly matched row should identify the matching XMLTV channel and find at least one programme reference. The renamed feed should report a missing match, even if similar names appear elsewhere. When you correct the fictional playlist ID to the value shown in the guide, the match should appear in the browser. Change one value at a time to see which field the result is using.

Try a second case in the same example. Keep the exact channel ID and remove the programme entries for that channel from the sample. The browser should still recognise the channel identity and report zero included programmes. That demonstrates the practical difference between finding an ID and having schedule coverage for your selected period. In a real support case, check the actual date and time ranges too.

Work with small sanitised text only. Real playlist entries and even a copied guide URL can reveal private service details. If you choose to inspect your own sources locally, work from a copy, remove secret addresses and avoid publishing the source text or screenshots of it. The fixture on this page uses reserved example addresses. The tool runs in the page and sends no input to an API.

Treat the result as a check on what you pasted. A single sample never proves that the production source is healthy. Confirm with an authorised source and the actual supported device. Take the exact card option, correct mapping and a date from the official schedule. A successful local check and a failing production device can both be real observations about different parts of the path.

Check a small XMLTV mapping sample

Use the fictional example or paste a redacted sample. The browser checks exact IDs and counts the programme records you included.

Tell a temporary event gap from a persistent problem

A broadcaster may announce a pop-up channel, a separate event slot or a specific broadcast window. Check the official schedule before changing the permanent mapping of a regular channel. A temporary event can appear under a distinct edition, with a shorter schedule and different availability. Confirm the channel and start time independently from any service marketing.

When a replay is involved, look for the format and date the provider expects. The line in a live guide can point to a previous programme without a playback window. If the schedule row is accurate while replay still fails, record that your guide and video are different parts of the issue. Contact the provider for its catch-up support and permitted time range. A programme label alone does not establish replay access.

In shared households, two clients can use different regional settings or guide sources. Compare their guide labels, account market and software version if one works and the other does not. An older client’s local cache can also retain a familiar edition. Do one scheduled comparison after you have checked the active source in both clients. If they differ, reproduce the outcome after applying one intended setting to the test device.

If a guide intermittently fails near midnight or in the hours around a clock change, retain the complete date and offset from the official source. A duplicated local hour is an important detail. An app may be interpreting a source time or clock zone differently from the other devices. Test a simple dated record before changing a favourite channel list or making a global correction.

Write down one alternate observation that would change the explanation. If you suspect the provider has no schedule for the event, see whether a current approved XMLTV feed or its native app includes it. If you suspect a blank result follows the client, try another authorised player for the exact station where appropriate. Keep the scope of the conclusion tied to the check you actually performed.

Write a support request that someone can reproduce

Use a short first line with the symptom, station and date. Include the device, operating system and app version and say whether live video works. List the exact viewing time zone and what the publisher’s schedule says for one station. If possible, include the affected guide ID using a sanitised sample or share the legitimate value privately where support requires it. Mention a control result from another station or permitted client.

A useful report might say “Blank guide row for Field News East in the TV app. Live video plays. On 15 November at 18:15 local time the broadcaster listed a programme. The guide had the North station as a working control. Refresh completed at 18:20. A second approved app on the same account showed a listing for the eastern feed.” Somebody can act on this without learning your password or personal details.

If the issue is an offset, include both UTC or source offset and expected local time with the date. For two channels with the same label, name the intended edition, the one that was mistakenly shown and the event that helped you tell them apart. If the fault follows a particular day after every guide update, report those two occurrences and whether the wrong date persisted after a supported refresh.

Send the request to the party responsible for the part that failed. The broadcaster confirms its actual viewing schedule. The service supplies the approved programme feed or line-up and can investigate provider-side mapping. The player publisher handles a parsing or display problem specific to its app. State what worked elsewhere if you have that evidence, so the recipient can identify which part of the path you already tested.

On the EPG forum, use a fictional playlist address and leave out personal account details, email addresses and labels you cannot safely share. Include the smallest example that demonstrates the problem. A screenshot of the time difference can help when carefully cropped. Follow the posting guide for a template you can use without exposing the guide source.

Verify the fix after a real programme change

A fixed row should show the right programme now and the expected next one. Compare both with the official programme schedule for the intended market. Make sure the channel opens the same feed shown by the guide. Recheck a control station after your change. If the issue was a global shift, use two stations and both a current and a future time before calling it resolved.

Run the documented refresh again when the app requires it or after a normal update interval. Confirm the corrected association survives the refreshed playlist and guide. If the provider releases new channel IDs, test the updated version rather than keeping an old private copy indefinitely. Preserve your small rollback note so you know which part of the change to reverse if it affects a different station.

Test at least one programme close to a date boundary if the original fault appeared there. When a seasonal transition is relevant, use a date on the other side or after the next planned review. During a period of uncertainty, keep the broadcaster’s published schedule as a fallback for the programmes you care about. Navigating to a known station while a guide problem is investigated can keep the household’s viewing working.

Record the resolution in a sentence somebody else can repeat. “Guide source refreshed after the lineup update. Field News East was mapped to the correct edition. The evening news and the following programme matched the broadcaster at the expected local times. The control channel stayed correct after a second refresh.” That gives the next viewer a grounded result without a claim about every channel in the package.

Check language labels and character handling separately

Programme titles and channel labels can contain punctuation, accented letters or more than one translation. Compare the visible label, the content of the underlying channel field where you can lawfully inspect it, and the selected language or market in the playback app. If a title looks incomplete or includes replacement characters while playback still works, capture which columns are affected. A blank due to text encoding deserves a different report from a blank due to missing programme records.

Check whether the device shows proper text in other menus and in a recognised control channel. If all guide data from a specific source shows the same rendering problem while a second published source looks correct, report the supported format and what appeared. Write the exact intended characters using a small excerpt you have permission to share. If an audio track is affected too, treat its language label as a separate observation. Text in the guide and actual audio through the player can be sourced independently.

Look for spaces or capitalisation differences in a copied identifier when the client supports exact matching. For a fictional example, field.news.East and field.news.east are different written strings. The browser check here shows them separately. Your app may offer a documented fallback to a display name or an explicit manual association. Use that instruction for the installed version and verify that the actual programme changed. An apparent success after changing several fields at once makes it impossible to tell which rule the app used.

When a provider has more than one language schedule, ask which edition matches the actual feed and whether regional audio is documented. A matching title in English and a translated listing can describe the same scheduled programme. Two stations with similar translations can also carry different programmes. Confirm a dated event using the correct broadcaster and compare the channel and programme identifiers through the supported client when possible.

Repeat the test after moving to a different player

Make a copy of your private configuration before comparing apps. You will need the service’s permitted account route, which version of the app you used and what the old player did for one known station. If the old player accepted an external XMLTV source, find out if the replacement supports that source and the same identifier method. A successful enrolment and working video do not automatically bring the old guide mapping across.

Record any manual adjustments you plan to carry forward. An earlier player could have one saved timeshift or a custom pairing for a local station. Recreate just one of those changes in the new app and run the two-station check. A different client can apply a shift globally instead of to one source or use different precedence where multiple feeds are present. Check what the relevant options do before importing an entire reference list from an old setup.

Try the regular update again once the new setup is working. Keep an approved fallback during normal viewing. If the guide returns to the old row after refresh, check whether the edit was stored in the individual player or supplied by a data feed that replaced it later. Ask the entity that publishes the line-up to include the intended identifiers if you cannot keep a compatible manual association through regular updates.

Keep only the details someone could reuse safely. Save the confident match, the app and OS versions and the expected broadcaster at a specific local time. If the mapping problems return after an update, you can bring the same small two-channel sample back to support. Avoid carrying old screenshots and unredacted playlist exports into an unrelated forum account simply because they are convenient to attach.

Keep a small record of guide changes

A repair log can stay short. Include the station edition, what field changed, two expected programme times and the date you checked them. Keep private source addresses in the service’s own protected settings. If you maintain the guide for relatives, write down where they can find the published broadcaster schedule while a repair is in progress. A person who just wants to watch the evening news should have a simple fallback they can find on their own.

When a new source arrives, compare its first useful day against that record before replacing the current one. Check a station that previously failed and one that acted as your reference. If the source gaps or broadcast times are different from the old guide, record the observable difference. This lets you distinguish a source correction from an unrelated player update that happened the same day.

Sources and scope

Publisher documentation and editorial analysis. Hardware and subscriptions were not purchased or tested for these guides.