AltEPG

As we know, at the moment, our TiVos have the time on the box corrected when they do the daily call.

Will the new system have something in place that will allow the time correction to take place, as from experience the clock on my two boxes will drift quite quickly.

Will it also be able to instruct our boxes as to when to perform the switch to and from daylight saving.

Just a thought I had at work this afternoon whilst discussing the TOD changes for next week for our IBM mainframes.

Regards,
Tony.

As I understand it, clock sync is done via standard ntp so I don't see any reason why that can't continue.

I believe that internally Tivo doesn't really care what timezone it's located in: dates and times are specified in the guide data in UTC as days since 1-Jan-1970 and seconds after midnight respectively. So the adjustment for the BST changeover is taken account of in the guide data.

That's correct; TiVo carries on in UTC regardless in its underlying code and guide data, just changing the display dates when it moves in BST. AFAIK, that's handled by the TiVo software. Whatever, it's an issue the OzTivo software should have solved, albeit in reverse!

Time setting is pushed out during the HServer.cgi negotiations. The tivo is told which numeric IP to attempt to time sync with via the NTP protocol. It must be numeric unless you have fixed the broken DNS resolution library (I assume the UK kernel software was also broken) to allow something like ntp.pool.uk. The tivo attempts to fall back to rdate if the NTP call fails, but that only works on a local subnet. After 5 days your box goes into timewarp.

Suggest your server resolve the NTP server du jour from the ntp.pool list into dotted quad notation and supply that in the daily call string.

D.

Just thought I'd bump this thread as the clocks change back to GMT next weekend - if anything needs to be done I assume it's in hand

The way it all works is covered already above. However for me, all guide data times are in GMT on the TVguide system, so it's been a mighty confusing trying to check data in some cases since the start, so I can't wait until the change to GMT .

There are a few issues with gaps in the data for any programme which starts in the first 1am-2am timeslot (the BST one) and following it, the second 1am-2am timeslot (the GMT one). If you look right now you will see the gaps, but we hope to sort them in the next few days.

Tonight on BBC1, according to TiVoWeb I have Panorama starting at 21:30 when it should be 20:30, presumably the time in guide data was provided/specified in GMT rather than something like UTC? The time on my TiVo is correct and has gone back one hour. Unless TiVoWeb is wrong of course...

EDIT: Forget it, it's TivoWeb showing the incorrect details for some reason - checking the programme on the TiVo itself shows the correct 20:30 start time. Phew.

The source data was & is correct - my Panorama todo item is showing up at 20:30? I think there would have been a slew postings yesterday if there was a general problem!

Try forcing a call - if Panorama was originally scheduled for 21:30 GMT but moved to 20:30 GMT and I corrected it and you haven't got the update yet (sorry but I can't remember - I've done a lot of editing since Thursday ish) then that may explain your issue.

Edit after your edit: ah right - yes TiVoweb only checks and set the timezone offset once, when it starts. So when the clocks change you need to do a full restart of TiVoweb. It's annoying in the week before the change when all the future to-do items are obviously wrong!

No, it was my mistake. I had looked at Panorama in the Channel Guide of TivoWeb and it was showing up an hour late, in fact all programmes are showing an hour later than they are on the TiVo itself. I suspect TiVoWeb needs a full restart...

Milhouse wrote:I suspect TiVoWeb needs a full restart...

I know that it does

Edit: lots of cross-over editing going on here

mrtickle wrote:

Milhouse wrote:I suspect TiVoWeb needs a full restart...

I know that it does

Just did a Full Reload, and Panorama is still showing for 21:30... no big deal, I'll reboot the TiVo one of these days.

always fixes it for me ?! Try a "quit" followed by a manual start from bash. There shouldn't be any need to reboot.

Full reload of Tivoweb didn't do the trick for me yesterday either, I needed to reboot Tivo to get everything straight again.

Edit: Just joining in on the edits

mrtickle wrote:always fixes it for me ?! Try a "quit" followed by a manual start from bash. There shouldn't be any need to reboot.

Quitting fixed it - thanks!

Sorry I'm a bit late to the party...

yes you will need to "quit" TivoWeb 1.9.4 and then reload it. (TiVoWebPlus 2.1 should be ok and shouldn't need this).