Is anyone else's clock off?

[dishrich]

OK, when I first got the Hopper, the clock was already very accurate; I never had issues with recordings starting late & never gave it a thought. (& hence, I never padded start times on normal, daily shows, especially if you are doing back-to-back shows) But as of the last few months, the clock on all my Ho's is usually off, by more than a minute or two. Sometimes after a nightly update, they'll get back to being correct...but that only lasts a day or two max, then it's right back to being off again. I KNOW it's clock is off, because I've compared with other sources, & all are in synch except the Ho's.

This is crazy; I have never had this with any other DVR, including ANY previous E* units...

 

[TommyF@DISH Network]

I don't show any known issues, and wasn't able to really locate any troubleshooting on that outside of trying a reset. I can forward a report to our operations team for you though. Can you please PM me the account or phone #?

 

[Bobby]

The clock on my Hopper has been rock steady and right on since March, 2012....

 

[KAB]

The clock on my Hopper has been rock steady and right on since March, 2012....

Same here. This one is a first to me.

 

[Jim S.]

I haven't looked at the time on my Hopper lately, as I'm hopelessly behind in watching my shows, but I remember a long time ago there were times when the clock on my 622 was off by a few minutes.

 

[Brussam]

The Hopper clock has been so accurate, we set the other clocks to it besides the clock that used the National Time Service. It matches the Hopper.

 

[charlesrshell]

I noticed last week I had an issue a couple of days with recordings starting late. Maybe there was some Hopper hiccups for some reason and they are now back on track.

 

[Hall]

The Hopper clock has been so accurate, we set the other clocks to it besides the clock that used the National Time Service. It matches the Hopper.

TV providers almost have to sync their clocks with the Naval atomic clock in order to make sure everything "lines up". As you're doing, using the Hooper's clock should normally be a very good reference.

 

[KAB]

I noticed last week I had an issue a couple of days with recordings starting late. Maybe there was some Hopper hiccups for some reason and they are now back on track.

Or perhaps the channel started the program early. It does happen.

 

[Hall]

Do any shows start "on time" now ?

 

[Bobby]

Not really...

 

[Tampa8]

OK, when I first got the Hopper, the clock was already very accurate; I never had issues with recordings starting late & never gave it a thought. (& hence, I never padded start times on normal, daily shows, especially if you are doing back-to-back shows) But as of the last few months, the clock on all my Ho's is usually off, by more than a minute or two. Sometimes after a nightly update, they'll get back to being correct...but that only lasts a day or two max, then it's right back to being off again. I KNOW it's clock is off, because I've compared with other sources, & all are in synch except the Ho's.

This is crazy; I have never had this with any other DVR, including ANY previous E* units...

Is your guide fully up to date? (About 8 days out?) Noticed any problems with the hard drive or not getting channels?

 

[Hall]

Not really...

I've been with Dish since 2005 and even then, the DVRs were already defaulting to starting early and ending late because of the shows not starting when they're scheduled to.

 

[adkinsds]

Mine is 1 minute behind compared to the atomic clock and cell phone... It started after s523 update. After reboot it's right but by the next evening it's off by a minute again.

 

[dlmcmurr]

My new HWS that I just plugged in yesterday afternoon is 1:25 behind my "atomic" clock. Ironically, my H2K is only 0:25 behind.

 

[Grandude]

My Hopper with sling is 5 seconds behind my atomic clocks.
Not sure of the time required for the signal from Dish in Colorado to travel to the satellite and back down to Santa Rosa, CA.

 

[Hall]

Dish knows the "travel" time and likely compensates for it.

A few people have mentioned it now and it appears that this issue just started with the last software update to the HWS and the older Hopper isn't affected.