Working now. Seeing all the guide entries.
yea got some entries now
I'm still getting nothing this morning, despite forcing reload of m3u & redownload of xmltv.
Yup. No entries now for me, since late last night... all blank now again.
Same here, No SamsungTV guide data, Pluto is fine.
I have guide data this morning.
I had an article show up in my Google Discovery feed a couple of days ago where the headline appeared to be clickbait about the demise of Samsung TV Plus. Apparently the article was really about what they display on refrigerators and perhaps has some backend integration with what we use here.
While just googling for that article, I see there's another one correcting the first article. So, who knows what's happening behind the scenes.
The initial clickbaity article:
The second, correcting article:
1 Like
I don't think correlation causes causation here.
Thank God, I can map the channels I use with gracenote instead of relying on Samsung's weird API to pop up with data...
Guide Data Not updating again this morning ? Guide was okay for about a day, us.xml
Pretty much, it updates once every 24hrs and show 4hrs of data, then nothing.
Must be the Samsung API since Matt says he updates his xml every 59 minutes.
To check if the guide data is stale...
Right now his xml file is almost 4 hours old (timestamps are New Zealand time, UTC+12:00) Index of /SamsungTVPlus/
And was supposedly generated almost 4 hours ago
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE tv SYSTEM "xmltv.dtd"><tv generator-info-name="www.matthuisman.nz" generated-ts="1716599390"> is Saturday, May 25, 2024 1:09:50 AM UTC
and it updated
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE tv SYSTEM "xmltv.dtd"><tv generator-info-name="www.matthuisman.nz" generated-ts="1716613589"> is Saturday, May 25, 2024 5:06:29 AM UTC
I'm surprised nobody has asked the question.
@matthuisman If you're generating an updated us.xml file every 59 minutes, how come the timestamp on the us.xml file at https://i.mjh.nz/SamsungTVPlus/ doesn't consistently update every 59 minutes?
If you have Channels DVR refreshing the XML every hour and still lose guide data, it must be a problem at the source https://i.mjh.nz/SamsungTVPlus/
Next time you get low on guide data, check that source site to see if the xml guide file is up to date.
Take into account those timestamps are NZ time (UTC + 12 currently)
Right now it's been 2hrs since it updated the us.xml file.
Even if it is "updated" does not mean that it has newer guide data, or that Channels will import it and parse the data correctly.
I have seen 2 things:
NO change in the date/time of the source .xml for several hours.
I have also see it change, but Channels still shows no guide data, even after a manual forced re-download.
That has to be something preventing Matt's scripts from generating a new xml file.
That would be as he explained earlier. If the Samsung TV API isn't providing new guide data, then his generated xml file will only include a new timestamp for when it was generated, but no update to the guide entries.
I don't know what scripts he uses and I don't use his Samsung TV guide data. Was just saying that users noticing these things should let Matt know. He generously offers it as a free service, so I wouldn't expect immediate responses or fixes to it.
1 Like
One could setup a simple one-liner shell script to check the timestamp of the xml file at his website.
Throw it into a cron job to run hourly.
Could even get fancy with the script and notify you that xml file is stale.
But it won't fix the problem, only Matt can do that.
samsung-epg-timestamp.sh
#!/bin/sh
# log timestamp of Samsung TV epg file at https://i.mjh.nz/SamsungTVPlus/ every hour into the file /volume1/arkives/samsung-epg-timestamp.log
# log time of run in ISO 8601 format (to the second)
echo $(date -Iseconds) $(curl -s "https://i.mjh.nz/SamsungTVPlus/" | grep 'href="us.xml"') >>/volume1/arkives/samsung-epg-timestamp.log
samsung-epg-timestamp.log
Website checked timestamp Website content
2024-05-26T10:01:01-07:00 <a href="us.xml">us.xml</a> 27-May-2024 03:06 1607076
2024-05-26T11:01:01-07:00 <a href="us.xml">us.xml</a> 27-May-2024 03:06 1607076
2024-05-26T12:01:01-07:00 <a href="us.xml">us.xml</a> 27-May-2024 03:06 1607076
2024-05-26T13:01:01-07:00 <a href="us.xml">us.xml</a> 27-May-2024 03:06 1607076
2024-05-26T14:01:01-07:00 <a href="us.xml">us.xml</a> 27-May-2024 03:06 1607076
It appears the gzipped xml files are updating, but they only contain the latest xml files, which are all stale, except for Austria.
Country xmlFile xmlFile Timestamp gzipped Timestamp
----------- ------- ----------------- -----------------
All all.xml 27-May-2024 03:06 27-May-2024 08:30
Austria at.xml 27-May-2024 08:07 27-May-2024 08:30
Canada ca.xml 27-May-2024 06:06 27-May-2024 08:30
Switzerland ch.xml 27-May-2024 06:06 27-May-2024 08:30
Germany de.xml 27-May-2024 06:06 27-May-2024 08:30
Spain es.xml 27-May-2024 06:06 27-May-2024 08:30
France fr.xml 27-May-2024 03:06 27-May-2024 08:30
UK gb.xml 27-May-2024 03:06 27-May-2024 08:30
India in.xml 27-May-2024 03:06 27-May-2024 08:30
Italy it.xml 27-May-2024 03:06 27-May-2024 08:30
Korea kr.xml 27-May-2024 03:06 27-May-2024 08:30
USA us.xml 27-May-2024 03:06 27-May-2024 08:30
The only reason I looked into it was I wanted to get the InWonder channel. But after seeing it's not the same one I miss from Fubo, I'm still looking for it.
1 Like
Well, whatever is happening, it is a regular thing now.
I only have guide day for some hours each day.
No data late evening, overnight.
Only gets some late morning and early afternoon.
(central USA time)
You say is NZ time, so, I asked my Google speaker, it is 1:05am Central USA, in NZ, it is between 6:05pm and 6:50pm. (NZ has multiple time zones it says)
@ matthuisman Any idea what is up?
1 Like
yup. wasnt a samsung thing at all.
I was using restcountries.com to get a friendly country name + flag .. and it seems to have "gone" ...
Anyway, chatgpt generated me a list of country codes + names and I can just use https://flagcdn.com/h240/{cpde}.png for flags
This removes all need for external service.
Changes have been made. Hopefully more reliable now.
4 Likes
Hi Matt,
Appears it's still missing some updates. 8am, 11am and 1pm NZST today.
shell script running every hour on the half hour
echo $(date -Iseconds) $(TZ='Pacific/Auckland' date -Iseconds) $(curl -s "https://i.mjh.nz/SamsungTVPlus/" | grep 'href="us.xml"')
Output
Time checked: Local time Time checked: NZST time Website content https://i.mjh.nz/SamsungTVPlus/
------------------------- ------------------------- -----------------------------------------------------
2024-05-27T13:30:01-07:00 2024-05-28T08:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 07:09 1605961
2024-05-27T14:30:01-07:00 2024-05-28T09:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 09:06 1602389
2024-05-27T15:30:01-07:00 2024-05-28T10:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 10:09 1597702
2024-05-27T16:30:01-07:00 2024-05-28T11:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 10:09 1597702
2024-05-27T17:30:01-07:00 2024-05-28T12:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 12:08 1593363
2024-05-27T18:30:01-07:00 2024-05-28T13:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 12:08 1593363
Not sure if curl is grabbing a cached copy from cloudflare, I have to look into the curl command line options for that. I can tell my browser (Firefox) is getting a cached copy from cloudflare.
I'm assuming
last-modified: Tue, 28 May 2024 01:56:42 GMT means that's when the webpage was last updated.
2 Likes
update your script to check at 30 past the hour.
It kicks off at 5 pass but can take 20mins before it pushes / updates CF cache.
that is why some files created earlier and then .gz 20 mins later when they are generated before push
But yeh, I need to migrate away from a monolithic script to individual jobs to stop each other breaking others etc.
1 Like
script is checking at 30 past the hour.
added the us.xml.gz file to it.
shell script running every hour at 30 past the hour
echo $(date -Iseconds) $(TZ='Pacific/Auckland' date -Iseconds) $(curl -s "https://i.mjh.nz/SamsungTVPlus/" | grep 'href="us.xml' | tr -d "\r")
Output
2024-05-27T13:30:01-07:00 2024-05-28T08:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 07:09 1605961
2024-05-27T14:30:01-07:00 2024-05-28T09:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 09:06 1602389
2024-05-27T15:30:01-07:00 2024-05-28T10:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 10:09 1597702
2024-05-27T16:30:01-07:00 2024-05-28T11:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 10:09 1597702
2024-05-27T17:30:01-07:00 2024-05-28T12:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 12:08 1593363
2024-05-27T18:30:01-07:00 2024-05-28T13:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 12:08 1593363
2024-05-27T19:30:02-07:00 2024-05-28T14:30:02+12:00 <a href="us.xml">us.xml</a> 28-May-2024 13:09 1602002 <a href="us.xml.gz">us.xml.gz</a> 28-May-2024 13:32 283099
2024-05-27T20:30:01-07:00 2024-05-28T15:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 15:05 1596313 <a href="us.xml.gz">us.xml.gz</a> 28-May-2024 15:25 282487
2024-05-27T21:30:01-07:00 2024-05-28T16:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 16:05 1565902 <a href="us.xml.gz">us.xml.gz</a> 28-May-2024 16:26 275896
2024-05-27T22:30:01-07:00 2024-05-28T17:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 17:05 1585933 <a href="us.xml.gz">us.xml.gz</a> 28-May-2024 17:12 277449
2024-05-27T23:30:01-07:00 2024-05-28T18:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 17:05 1585933 <a href="us.xml.gz">us.xml.gz</a> 28-May-2024 17:12 277449
2024-05-28T00:30:01-07:00 2024-05-28T19:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 19:05 1607612 <a href="us.xml.gz">us.xml.gz</a> 28-May-2024 19:12 281955
2024-05-28T01:30:01-07:00 2024-05-28T20:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 20:05 1608118 <a href="us.xml.gz">us.xml.gz</a> 28-May-2024 20:11 281059
2024-05-28T02:30:01-07:00 2024-05-28T21:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 20:05 1608118 <a href="us.xml.gz">us.xml.gz</a> 28-May-2024 20:11 281059
2024-05-28T03:30:01-07:00 2024-05-28T22:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 22:05 1591794 <a href="us.xml.gz">us.xml.gz</a> 28-May-2024 22:11 277710
2024-05-28T04:30:01-07:00 2024-05-28T23:30:01+12:00 <a href="us.xml">us.xml</a> 28-May-2024 23:05 1604335 <a href="us.xml.gz">us.xml.gz</a> 28-May-2024 23:22 280897
2024-05-28T05:30:01-07:00 2024-05-29T00:30:01+12:00 <a href="us.xml">us.xml</a> 29-May-2024 00:05 1589143 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 00:21 280265
2024-05-28T06:30:01-07:00 2024-05-29T01:30:01+12:00 <a href="us.xml">us.xml</a> 29-May-2024 01:05 1590349 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 01:17 282132
2024-05-28T07:30:01-07:00 2024-05-29T02:30:01+12:00 <a href="us.xml">us.xml</a> 29-May-2024 02:05 1599612 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 02:11 283579
2024-05-28T08:30:01-07:00 2024-05-29T03:30:01+12:00 <a href="us.xml">us.xml</a> 29-May-2024 03:05 1591546 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 03:13 283336
2024-05-28T09:30:01-07:00 2024-05-29T04:30:01+12:00 <a href="us.xml">us.xml</a> 29-May-2024 04:05 1570730 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 04:18 282493
2024-05-28T10:30:01-07:00 2024-05-29T05:30:01+12:00 <a href="us.xml">us.xml</a> 29-May-2024 05:05 1599947 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 05:13 286890
2024-05-28T11:30:01-07:00 2024-05-29T06:30:01+12:00 <a href="us.xml">us.xml</a> 29-May-2024 06:05 1597967 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 06:19 286178
2024-05-28T12:30:01-07:00 2024-05-29T07:30:01+12:00 <a href="us.xml">us.xml</a> 29-May-2024 07:05 1592903 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 07:14 286331
2024-05-28T13:30:01-07:00 2024-05-29T08:30:01+12:00 <a href="us.xml">us.xml</a> 29-May-2024 08:05 1586515 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 08:20 285086
2024-05-28T14:30:01-07:00 2024-05-29T09:30:01+12:00 <a href="us.xml">us.xml</a> 29-May-2024 09:05 1601316 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 09:13 287261
2024-05-28T15:30:01-07:00 2024-05-29T10:30:02+12:00 <a href="us.xml">us.xml</a> 29-May-2024 10:05 1597027 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 10:11 285292
2024-05-28T16:30:02-07:00 2024-05-29T11:30:02+12:00 <a href="us.xml">us.xml</a> 29-May-2024 11:05 1598407 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 11:22 283840
2024-05-28T17:30:02-07:00 2024-05-29T12:30:02+12:00 <a href="us.xml">us.xml</a> 29-May-2024 12:05 1583167 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 12:11 280540
2024-05-28T18:30:02-07:00 2024-05-29T13:30:02+12:00 <a href="us.xml">us.xml</a> 29-May-2024 12:05 1583167 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 12:11 280540
2024-05-28T19:30:01-07:00 2024-05-29T14:30:01+12:00 <a href="us.xml">us.xml</a> 29-May-2024 14:05 1596620 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 14:08 280196
Updated with latest log. Missed updates for May 28 8am, 11am, 1pm(late), 2pm, 6pm and 9pm NZST
Looking good since 10pm NZST last night!
Update: It appears the web page doesn't update until all the xml.gz files are updated. It was doing great until just now (2024-05-29T13:30:02 NZST).
2024-05-28T18:30:02-07:00 2024-05-29T13:30:02+12:00 <a href="us.xml">us.xml</a> 29-May-2024 12:05 1583167 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 12:11 280540
Using a web browser it shows the page was last-modified at Wed, 29 May 2024 01:36:18 GMT (2024-05-29T13:36:18 NZST). Website now shows this.
<a href="us.xml">us.xml</a> 29-May-2024 13:05 1592826 <a href="us.xml.gz">us.xml.gz</a> 29-May-2024 13:31 279350