[mythtv-users] tv_grab_zz_sdjson_sqlite - Unknown xmltv channel identifier

[Mike Perkins]

On 19/02/2023 23:15, Bill Meek wrote:
> 
> 
> 
> On Sunday 19 February 2023 02:33:41 PM (-06:00), Ian Evans wrote:
> 
>  > New to using xmltv with Schedules Direct.
>  > > When I run mythfilldataase (and yes, as the mythtv user) I get about
>  > 40 of these for my OTA listings:
>  > > 2023-02-19 15:21:31.439935 N  Unknown xmltv channel identifier:
>  > I99248.json.schedulesdirect.org - Skipping channel.
>  > > Here's the thing I used the channel editor in mythtv-setup to enter
>  > the xmltv ids from SD. I'm getting the correct guide info inserted
>  > into my guide.
>  > > So where are these errors coming from?
> 
> Not sure my 1st reply made it to the list, but here's one way to
> eliminate the message (or use the 'ignore them' method (which
> I've used for months.)
> 
> 
> ...Unknown xmltv channel identifier: I125045.json.schedulesdirect.org - Skipping channel.
> 
> $ sqlite3 -line SchedulesDirect.DB 'SELECT * FROM channels WHERE station="125045"'
>    lineup = USA-OTA-90210
>   station = 125045
>   channum = 32.5
> selected = 0
>   details = {"atscMajor":32,"atscMinor":5,"stationID":"125045","uhfVhf":24}
> 
> $ sqlite3 -line SchedulesDirect.DB 'UPDATE channels SET selected=0 WHERE station="125045"'
> 
> To look at multiple stations:
> $ sqlite3 -line SchedulesDirect.DB 'SELECT * FROM channels WHERE station IN 
> ("124835","124741","125045")'
> 
I notice that in your SELECT statement response that 'selected' is already 0, before the following 
command sets it to zero. Is this a display artifact where 'selected' was actually null previously?
-- 

Mike Perkins