Auto Update missing from Scheduled Events

[Brian]

I have two HDR-FOX T2 boxes which do not have an Auto Update event listed in webif Scheduled Events. These boxes have not been seen by the RS server since 30th March, and have not been used since then. The front panel clock displays are currently running 9 minutes fast.

I Did install the disable-ota package before the last OTA firmware update, but found out that I wouldn't need it due to the OTA being transmitted from mux 1 (which I don't have tuned into my boxes), so I uninstalled disable-ota. My other boxes are behaving OK, but not these two. How can I restore the Auto Update event on these boxes?

 

[af123]

It should come back of its own accord but I'm not sure what triggers it. It usually takes a couple of days and/or reboots but I don't know exactly.

 

[Brian]

Thanks, the boxes have both been rebooted a number of times since removing disable-ota, but I will try a few more.

 

[Brian]

Three more reboots, and still no change.

 

[af123]

Sorry, I don't know the trigger mechanism. Maybe try changing the schedule if you haven't already?

 

[Brian]

There are no scheduled recordings set, so I will try setting some and rebooting.

 

[prpr]

What exactly are you trying to achieve? You seem not to want auto updates but you want the auto update event. Seems a bit bizarre...

 

[Brian]

What exactly are you trying to achieve? You seem not to want auto updates but you want the auto update event. Seems a bit bizarre...

The standard Auto Update is useful to help keep the clock time, and EPG updated, and also to contact the RS server.

Auto Update has returned on one box following the setting of a scheduled recording, and a reboot. This has not worked with the other box, so will try another reboot when it has finished recording.

 

[Black Hole]

The front panel clock displays are currently running 9 minutes fast.

That is also odd, contrary to existing theory. What does the screen saver clock say?

 

[Brian]

The only reason I can think of for the front panel clock being so wrong, is due to the boxes being in standby for more than a month, with no early morning Auto Update schedule.
I didn't check the screensaver clock, but no doubt that would have been correct due to the boxes being brought out of standby.

 

[Black Hole]

I see, so the time was on the front panel clock with the units in standby.

 

[Brian]

Just an update, the front panel clock on my box without the Auto Update event, had become 2 minutes fast since last Saturday.
I have just brought it out of standby, and it has finally recreated an Auto Update event. Hopefully it is back to normal now, and will keep better time from now on.

 

[Border]

These boxes have not been seen by the RS server since 30th March, and have not been used since then.
s?

Is the network time / box time different after British Summertime kicks in?

 

[Border]

The only reason I can think of for the front panel clock being so wrong, is due to the boxes being in standby for more than a month, with no early morning Auto Update schedule.
I didn't check the screensaver clock, but no doubt that would have been correct due to the boxes being brought out of standby.

There are a few things in the thread I wondered about.

Did the Auto Update schedule stop working after the BST time change? Can sysmon tell what time the box turned on and off after 30/3/14.? Could the front panel clock have been running independent of the network / broadcast time during this standby?