Seeing the same issue. Logs have been submitted as 87a28f13-b527-4e52-9f8f-4df4332e939f
Please try the next build and see if it resolves the issue:
Nope. Same issue. Logs have been submitted as a0d41c8a-c78e-469b-b591-cc2552d64814
It appears to download guide data for one source, but not all sources. Have to do the rest manually.
DVR SERVER #1 [DVR] No listings for X-TVE (0 airings, 0 groups); starting indexer..
DVR SERVER #2 [DVR] No listings for USA-CA54023-X (0 airings, 0 groups); starting indexer..
I upgraded from v2025.07.17.1357 to v2025.07.17.1738 on both macos and linux docker and did not have any guide data issue this time. The logs do not show it reloading guide data or modifying scheduled recordings.
I have the guide problem. First release only got HDHomeRun guide data. Second version I got HDHomeRun and TVE guide data. Missing the rest of the source listings. It appears that is not going through the entire list of sources. The additional releases are just picking up one more source and stopping.
It appears to be loading guide data for the highest priority source and never does the rest of the sources.
I updated one server from v2025.07.17.0309 to v2025.07.17.1357 and another server from v2025.07.17.0309 to v2025.07.17.1738 and they both only updated guide data for the highest priority source.
Appears that it's also holding onto old, deleted sources in settings.
/settings
"device.priority.1323AADB": "1", OLD, DELETED SOURCE
"device.priority.M3U-ABCLocalNews": "2", OLD, DELETED SOURCE
"device.priority.M3U-Fubobridge": "5", OLD, DELETED SOURCE
"device.priority.M3U-NM21": "2", OLD, DELETED SOURCE
"device.priority.M3U-NM22": "3", OLD, DELETED SOURCE
"device.priority.M3U-NM23": "5", OLD, DELETED SOURCE
"device.priority.M3U-NM24": "4", OLD, DELETED SOURCE
"device.priority.M3U-NM25": "3", OLD, DELETED SOURCE
"device.priority.M3U-NM26": "4", OLD, DELETED SOURCE
"device.priority.M3U-NM27": "2", OLD, DELETED SOURCE
"device.priority.M3U-NewsMax2": "2", OLD, DELETED SOURCE
"device.priority.M3U-Newsmax2": "2", OLD, DELETED SOURCE
"device.priority.M3U-Plutonocords": "2", OLD, DELETED SOURCE
"device.priority.M3U-Prime1323AADB": "4", OLD, DELETED SOURCE
"device.priority.M3U-TestPrime": "1", OLD, DELETED SOURCE
"device.priority.M3U-tubiTV": "3", OLD, DELETED SOURCE
"device.priority.M3U-tubiTVNoEpg": "2", OLD, DELETED SOURCE
"device.priority.TVE-Comcast_SSO": "2", VALID SOURCE, 1st priority
"device.priority.TVE-Fubo": "4", OLD, DELETED SOURCE
"device.priority.TVE-slingtv": "2", OLD, DELETED SOURCE
My second priority source (M3U-LocalFOX40KTXL) doesn't even appear in the list.
So I changed source priority, saved and now it appears in the list.
You're saying that when you were on v2025.07.17.0309 you didn't have this issue?
Correct
Server 1
2025/07/16 21:15:00.501102 [SYS] Downloading new version v2025.07.17.0309
2025/07/16 21:15:14.877405 [SYS] Update downloaded and verified successfully.
2025/07/16 21:15:15.353424 [SYS] Created database snapshot: backup-20250717.041514
2025/07/16 21:15:15.353746 [SYS] Removing old backup backup-20250626.094844
2025/07/16 21:15:15.424506 [SYS] Shutting down for upgrade from v2025.07.16.2300 to v2025.07.17.0309
2025/07/16 21:15:15.426089 [DVR] Recording engine stopped.
2025/07/16 21:15:16.818187 [SYS] Starting Channels DVR v2025.07.17.0309 (linux-x86_64 pid:7) in /channels-dvr/data
2025/07/16 21:15:17.185711 [SYS] Started HTTP Server on 8189
2025/07/16 21:15:18.179639 [HDR] Found 1 devices
2025/07/16 21:15:18.962111 [M3U] Refreshed lineup for Prime1323AADB with 28 channels
2025/07/16 21:15:22.068688 [DVR] Deleting skipped job 1752717600-786 Viewfinder
2025/07/16 21:15:22.297125 [DVR] Recording engine started in /volume1/ChDVR8189
2025/07/16 21:15:22.308121 [SYS] Removing old update 2025.06.26.1658
2025/07/16 21:15:32.431013 [IDX] Pruned 99 expired airings from USA-CA54023-X in 171ms.
2025/07/16 21:15:32.551937 [IDX] Pruned 99 expired airings from X-M3U in 120ms.
2025/07/16 21:15:54.025496 [SYS] Created database snapshot: backup-20250717.041553
2025/07/16 21:15:54.025767 [SYS] Removing old backup backup-20250627.124844
Server 2
2025/07/16 21:15:02.898278 [SYS] Downloading new version v2025.07.17.0309
2025/07/16 21:15:22.804555 [SYS] Update downloaded and verified successfully.
2025/07/16 21:15:22.933258 [SYS] Created database snapshot: backup-20250717.041522
2025/07/16 21:15:22.933624 [SYS] Removing old backup backup-20250625.201726
2025/07/16 21:15:23.006079 [SYS] Shutting down for upgrade from v2025.07.16.2300 to v2025.07.17.0309
2025/07/16 21:15:23.008035 [DVR] Recording engine stopped.
2025/07/16 21:15:24.782391 [SYS] Starting Channels DVR v2025.07.17.0309 (linux-x86_64 pid:7) in /channels-dvr/data
2025/07/16 21:15:25.366167 [SYS] Started HTTP Server on 8190
2025/07/16 21:15:25.816131 [HDR] Found 1 devices
2025/07/16 21:15:27.544322 [DVR] Recording engine started in /volume1/ChDVR8190
2025/07/16 21:15:27.546629 [SYS] Removing old update 2025.06.26.1658
2025/07/16 21:15:37.407182 [IDX] Pruned 245 expired airings from X-TVE in 192ms.
2025/07/16 21:15:37.495956 [IDX] Pruned 4 expired airings from X-M3U in 88ms.
2025/07/16 21:15:40.027191 [SYS] Created database snapshot: backup-20250717.041539
2025/07/16 21:15:40.027442 [SYS] Removing old backup backup-20250626.231726
For the folks who are having this problem, what kind of guide data/source is having problems?
- Is it all of your sources? only some of them?
- what is the guide data source for each one?
- Are there some that are working?
- What have you done to fix it?
My order of sources is
HDHomeRun
YouTube TV
Frndly1
Frndly2
Pluto
E+TV
After upgrading to 2025.07.17.1738, I got guide info for the first two and Frndly2. No guide data for Frndly1, Pluto, or E+TV.
I manually updated guide for Frndly1. Pluto and E+TV had no guide data.
I was checking before this reply and Pluto and E+TV now have guide data. I never touched these two.
If you want to look at my logs, I submitted as
7e2cd50a-4c30-4e59-8274-3e7e562c8823
Is everyone who is missing guide data only missing it for M3U sources?
- Is it all of your sources? only some of them?
SERVER #1 has two sources: HDHomeRun PRIME and an M3U. Only the HDHR PRIME fetched guide data after the update
SERVER #2 has 3 sources: TVE-Xfinity, an M3U and a disabled HDHR Prime. Only TVE-Xfinity fetched guide data after the update
- what is the guide data source for each one?
See source setting images above
- Are there some that are working?
Only the highest priority source on each server. Had to manually fetch guide data for the rest.
- What have you done to fix it?
manually fetch guide data
Appears that's the case.
I have another server with 4 M3U sources and after updating to v2025.07.17.1738 ALL guide data is missing. Including one of the sources that uses stationid to get Gracenote guide data.
Please try the latest build and see if that resolves it.
Thanks, working here.
Have to assume some changes were made to the guide database that requires reloading all the guide data.
2 Likes
Seems to be working for me as well.
1 Like
No I did have the issue when I updated to v2025.07.17.0309. I did not see the issue happen again when I upgraded "from v2025.07.17.0309 to v2025.07.17.1357"
I usually lag updating, had:
2025.06.01.2212
Sources (in order):
Philo: http://192.168.2.102:8089/devices/TVE-Philo/channels.m3u?format=ts&codec=copy
Hulu: http://192.168.2.102:8089/devices/TVE-Hulu/channels.m3u?format=ts&codec=copy
HDHomeRun QUATRO: http://192.168.2.102:8089/devices/1077364E/channels.m3u?format=ts&codec=copy
Pluto Docker: http://192.168.2.102:8089/devices/M3U-PlutoDocker/channels.m3u?format=ts&codec=copy
Plex: http://192.168.2.102:8089/devices/M3U-Plex/channels.m3u?format=ts&codec=copy
VLC BRIDGE PBS: http://192.168.2.102:8089/devices/M3U-VLCBRIDGEPBS/channels.m3u?format=ts&codec=copy
Updated to:
2025.07.17.2006 (see logs starting 2025/07/17 15:58:02.783404)
It began processes of "fetching missing guide data for ..."
... a little while later ...
After completion, Guide looks good, except for Philo, it was empty.
I then ran manual "Redownload" of guide data for this source
(see logs starting 2025/07/17 16:12:23.662164)
Everything is now complete, unsure if Philo may have auto fixed later, but it seemed to miss it after the update to new version.
No need to reply, just posting in case helpful.
Diagnostic sent (all checks were green by the way) after manual guide pull for Philo completed:
Logs have been submitted as 331c2972-16e6-4a17-84d7-f43a48ce680c
No need to reply direct to me, as it is working after the manual guide refresh
2 Likes
2025.07.28.0213 resolved our missing data issue (so far)