Tweet
We have two THR22s and both have started having incorrect time recently. One is either correct or two minutes late. (Actually 2:04 late, but when it's "correct" it's actually about 4 seconds late.) "Correct" time is from a classic WWV clock, itself accurate to milliseconds.
Manually making it connect to update programming information does not seem to correct the problem.
The other TiVo probably is doing the same thing but once the time error may have been more than 3 minutes.
An old post related to non-DirecTiVos ca 2017-2018 discussed a similar situation - two minute errors - and determined the problem to be a defective TiVo NTP server that the company couldn't bother to repair (over two years!) and the solution was to blacklist that time server at one's gateway. I note today that that time server (sjr1.tivo.com) is working fine (when I looked) as were the supposedly good ones, sjr2 and 3.
Manually making it connect to update programming information does not seem to correct the problem.
The other TiVo probably is doing the same thing but once the time error may have been more than 3 minutes.
An old post related to non-DirecTiVos ca 2017-2018 discussed a similar situation - two minute errors - and determined the problem to be a defective TiVo NTP server that the company couldn't bother to repair (over two years!) and the solution was to blacklist that time server at one's gateway. I note today that that time server (sjr1.tivo.com) is working fine (when I looked) as were the supposedly good ones, sjr2 and 3.
Comment