Portland, OR. HDHR5-4K 1080644E, firmware 20261107, Linux script 1.0.0.0.
Every job I've been scheduled is ch479000000p0?format=dbg. The tuner returns 503 with 806 Tune Failed every time, including the Nov 17 eas.dbg job. ATSC 3.0 tunes fine on 587 MHz.
479 MHz is ATSC 1.0 here right now (MeTV). The only ATSC 3.0 entry on 479 is 141.1, which my latest scan didn't find, so it only shows up in show=all. The server seems to be scheduling jobs based on lineup entries the latest scan didn't find.
Also, the script logs only the bare 503. Logging X-HDHomeRun-Error would make failures like this easier to diagnose.
EACapture (Linux): every job fails with 806 Tune Failed on 479 MHz
Re: EACapture (Linux): every job fails with 806 Tune Failed on 479 MHz
I'm in the PDX area as well. Running on Linux Mint 22.3. No problems with the script and it runs without errors.tjsander wrote: Fri Nov 13, 2026 1:22 am Portland, OR. HDHR5-4K 1080644E, firmware 20261107, Linux script 1.0.0.0.
Every job I've been scheduled is ch479000000p0?format=dbg. The tuner returns 503 with 806 Tune Failed every time, including the Nov 17 eas.dbg job. ATSC 3.0 tunes fine on 587 MHz.
479 MHz is ATSC 1.0 here right now (MeTV). The only ATSC 3.0 entry on 479 is 141.1, which my latest scan didn't find, so it only shows up in show=all. The server seems to be scheduling jobs based on lineup entries the latest scan didn't find.
Also, the script logs only the bare 503. Logging X-HDHomeRun-Error would make failures like this easier to diagnose.
I made sure I was on the latest firmware and did a rescan of the channels.
Re: EACapture (Linux): every job fails with 806 Tune Failed on 479 MHz
Fixed (if it is the problem I think it is) - please download the script again to get the latest script.
Re: EACapture (Linux): every job fails with 806 Tune Failed on 479 MHz
I installed it, but the issue is still reproducing. The update changes the script's local check, which now skips Subscribed: 0 entries. The script still sends the full show=all lineup, and the server still schedules everything on 479 MHz.
After the update I restarted and checked in again (HDHR5-4K 1080644E, Portland, OR). All 17 jobs in the new schedule are ch479000000p0?format=dbg, including the Nov 17 eas.dbg job. Every attempt on 479 so far has returned 503 / 806 Tune Failed. 479 MHz is still ATSC 1.0 here, and ATSC 3.0 works on 587 MHz.
The fix probably needs to be server-side. Maybe only frequencies with an ATSC 3.0 entry that was found in the most-recent scan?
After the update I restarted and checked in again (HDHR5-4K 1080644E, Portland, OR). All 17 jobs in the new schedule are ch479000000p0?format=dbg, including the Nov 17 eas.dbg job. Every attempt on 479 so far has returned 503 / 806 Tune Failed. 479 MHz is still ATSC 1.0 here, and ATSC 3.0 works on 587 MHz.
The fix probably needs to be server-side. Maybe only frequencies with an ATSC 3.0 entry that was found in the most-recent scan?
Re: EACapture (Linux): every job fails with 806 Tune Failed on 479 MHz
Is there a way to factory reset and/or clear the stale channel entries from /lineup.html?show=all ?
This would likely repro for anyone who has run channel scans on the same device in different cities, unless there is some region check that clears stale entries.
This would likely repro for anyone who has run channel scans on the same device in different cities, unless there is some region check that clears stale entries.
Code: Select all
2026-11-13 01:57:56 First launch
2026-11-13 01:57:56 Found: HDHomeRun CONNECT 4K 1080644E
2026-11-13 01:57:56 Chosen: 1080644E
2026-11-13 01:57:56 Check-in succeeded.
2026-11-13 01:57:56 Clock delta: -0.9 sec
2026-11-13 01:57:56 Next capture to run at 2026-11-13 03:51:20
2026-11-13 01:58:23 Loaded configuration
2026-11-13 01:58:23 Found: HDHomeRun CONNECT 4K 1080644E
2026-11-13 01:58:23 Chosen: 1080644E
2026-11-13 01:58:23 Check-in succeeded.
2026-11-13 01:58:23 Clock delta: -1.0 sec
2026-11-13 01:58:23 Next capture to run at 2026-11-13 03:51:20
2026-11-13 01:58:43 Loaded configuration
2026-11-13 01:58:44 Found: HDHomeRun CONNECT 4K 1080644E
2026-11-13 01:58:44 Chosen: 1080644E
2026-11-13 01:58:44 Check-in succeeded.
2026-11-13 01:58:44 Clock delta: -0.5 sec
2026-11-13 01:58:44 Next capture to run at 2026-11-13 03:51:19
2026-11-12 17:59:07 Loaded configuration
2026-11-12 17:59:08 Found: HDHomeRun CONNECT 4K 1080644E
2026-11-12 17:59:08 Chosen: 1080644E
2026-11-12 17:59:08 Check-in succeeded.
2026-11-12 17:59:08 Clock delta: -0.7 sec
2026-11-12 17:59:08 Next capture to run at 2026-11-12 19:51:20
2026-11-12 19:51:19 Capturing http://192.168.1.29:5004/auto/ch479000000p0?format=dbg&duration=15 to 7ab10b7d6c833d8d22e6766dbccaae84.tmp
2026-11-12 19:51:20 Capture failed: http://192.168.1.29:5004/auto/ch479000000p0?format=dbg&duration=15 (The requested URL returned error: 503). Partial data (if any) left at: /home/travis/eacapture/Captures/7ab10b7d6c833d8d22e6766dbccaae84.tmp
2026-11-12 19:51:20 Next capture to run at 2026-11-13 01:41:02
2026-11-13 01:41:02 Capturing http://192.168.1.29:5004/auto/ch479000000p0?format=dbg&duration=15 to 6a6aa0ddb8738472df4fc4afec977a4c.tmp
2026-11-13 01:41:02 Capture failed: http://192.168.1.29:5004/auto/ch479000000p0?format=dbg&duration=15 (The requested URL returned error: 503). Partial data (if any) left at: /home/travis/eacapture/Captures/6a6aa0ddb8738472df4fc4afec977a4c.tmp
2026-11-13 01:41:03 Next capture to run at 2026-11-13 08:03:56
2026-11-13 01:59:10 Found: HDHomeRun CONNECT 4K 1080644E
2026-11-13 01:59:10 Chosen: 1080644E
2026-11-13 01:59:10 Check-in succeeded.
2026-11-13 01:59:10 Clock delta: -0.5 sec
2026-11-13 08:03:56 Capturing http://192.168.1.29:5004/auto/ch479000000p0?format=dbg&duration=15 to e09159ee8659627429581bc3d1deb4e6.tmp
2026-11-13 08:03:56 Capture failed: http://192.168.1.29:5004/auto/ch479000000p0?format=dbg&duration=15 (The requested URL returned error: 503). Partial data (if any) left at: /home/travis/eacapture/Captures/e09159ee8659627429581bc3d1deb4e6.tmp
2026-11-13 08:03:57 Next capture to run at 2026-11-13 14:14:52
2026-11-13 09:59:11 Found: HDHomeRun CONNECT 4K 1080644E
2026-11-13 09:59:11 Chosen: 1080644E
2026-11-13 09:59:11 Check-in succeeded.
2026-11-13 09:59:11 Clock delta: -0.9 sec
2026-11-13 11:47:11 Loaded configuration
2026-11-13 11:47:11 Deleted 3 leftover partial capt
2026-11-13 11:47:12 Found: HDHomeRun CONNECT 4K 1080644E 2026-11-13 11:47:12 Chosen: 1080644E
2026-11-13 11:47:12 Check-in succeeded.
2026-11-13 11:47:12 Clock delta: -0.8 sec
2026-11-13 11:47:12 Next capture to run at 2026-11-13 14:14:52 2026-11-13 14:14:51 Capturing http://192.168.1.29:5=dbg&duration=15 to811736e26e062fa0d6b1cbfd53a46430.tmp
2026-11-13 14:15:01 Capture failed: http://192.168.1.29:5004/auto/ch479000000p0?format=dbg&duration=15 (The requested URL returned error: 503). Partial data (if any) left at: /home/tr6e26e062fa0d6b1cbfd53a46430.tmp
2026-11-13 14:15:01 Next capture to run at 2026-11-13 20:27:21
2026-11-13 14:55:21 Loaded configuration
2026-11-13 14:55:21 Deleted 1 leftover partial capt
2026-11-13 14:55:22 Found: HDHomeRun CONNECT 4K 1080644E
2026-11-13 14:55:22 Chosen: 1080644E
2026-11-13 14:55:22 Check-in succeeded.
2026-11-13 14:55:22 Clock delta: -0.8 sec
2026-11-13 14:55:22 Next capture to run at 2026-11-13 20:27:21Re: EACapture (Linux): every job fails with 806 Tune Failed on 479 MHz
This is 100% local.tjsander wrote: Fri Nov 13, 2026 12:53 pm The fix probably needs to be server-side. Maybe only frequencies with an ATSC 3.0 entry that was found in the most-recent scan?
Can you please save http://1080644E.local/lineup.json?tuning&show=all and email it to support@silicondust.com
Once sent please let me know the ticket number so I can find it quickly.