Is there a way to temporarily disable tuners(so they are not available for recording)

[mkanet]

Currently a couple of my TV recording sources need to go offline temporarily for automatic maintenance (5 minutes). Is there a clever way to tell sageTV to not use those tuners during that 5 minute window; hence, using alternate tuners on the same lineup at that time?

Maybe there's a clever way to do this?

Thanks,
Michael

[Fuzzy]

I think it would be easier to move your maintenance to when the device will not be needed, than to tell sage not to use the device for the period of time. I'm pretty sure some people use SJQ to check for gaps in the recording schedule, for things like system maintenance/reboots.

[mkanet]

Thanks fuzzy, the maintenance window is already set in the least likely time to record something. However, that isn't quite good enough.

I did figure out one way; but probably not the most elegant method:

1. Set a reoccurring timed recording (4 minute recording) immediately after the maintenance window (4:04am-4:08am). This will cause a scheduling conflict for any favorites, etc that try to use those merit-based devices in that small block of time.

2. Launch a "cleanup" script (which just just finished doing) that deletes these temporary timed recordings after the recordings finish.

Originally Posted by Fuzzy

I think it would be easier to move your maintenance to when the device will not be needed, than to tell sage not to use the device for the period of time. I'm pretty sure some people use SJQ to check for gaps in the recording schedule, for things like system maintenance/reboots.

[Slugger]

With SJQ, you can just write a task that will only launch if there's at least five minutes free before the next scheduled recording starts. There's no need to guess or add manual recordings to lock tuners and then cleanup the timed recordings, etc. SJQ (v4) includes a cron scheduler so you can schedule this job to start daily at, say 4am, and it will not run until it knows there's that free 5 minute block available. Then you just run whatever script/exe you need to do whatever maintenance you're doing and then you're done. There is some learning to be done to make it work, but well worth it, imho.