<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 03/05/2015 10:39 AM, Dan Wilga
wrote:<br>
</div>
<blockquote cite="mid:54F886DA.2030404@dwilga-linux1.amherst.edu"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 2/26/15 1:36 PM, Martin Compton
wrote:<br>
</div>
<blockquote cite="mid:54EF67CB.4040301@itrans.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 02/26/2015 11:14 AM, Jon Heizer
wrote:<br>
</div>
<blockquote
cite="mid:CAF7qfvk_BsmK6MKj=vDCERDJRAh9mqm0gOs0e-fOnDPY1cvB0g@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Feb 26, 2015 at 11:10 AM,
Dan Wilga <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:mythtv-users2@dwilga-linux1.amherst.edu" target="_blank">mythtv-users2@dwilga-linux1.amherst.edu</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">So
I've been tinkering with the upnp interface for my VIP
211k receivers, and I'm pretty sure I've found a way
to turn off the annoying nightly firmware updates that
can't be disabled from the normal UI.<br>
<br>
Make a copy of Jon's original vip211-channellist
script (from <a moz-do-not-send="true"
href="https://github.com/jheizer/UPnPChannelChanger"
target="_blank">https://github.com/jheizer/UPnPChannelChanger</a>)
and replace the call to upnp_send near the end of the
script with this:<br>
<br>
upnp_send $HOST 'Updates'
'<Enable_disable>Disable</Enable_disable>'<br>
<br>
Then, call your edited script, passing it the IP
address of your receiver.
<div class="HOEnZb">
<div class="h5"><br>
_______________________________________</div>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>Do you know the effects of doing this though? I
had debated including it but I never have anything
recording at 3am so I left it. Will you lose new
channel updates? Miss getting access to preview
channels? etc?</div>
<div><br>
</div>
<div>Jon </div>
</div>
</div>
</div>
<br>
</blockquote>
I tried that when the UPnP interface first started showing up:
it did not honor that setting and rebooted at the scheduled time
anyway. Note that in the ViP222k you cannot disable the
automatic updates via the menu, only change the update time. It
is worth testing, though, as that was at least a year ago.<br>
<br>
</blockquote>
Sadly, Martin's report that setting this via upnp didn't help
still seems to be the case, at least on my VIP 211k boxes. The
nightly poweroff still occurs.<br>
<br>
So I'm forced to continue my current hack: I set up each box to do
updates at different times, one at 3:00 AM, the other at 4:00 AM.
Then, I have high-priority recording rules to record something on
each box during the update time period every night. That way,
nothing I care about gets recorded during that time.<br>
</blockquote>
I set mine to reset at 53 minutes past the hour (e.g. 4:53am), that
way it is typically ready to record something at the top of the
hour.<br>
<br>
I should also note that historically, on occasion, the UPnP
interface has disappeared after a reboot. When that happens a
subsequent hard power off (i.e. unplug the device) 'fixes' the
problem. It seems to be occur much less frequently these days, but
early on it was every week or two.<br>
<br>
FYI: I use a sling adapter to connect the ViP222k to the network via
power line (the 222k has it built in), which works fine across my
old UPS.<br>
<br>
Regards,<br>
MC<br>
</body>
</html>