We are capturing all ATSC 3.0 channels, not just the channels that are using DRM or have been previously identified as using DRM.lenlab wrote: Sun Nov 15, 2026 4:59 am The "ch587000000" in the URL is 587 MHz, which is the center frequency for RF channel 33.
Uhm then this app has a serious issue as my DRM channels are NOT on RF channel 33. They are on RF channel 32 which is 578 frequency! So how is this logic in this app determining where the DRM channels are? Is it correctly finding them?
Maybe that is why Nick is saying there is reception issues for me? Also RF 33 is NOT on my list of channels to receive in my TV FireTV stick app to receive. IT is red X'd out. Ditto on my WIN11 PC. So this makes NO sense!
We need your help!
Re: We need your help!
Re: We need your help!
1. Would it help if it could use all tuners? (I'd happily let it) If so, can we config the script to go to the max (or number of tuners it can use etc)?
-
maclark7029
- Posts: 3
- Joined: Fri Nov 13, 2026 1:38 pm
- x 1
Re: We need your help!
How do I switch which channel is being monitored? Its currently capturing RF 33 (587 MHz), the Washington DC lighthouse on RF 28 (539 MHz), but its signal is only about 70% strength and 45-65% quality. I receive the Baltimore lighthouse at 100% signal and quality. WMAR 102.1 and WBAL 111.1 there are DRM-encrypted; WBFF 145.1 isn't. WMPT 122.1 and WNUV 154.1 also come in without DRM.
-
PhilJSmith67
- Posts: 12
- Joined: Sun Apr 13, 2014 6:13 pm
Re: We need your help!
If your ATSC 3.0 signal is on RF 32 then the URL should contain ch581000000 for (center of the channel at 578 - 584 MHz). For my tuner I ran Rescan in the hdhomerun_setup app, not the web interface, and that seemed to affect the frequency EACapture is checking.lenlab wrote: Sun Nov 15, 2026 4:59 am The "ch587000000" in the URL is 587 MHz, which is the center frequency for RF channel 33.
Uhm then this app has a serious issue as my DRM channels are NOT on RF channel 33. They are on RF channel 32 which is 578 frequency! So how is this logic in this app determining where the DRM channels are? Is it correctly finding them?
Maybe that is why Nick is saying there is reception issues for me? Also RF 33 is NOT on my list of channels to receive in my TV FireTV stick app to receive. IT is red X'd out. Ditto on my WIN11 PC. So this makes NO sense!
Re: We need your help!
Running the app on a 2nd PC will work as the HDHomeRun FLEX 4K can receive two ATSC 3.0 channels at once.kingpin2k wrote: Sun Nov 15, 2026 7:24 am 1. Would it help if it could use all tuners? (I'd happily let it) If so, can we config the script to go to the max (or number of tuners it can use etc)?
If you have two ATSC 3.0 channels there is a 50/50 chance of the server picking the same channel vs picking the other channel.
Re: We need your help!
I'm in the Chicago area and just got it running on my Synology NAS; thanks for providing the Docker image.
Re: We need your help!
Sorry I can't participate in test. I'm receiving a very weak signal (red) on all ATSC 3 signals in my area (23606). Have rescanned, no help. They had been viewable, but at some point they went red. I though they just gave up. Could be receiver though.
Dan
Dan
-
SpiderJerusalem
- Posts: 3
- Joined: Tue Oct 20, 2020 3:55 pm
Re: We need your help!
I'm doing my part!
AI bot just deployed the container on one of my homelabs. Happy to be a part of this and glad the community is here for you!
AI bot just deployed the container on one of my homelabs. Happy to be a part of this and glad the community is here for you!
Re: We need your help!
Yes fine you are picking up all ATSC 3.0 channels but the only channel being reported by your app is one that I am not tunning in. So why? Are you just capturing all ATSC 3.0 channels my antenna is picking up regardless of whether I am actually keeping them in my channel list? I pick up Philly stations poorly since I am in the NYC market. My antenna still shows them in your tuner in red. I have X'd them in the channel scan. So are you picking them up in the app?nickk wrote: Sun Nov 15, 2026 7:20 amWe are capturing all ATSC 3.0 channels, not just the channels that are using DRM or have been previously identified as using DRM.lenlab wrote: Sun Nov 15, 2026 4:59 am The "ch587000000" in the URL is 587 MHz, which is the center frequency for RF channel 33.
Uhm then this app has a serious issue as my DRM channels are NOT on RF channel 33. They are on RF channel 32 which is 578 frequency! So how is this logic in this app determining where the DRM channels are? Is it correctly finding them?
Maybe that is why Nick is saying there is reception issues for me? Also RF 33 is NOT on my list of channels to receive in my TV FireTV stick app to receive. IT is red X'd out. Ditto on my WIN11 PC. So this makes NO sense!
Re: We need your help!
I have done a number of rescans and it did not change anything.PhilJSmith67 wrote: Sun Nov 15, 2026 8:15 amIf your ATSC 3.0 signal is on RF 32 then the URL should contain ch581000000 for (center of the channel at 578 - 584 MHz). For my tuner I ran Rescan in the hdhomerun_setup app, not the web interface, and that seemed to affect the frequency EACapture is checking.lenlab wrote: Sun Nov 15, 2026 4:59 am The "ch587000000" in the URL is 587 MHz, which is the center frequency for RF channel 33.
Uhm then this app has a serious issue as my DRM channels are NOT on RF channel 33. They are on RF channel 32 which is 578 frequency! So how is this logic in this app determining where the DRM channels are? Is it correctly finding them?
Maybe that is why Nick is saying there is reception issues for me? Also RF 33 is NOT on my list of channels to receive in my TV FireTV stick app to receive. IT is red X'd out. Ditto on my WIN11 PC. So this makes NO sense!
![]()
-
dseto@live.com
- Posts: 2
- Joined: Wed Nov 11, 2026 3:21 pm
Re: We need your help!
Seem to keep getting the 503 error, not sure how to correct. have already did a rescan, reboot, and all main signals are 99-100% of strength.
Code: Select all
Loaded configuration
Found: HDHomeRun CONNECT 4K 10808E3D
Chosen: 10808E3D
Check-in succeeded.
Clock delta: -1.4 sec
Next capture to run at 11/15/2026 12:16:44 PM
Capturing http://192.168.50.82:5004/auto/ch497000000p0p1?format=dbg&duration=15 to b2ad2f4597bb4e13836bdf899b0cd7f7.tmp
Capture failed: http://192.168.50.82:5004/auto/ch497000000p0p1?format=dbg&duration=15 (server returned 503 Service Unavailable). Partial data (if any) left at: C:\Users\dseto\AppData\Local\EACapture\Captures\b2ad2f4597bb4e13836bdf899b0cd7f7.tmp
Next capture to run at 11/15/2026 6:30:28 PMRe: We need your help!
We need captures from all channels, but if are multiple ATSC 3.0 channels in your area and you really really really want to have it capture a different channel, you can have it repeat the random selection by 1) stopping the app, 2) deleting checkin_state.json in C:\Users\[username]\AppData\Local\EACapture\ 3) launching the app again.
Re: We need your help!
Am I getting captures from all channels? I only see one. 587 which is not even an ATSC 3.0 channel in my list of channels I want in my scans.
Loaded configuration
Found: HDHomeRun FLEX 4K 10ABA79B
Chosen: 10ABA79B
Check-in succeeded.
Clock delta: -0.6 sec
Next capture to run at 11/14/2026 3:39:08 PM
Capturing http://192.168.50.228:5004/auto/ch58700 ... uration=15 to 5e418183229f4faab44c07f18d26af3c.tmp
Upload to run at 11/14/2026 3:39:42 PM
Uploading 5e418183229f4faab44c07f18d26af3c.tmp
Next capture to run at 11/14/2026 9:23:31 PM
Found: HDHomeRun FLEX 4K 10ABA79B
Chosen: 10ABA79B
Check-in succeeded.
Clock delta: -0.6 sec
Capturing http://192.168.50.228:5004/auto/ch58700 ... uration=15 to cebd33742ee844ac9d8c47d79fea8379.tmp
Upload to run at 11/14/2026 9:24:17 PM
Uploading cebd33742ee844ac9d8c47d79fea8379.tmp
Next capture to run at 11/15/2026 3:08:06 AM
Capturing http://192.168.50.228:5004/auto/ch58700 ... uration=15 to 1ed82ccba2094314b617056cb4157101.tmp
Upload to run at 11/15/2026 3:08:59 AM
Uploading 1ed82ccba2094314b617056cb4157101.tmp
Next capture to run at 11/15/2026 8:53:07 AM
Found: HDHomeRun FLEX 4K 10ABA79B
Chosen: 10ABA79B
Check-in succeeded.
Clock delta: -0.6 sec
Capturing http://192.168.50.228:5004/auto/ch58700 ... uration=15 to 7ee93841b11742268417d8ce7451f174.tmp
Capture failed: http://192.168.50.228:5004/auto/ch58700 ... uration=15 (server returned 503 Service Unavailable). Partial data (if any) left at: C:\Users\lenla\AppData\Local\EACapture\Captures\7ee93841b11742268417d8ce7451f174.tmp
Next capture to run at 11/15/2026 3:16:27 PM
Found: HDHomeRun FLEX 4K 10ABA79B
Chosen: 10ABA79B
Check-in succeeded.
Clock delta: -0.6 sec
Loaded configuration
Found: HDHomeRun FLEX 4K 10ABA79B
Chosen: 10ABA79B
Check-in succeeded.
Clock delta: -0.6 sec
Next capture to run at 11/14/2026 3:39:08 PM
Capturing http://192.168.50.228:5004/auto/ch58700 ... uration=15 to 5e418183229f4faab44c07f18d26af3c.tmp
Upload to run at 11/14/2026 3:39:42 PM
Uploading 5e418183229f4faab44c07f18d26af3c.tmp
Next capture to run at 11/14/2026 9:23:31 PM
Found: HDHomeRun FLEX 4K 10ABA79B
Chosen: 10ABA79B
Check-in succeeded.
Clock delta: -0.6 sec
Capturing http://192.168.50.228:5004/auto/ch58700 ... uration=15 to cebd33742ee844ac9d8c47d79fea8379.tmp
Upload to run at 11/14/2026 9:24:17 PM
Uploading cebd33742ee844ac9d8c47d79fea8379.tmp
Next capture to run at 11/15/2026 3:08:06 AM
Capturing http://192.168.50.228:5004/auto/ch58700 ... uration=15 to 1ed82ccba2094314b617056cb4157101.tmp
Upload to run at 11/15/2026 3:08:59 AM
Uploading 1ed82ccba2094314b617056cb4157101.tmp
Next capture to run at 11/15/2026 8:53:07 AM
Found: HDHomeRun FLEX 4K 10ABA79B
Chosen: 10ABA79B
Check-in succeeded.
Clock delta: -0.6 sec
Capturing http://192.168.50.228:5004/auto/ch58700 ... uration=15 to 7ee93841b11742268417d8ce7451f174.tmp
Capture failed: http://192.168.50.228:5004/auto/ch58700 ... uration=15 (server returned 503 Service Unavailable). Partial data (if any) left at: C:\Users\lenla\AppData\Local\EACapture\Captures\7ee93841b11742268417d8ce7451f174.tmp
Next capture to run at 11/15/2026 3:16:27 PM
Found: HDHomeRun FLEX 4K 10ABA79B
Chosen: 10ABA79B
Check-in succeeded.
Clock delta: -0.6 sec
Re: We need your help!
The server assigns one channel to capture to keep things simple. The approach relies on there being multiple people in areas with multiple channels.
Re: We need your help!
Okay well in my case it is assigning a very wrong channel if it is ch587! I doubt you will get anything useful from ch587 since it is from Philly and poor reception as opposed to my NYC broadcasters!