Reply to thread

Message: <blockquote data-quote="HTPCSourcer" data-source="post: 1163103" data-attributes="member: 74879">I did not have time to work on the receiver-selective devcon remove process yet.But something strange happened tonight: As I had resume issues in the past, I have been working with [USER=60104]@Sebastiii[/USER] who has successfully added code to MP to address those issues. Indeed MP woke up without problems this morning, following a multi-hour standby. To my surprise the IR receiver was working <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite26" alt=":unsure:" title="Unsure    :unsure:" loading="lazy" data-shortname=":unsure:" />. I am not 100% certain, but thus far the receiver has always been dead after the night standby.The system in question (HTPC1) is entering standby when forced by MP. For some reason, if left to Windows, the PC would not enter standby while MP is running - it does though without MP. The particularity in my environment is that every night between 4:00 and 5:00 the Windows Server 2012 system is subsequently waking up each client in my network to perform a backup operation. For reasons of quicker testing I had set the forced standby time to 3 min - probably too short to allow for the server backup process to be completed - and in the last days I was always greeted by a message on the client that the backup process had not been succesful. In order to address this I increased the forced standby time to 10 min yesterday, and the server backup did complete this night.I will observe this over the next days to see if the receiver behavior is stable or if this has just been a coincidence. While the standby time between the client shutting off after the backup (say 4:15) and my current in-the-morning test resume at 7:00 is more or less the same (roughly 3 hours), the time of standby beween shutting off in the previous evening and the backup wake differs. Yesterday with Europe League I switched off at around 23:30 - or ca. 5 hrs of standby time.It sounds completely bizarre, but the receiver stopping to work appears to be subject to the time of the PC being in standby. That said, I have read reports of people stating that the receiver stopped working during the process of entering standby. In my case I never managed to confirm this: manually standby'ing the PC and then waking it up again shortly after never led to the remote not working anymore.</blockquote>

Verification