Wake from sleep recording issues

[clemon79]

Glancing through the forums, this looks like a combination of things that could be going on, but I could use some help on how to attack it.

Just recently I finally packed it in on Windows Media Center under Windows 7 and moved to NextPVR full time. Here's the config in a nutshell:

Windows 10 Pro
NextPVR 5.2.6.220206
HDHomerun Prime
Kodi 19.4 (as a front-end; not relevant to this issue)

And here's the problem: I do have the system set to sleep when it's not in use, and it wakes before recording something. For an IPTV channel I record this has never been a problem but I seem to be having an issue with the HDHR, especially with regard to recording sporting events.

Here are the errors, which you will find familiar:

FAILED Detroit Red Wings at Seattle Kraken: From Climate Pledge Arena in Seattle.
[Failed: Recording service not running at recording time]

then, on the reair:

FAILED Detroit Red Wings at Seattle Kraken: From Climate Pledge Arena in Seattle.
[Failed: A socket operation was attempted to an unreachable host. A socket operation was attempted to an unreachable host.]

Presumably the latter was a function of the former taking a dive the first time, but I dunno.

So. The service is set to "delayed start"; set it to regular "automatic" or will that make things worse? I'm also thinking the best way to alleviate this problem is simply to have the system wake a few minutes sooner so everything is in place to roll when it's time, but I can't seem to find a setting for that. Is there one?

Logs are attached if they are helpful. Appreciate it!

-- Chris

[mvallevand]

NextPVR did wake for the first recording, but likely the hidden Windows inactivity sleep setting put it back to sleep.

Delayed start is normally good to ensure that the network is up when the server restarts but it doesn't get involved in resume.

It is not clear why the system even resumed at 2am possibly you manually woke it. In any case NextPVR saw the missed recording and immediately tried to record the replay that started at 1am. I would suspect the immediate recording (normally NextPVR would wake before the recording) was before the network was up.

Martin

[clemon79]

NextPVR did wake for the first recording, but likely the hidden Windows inactivity sleep setting put it back to sleep.

I don't follow. It was inactive on its own, it went to sleep, hours later it is awoken to record something at which point it is active again so a) there's no reason for it to go back to sleep for at least a half hour and b) it's going to be actively recording anyhow so it's not gonna sleep until the recording ends. I know THAT part works.

It is not clear why the system even resumed at 2am possibly you manually woke it.

It wakes at 2 for another scheduled task for an XMLTV listings update that is used by other devices. That's a totally expected wake-up.

In any case NextPVR saw the missed recording and immediately tried to record the replay that started at 1am.[/quote]

Right, I get that part. I'm assuming that one bombed because the service was all screwed up from whatever happened the first time when it crapped out. The last time this happened, all subsequent recordings failed until the next time I manually woke the machine. So the trick is addressing that first failure and making it not happen, and it seems the key is making the machine wake well enough in advance that everything has time to get itself woken and restarted and connected with each other so that when the recording wants to start, the system's ready for it. So I'm thinking if I can set it to wake, say, 5 minutes before the recording is scheduled to start instead of whatever it's doing now (I'm guessing 1 minute), then that should be plenty of leeway. So I need to know if I can somehow make that happen.

[clemon79]

In fact, maybe I found it? In config.xml, I see a setting for "WakeupPreRecordingSeconds", set to 30, which seems way too low. So a) is this it, b) if so, is there a place I can edit it in the UX, and c) if the answer to (a) is "yes" and (b) is "no", will it harm anything if I manually edit that to 300?

EDIT: Okay, found it in the docs. Turns out the default is supposed to be 90, so I would LOVE to know how mine got to be 30. I'll be fixing that.

[mvallevand]

Right but there is also a somewhat hidden Windows setting that will put the PC back to sleep if there is no activity that you need to find since I don't feel like searching for it.

I actually think the service was fine, it was just trying to record before networking, normally recording is not normally immediate. There is a track error that sub might to look into though.

NextPVR does have a nasty habit of disabling the HDHR if it can't connect on startup so I would turn off the scan for tuners on startup.

30 seconds is the default, I don't think there is any v5 documentation for this.

Martin

[sub]

Obscure settings like that aren't shown in the UX.

You can change it. It's best to not have it set to too long before the recording is due to start because sometimes Windows power management decides nothing is going on and puts the machine back to sleep.

FYI, NextPVR never puts a machine to sleep - it only asks Windows to be awake at a specific time.

[BrettB]

NextPVR did wake for the first recording, but likely the hidden Windows inactivity sleep setting put it back to sleep.

I don't follow. It was inactive on its own, it went to sleep, hours later it is awoken to record something at which point it is active again so a) there's no reason for it to go back to sleep for at least a half hour and b) it's going to be actively recording anyhow so it's not gonna sleep until the recording ends. I know THAT part works.

I believe that what Martin is referring to is the system unattended sleep setting which defaults to 2 minutes.

Code:

The System unattended sleep timeout power setting is the idle timeout before the system returns to a low power sleep state after waking unattended. System unattended sleep timeout is set to two minutes and not available to change in Power Options by default in Windows.

When it wakes for the recording from the first recording wake timer, if that is more than the system unattended sleep timeout seconds before the recording will actually begin and there is nothing else to keep the server awake, then it will go back to sleep before the recording begins. And, what seems to happen is then it is still in the process of going back to sleep when the second/backup wake timer hits and Windows ignores it since it is not yet fully asleep at that point. The result is that the server is indeed in sleep mode when the recording is actually scheduled to begin.

[clemon79]

I believe that what Martin is referring to is the system unattended sleep setting which defaults to 2 minutes.

Code:

The System unattended sleep timeout power setting is the idle timeout before the system returns to a low power sleep state after waking unattended. System unattended sleep timeout is set to two minutes and not available to change in Power Options by default in Windows.

Gotcha. A quick search found how to surface that, and now it's available to change and set to 3 minutes to match what I have WakeupPreRecordingSeconds set to, so that shouldn't get in the way. Hopefully this does the trick.

[EDH]

I too am having difficulty wiith recordings not happening when a wake timer is involved.  (I have set up NPVR up on 5 computers over the years and never encountered this particular issue.)

There are two double channel Silicon Dust HDHomeRun tuners (model HDHR-3US) on the network.  The tuners are accessed by a number of laptops and NPVR works fine. On a new laptop, scheduled NPVR recordings do not happen if the computer is asleep.  Same with EPG updates although sometimes they work if the computer is awake for other things.  I can manually update the EPG in NPVR and recordings happen if the computer is awake at the time of the recording. 

The new laptop woth NPVR issues is a Dell Inspiron 15 Model 5510 with Windows 11, 500g SSD, i7 processor and 12 gig of memory with both wireless and Ethernet LAN connections.  It only has sleep state S0. The logs seem to indicate that the wake timer has worked but NPVR does not make the recording (or update the EPG). 

I have tried the following, none of which resolved the issue:
- Checked presence of timers in powercfg /waketimers (yes they scheduled recording times were there)
- Removed and reinstalled the wireless and LAN devices
- Reset network in Windows 11 settings troubleshooters
- Turned off power saving for the PCI Express buss as the wireless adapter uses it
- Set pre and post times to 0 or 1-2 minutes
- Tried both wireless and wired LAN connections (note wired ethernet lights continue to glow when computer is asleep)
- Increased Unattended Sleep Timer to 5 minutes

I would appreciate a hand at resolving this issue.  Logs are attached.

[mvallevand]

We can't really help with sleep issues because Windows controls that not NextPVR, You will need to send the logs.

Sleep state S0 isn't really sleep though, that means it is a on. Check your BIOS for real sleep modes.

Martin