[mythtv-users] Unknown xmltv channel identifier: I103786.json.schedulesdirect.org - Skipping channel

Gary Buhrmaster gary.buhrmaster at gmail.com
Fri Feb 2 19:05:58 UTC 2024

On Fri, Feb 2, 2024 at 6:46 PM Jack McGee <jack at greendesk.net> wrote:
> I don't know when this started. There is nothing in program guide.   I
> see mythfilldatabase completed successfully in mythtv frontend.  This is on

There are three common cases (and
none of them are considered fatal,
just informational).

The first is that there is a new channel
in your location, with a new XMLTVID
(if it is an OTA source maybe a new
diginet, or if it is a cable source maybe
a new channel).

The second is that a channel has
changed XMLTVID due to upstream
changes (it happens more often with
cable changes, such as a change
for timezone sources (east to west),
or sometimes the channel just
changes it's sources entirely).

The last is an artifact for (especially)
OTA locations with translators.
For "reasons" the upstream
sometimes (and the sometimes
is the annoying part) uses a
different XMLTVID for a translator
transmitter even though it is
providing 100% the same schedule.

In some cases you can rerun the
channel setup, or ask mythfilldatabase
to refresh your channels.

There is also a 3rd party application
that can try to identify the details
and offer to (in some cases) fix
things for you.  It is documented
on the MythTV wiki.

More information about the mythtv-users mailing list