Background channel scan: How to deal with tropo channels overwriting locals?

[Billi23]

Ran the script for 7 days, which queries the tuner every 5 minutes for scan status and never saw a background scan.

Does this query

Code: Select all

curl -s http://192.168.1.7/lineup_status.json

expose the background scanning when it happens?

Or does running the query itself

Code: Select all

curl -s http://192.168.1.7/lineup_status.json

prevent a background scan from happening (hoping this is the case)?

I did a firmware update, then did a manual scan and the running script using the query

Code: Select all

curl -s http://192.168.1.7/lineup_status.json

picked up the manual scan happening.

EDIT : rephrased the post into questions, in hopes of getting some response

[Cabal]

All my local (Austin) 17.x channels were overwritten by San Antonio 17.x channels again last night, so it looks like running manual scans on the regular does not impede the background scans.

Any SD folks want to chime in on page 2?

[Billi23]

While we're waiting for the official SD reply, I've been running this script from my always on NAS for the past 10 days.
It appears that this keeps the background scans from happening on my CABLE HDHR Prime, but I can't be sure since my lineup doesn't change like yours does.

Curious it it keeps the background scans from happening on your OTA HDHR.

Here is the (linux shell) script I'm running

hdhr_background_scans.sh

Code: Select all

#!/bin/sh
# query status of HDHR Prime tuner for background scans every 5 minutes, 
# logging the query responses until the file /volume1/scripts/hdhr_background_scans.stop exists to stop the script
# 
# log start time of script in ISO 8601 format (to the second)
echo $(date -Iseconds) hdhr background scan check started >>/volume1/scripts/hdhr_background_scans.log
# loop until the file /volume1/scripts/hdhr_background_scans.stop exists
until [ -e /volume1/scripts/hdhr_background_scans.stop ]
do
   # timestamp log entry and query status of HDHR Prime tuner for background scans
   echo $(date -Iseconds) $(curl -s http://192.168.1.7/lineup_status.json) >>/volume1/scripts/hdhr_background_scans.log
   # wait 5 minutes
   sleep 300
done
# log stop time of script in ISO 8601 format (to the second)
echo $(date -Iseconds) hdhr background scan check stopped >>/volume1/scripts/hdhr_background_scans.log

I stop the script from running by creating the file "/volume1/scripts/hdhr_background_scans.stop"
My log file /volume1/scripts/hdhr_background_scans.log looks like this

Code: Select all

2025-08-16T15:37:38-07:00 hdhr background scan check started
2025-08-16T15:37:38-07:00 {"ScanInProgress":0,"ScanPossible":1,"Source":"Cable","SourceList":["Cable"]}
# ... above message reapeated 2015 times
2025-08-23T15:38:20-07:00 {"ScanInProgress":0,"ScanPossible":1,"Source":"Cable","SourceList":["Cable"]}
# Updated HDHR PRIME firmware and ran manual channel scan
2025-08-23T15:39:03-07:00 NOTE: System: reset reason = firmware upgrade
2025-08-23T15:39:28-07:00 NOTE: CableCARD: time changed from Thu Jan 01 00:00:25 1970 to Sat Aug 23 22:39:28 2025
2025-08-23T15:43:20-07:00 {"ScanInProgress":0,"ScanPossible":1,"Source":"Cable","SourceList":["Cable"]}
2025-08-23T15:48:00-07:00 NOTE: STARTED MANUAL SCAN WHICH TOOK 7:49, UNTIL 2025-08-23T15:55:49-07:00
2025-08-23T15:48:20-07:00 {"ScanInProgress":1,"Progress":10,"Found":24}
2025-08-23T15:53:20-07:00 {"ScanInProgress":1,"Progress":82,"Found":161}
2025-08-23T15:55:49-07:00 NOTE: MANUAL SCAN TOOK 7:49, UNTIL 2025-08-23T15:55:49-07:00
2025-08-23T15:58:20-07:00 {"ScanInProgress":0,"ScanPossible":1,"Source":"Cable","SourceList":["Cable"]}
# ... above message reapeated 890 times
2025-08-26T18:13:38-07:00 {"ScanInProgress":0,"ScanPossible":1,"Source":"Cable","SourceList":["Cable"]}