Anyone else's Series 1 turn the clock back A WEEK EARLY?!?!

My series 1 is packed up now that I have my premiere.

In past years, after congress fooled with Daylight Saving Time, I recall my TiVo clock being "off", but it didn't matter since the guide data was off by the same amount. Everything recorded just fine.

 

OK.. Something must be different this year with the roll back to standard time. When they cut over to daylight time in the spring, did you have issues? I still was using the series 1 then, and had no issues.

It sounds almost like what ever patch was in place was backed out. Because this weekend would have been the weekend to roll the clocks back to standard time.

 

Advertisements

I noticed my series 1 was an hour early when I tried to watch Ghost Lab and instead got an hour of Dirty Jobs. Right now (8:30 Central) it shows 7:30.

I have forced a daily call to see if it corrects itself. It's still processing data...

 

Yeah, my car changed today. I have to manually adjust it for a week or two or three each spring and fall. So obviously today is when it would have changed under the old system.

 

My Series 1 has always changed a week early ( or whatever the orginal days were) I just live with it for a week.

 

Ditto for an atomic clock I have in my bathroom. Sunday 10/31 must have been the "fall back" day before it was changed. It always happens that the clock is off by an hour for a of a week or two each time change. The easy way to fix it is to temporarily change the time zone.

So Gastrof, the issue with your Series 1 is it doesn't have the DST time patch.

 

TiVo sends a "runme" command to each Series 1 to change the time at the start and end of each DST cycle. Mine are packed up but I think it had to reboot. It's possible that it didn't call in recently or that something stopped it from rebooting.

Try forcing a daily call, then restart it. If the time is still off after that I would call customer service.

 

The old rules say the "fall back" was the last Sunday of October. The new rules make it the first Sunday of November (thanks for making us change clocks FOUR times a year...). TiVo series 1 unfortunately fell out of support after the DST rule changes took place (the DST rules have been in place for years... no one really expected the changes).

GPS, "atomic clocks" (WWV/WWVB) and the PBS auto-timeset all have a DST flag embedded in their data streams. The clocks themselves don't do anything other than watch for the flag and adjust if user had enabled DST.

I just wish we could avoid his hassle - pick a time and stick with it.

 

ha ha well i lost service on a lifetime box Even worse than time being off! cant watch t.v. because it wont finish the setup because of issues on tivo's end

Before anyone says well just hook directly up.....
i cant new tv doesnt have the ports necessary to hook up the DTA!~ (thanks comcast)

 

If it says "Loading Data", then the command was successfully received and the Tivo is waiting to automatically reset itself at 2 AM. You can check to make sure it says this on the eve of the old and new DST time changes. If it doesn't say "loading data", force a daily call.

Also, any guided setup that is run this week will have to be run again after next Sunday.

 

Just got into the office and passed it along.

 

Are you making regular service connections to download the patch? If so, what are the affected TSNs?

 

GPS has no DST flag. It's up to the end device to program it correctly.

I think WWVB and PBS do have a DST flag. But I have a clock that ignores it, so I have to manually change the time zones four times a year.

 

We doublechecked the servers and they are sending out the patch. I'm not hearing from other S1 owners so I'm guessing this might be the result of not connecting to the service recently.

 

I resurrected one of my retired SVR2000s, and forced a connection. The time stayed 1 hour off and it sat for several hours at "loading data" so I rebooted it and everything is fine. I assume that it would have rebooted on its own at 2:00am if I had left it alone and didn't have a recording scheduled during that timeframe.

 

You assume correctly.

 

The patch worked for me. I will monitor it this weekend as well.