Originally Posted by P Smith
Seems to me, dish finally found a way to stream FW through OTA; the provision does exist - it's just a matter of making a deal with major networks or/and with stations to start broadcasting the FW.
Hmmm... I'd bet against that theory because it would open a can of worms if a network was to do that, as others would want the same deal, plus there are far too many broadcasters to make it practical if that was necessary. But lets test it! I just installed 132R, have tr50.dishaccess.tv
blocked in the router, used the DVR+ menu to check for an update and got Unable to download, unknown error
. Now I'll have to wait to see if the FW update nag appears via OTA, but of course that can take a couple of weeks.
As a side note, since I have tr50.dishaccess.tv
blocked, and the DVR+ gets an error trying to find 134R, that means that 132R only checks one web address for an update.
Progress Report (Stage 1):
I'll update the following report now and then for the next few weeks. If the DVR+ issues an update nag before that, even though the update web address is blocked, I'll finalize the report and make a new post to announce my surprise.
*** Day 14 gone, completing Stage 1 of this test. There were no signs of the DVR+ FW update nag via OTA, and 132R is still running. ***
Note: Stage 1 lasted 14 days without a sign of the DVR+ update nag window in version 132R while alias tr50.dishaccess.tv was blocked in the router. As such, I’ve decided to try to nudge things along by temporarily removing the address blockage until the DVR+ update nag screen makes an appearance. After that, I will reinstate the tr50.dishaccess.tv address block in the router. That way, the DVR+ will have at least been made aware of an update (just in case it is smart enough to remember), and perhaps provoke an attempt to acquire the update from the OTA broadcast stream (if that technology exists in 132R).
Progress Report (Stage 2):
1. After Stage 1, I began Stage 2 by temporarily unblocking alias tr50.dishaccess.tv
in the router, and allowing the DVR+ Internet access. Six hours later the 1st update nag for 134R appeared. Keep in mind that 14 days passed in Stage 1 without a nag, and only 6 hours after allowing Internet access, the update nag appeared. Although the nag window had a Cancel button, I allowed the nag to time out and close itself, after which there was no download progress window. I waited 4 hours before restoring the address block in the router, just to demonstrate that the DVR+ does not download the update unless it's given permission, or until the last update nag (the one without a cancel button) which forces the update. Now it's back to again waiting to see if the update nag reappears even though Internet access to tr50.dishaccess.tv
2. There appears to be a technology named UpdateTV
, which provides software update services via OTA broadcasts over very limited PBS stations. Click HERE
, and HERE
for what little I know. Rabbitears reveals that this service does not exist in my geographic area, so my tests will be inconclusive unless the DVR+ uses some other similar technology. But keep in mind that there are no reports as of June 29, 2017 where a DVR+ owner states an update has occurred on a DVR+ while alias tr50.dishaccess.tv
is blocked. That said, the rabbitears page
was updated on June 26, 2017 to state the following, and that pretty much says it all!
UpdateTV was a service carried on PBS stations which allowed software updates for devices such as TVs and converter boxes to be transmitted over the air. This list is now considered abandoned; most PBS stations have dropped the service.
3. *** Day 14 of 14 for Stage 2 has gone. There were no signs of the DVR+ FW update nag via OTA, and 132R is still running. ***
While the technology to update the firmware of TV related equipment through OTA broadcasts exists (for example, UpdateTV
by Qterics, or methods used by Dish Network on their own network), based upon my 28 day test, in my geographic location, the Channel Master DVR+ does NOT
employ such technology, at least through July 10, 2017 running version 132R, with 134R being the latest version.
Since I am able to test only for my geographic location, there may be those who believe different results might occur in other locals, but keep in mind that there are no reports in this thread of anyone experiencing an update through any means when address tr50.dishaccess.tv
is properly blocked in the router used by the DVR+. Anyone with evidence to the contrary, please make a report in this thread.
Another question that may come up is that 134R was released on 5/10/2016 (14 months ago), so maybe the update is no longer broadcast OTA. Well, that would never do since new purchases rarely come with the latest version. To be beneficial, the broadcast would have to continue at least until all of CM stocked units are flashed with the latest version. That will still not take care of purchased boxes that are not powered for long periods of time (for example, a vacation home or camper, or whatever reason you can imagine). So I’ll stick with my initial reaction that with an Internet connected device, updating via OTA broadcast is very impractical, and I suspect too costly and burdensome.
Note: Shortly after this test concluded, I unblocked address tr50.dishaccess.tv
in the router to see how long it would take for the update nag to appear. It did so about 6 hours later. Interestingly that nag was very close to the same time of day as the period between Stage 1 and Stage 2. The next nag was 6 hours later. The DVR+ was put into Standby Mode until the next morning when another nag about 10AM. The next was 2 hours later, and it was the nag without the buttons, which meant it was the forced update nag. So, in less than 24 hours after unblocking tr50.dishaccess.tv
, the DVR+ insisted upon an update, something that the speculated OTA update method did not do in 28 days.