I have just noticed that all my scheduled IceTV timers that are set for January the 1st and after have been incremented by an hour.
Has anyone else noticed this?
For example, I record the 6pm Seven news program each night. The timers scheduled for between today and the 31st of December are OK and are set for 18:00 as expected, however the timers from the 1st of January are now being set for 19:00.
Another example is the 3 episodes of the X-files scheduled for next Saturday as per the following screen capture.
Here it can be seen that the first episode of X-Files is being missed and a timer has been set for the 23:30 episode of Black Ops.
Quote from: fastcars on December 27, 2015, 02:01:22 PM
I have just noticed that all my scheduled IceTV timers that are set for January the 1st and after have been incremented by an hour.
Has anyone else noticed this?
Hmm. Interesting. I have not got this problem, however, also starting on the 1st, the random single recordings have started again. However, all these single recordings showing on the IceTV page as being set for the Wiz, do
not show up on the Wiz. I have no idea what that means. Also have (other) blank recordings set on the Wiz (before the 1st)
Quote from: csutak40 on December 27, 2015, 02:45:00 PM
Hmm. Interesting. I have not got this problem, however, also starting on the 1st, the random single recordings have started again. However, all these single recordings showing on the IceTV page as being set for the Wiz, do not show up on the Wiz. I have no idea what that means. Also have (other) blank recordings set on the Wiz (before the 1st)
Mine is exactly the same as yours, set timers are on correct times but I have several random single timers that I did not set. They're all on the T4 but not on the T3.
I too have random single timers on my T3 from 1st January.
Actually, my random timers are all for shows that are on an hour earlier, and all of those are shown with grey icons unless they are longer than an hour.
Quote from: simoncasey on December 27, 2015, 07:57:54 PM
Actually, my random timers are all for shows that are on an hour earlier, and all of those are shown with grey icons unless they are longer than an hour.
My timers from the 1st of January onwards are actually being set for the show that is 1 hour after the program that I want recorded.
Quote from: fastcars on December 27, 2015, 08:16:22 PM
Quote from: simoncasey on December 27, 2015, 07:57:54 PM
Actually, my random timers are all for shows that are on an hour earlier, and all of those are shown with grey icons unless they are longer than an hour.
My timers from the 1st of January onwards are actually being set for the show that is 1 hour after the program that I want recorded.
We seem to be seeing the same issue. Where are you, in case it is just region related? I'm in melbourne.
I'm seeing the same thing in Canberra, so not regional.
I'm in Sydney
Quote from: simoncasey on December 27, 2015, 09:15:38 PM
Quote from: fastcars on December 27, 2015, 08:16:22 PM
Quote from: simoncasey on December 27, 2015, 07:57:54 PM
Actually, my random timers are all for shows that are on an hour earlier, and all of those are shown with grey icons unless they are longer than an hour.
My timers from the 1st of January onwards are actually being set for the show that is 1 hour after the program that I want recorded.
We seem to be seeing the same issue. Where are you, in case it is just region related? I'm in melbourne.
I'm in Melbourne too
Mine are all OK on the Sunshinecoast (Including Brisbane Channels).
In some detail:
I have 5 min pre-padding and 25 min post-padding, Beyonwiz T4, beta firmware 2015-12-23.
On 1 Jan:
Series recording for Better Homes and Gardens (Prime7 19:00-20:30) is showing up as a timer on our T4 set for 19:55-21:55 (should be 18:55-20:55 with padding), and that is reflected in My Week as a one-off recording for Movie: As Good as it Gets (20:30-23:25).
Series recording for Escape To The Country (7TWO 21:30-22:30) is showing up as a timer set for 22:25-23:55 (should be 21:25-22:55 with padding) and is reflected in My Week as a one-off recording for Storage Hoarders (22:30-23:30).
Series recording for New Year's Day Concert '2016' (SBS 23:30-02:20) is showing up as a timer set for 00:25-03:45 (should be 23:20-20:55 with padding) and is reflected in My Week as a one-off recording for Shameless (02:20-03:25).
The timers are all being set one hour later than they should be, and the same pattern is reflected in all IceTV timers that have been set so far on 2 Jan and 3 Jan.
If anyone's home at IceTV, could they please look into this problem?
Quote from: mac37 on December 28, 2015, 05:05:44 PM
Mine are all OK on the Sunshinecoast (Including Brisbane Channels).
I'm beginning to think that IceTV is treating everywhere as not being on daylight savings time from 1 January. January, apparently, is the new April, and 1 January is now 1 April ;).
Are Adelaide users seeing timers off by 30 min from 1 Jan?
Quote from: prl on December 28, 2015, 05:11:43 PM
I'm beginning to think that IceTV is treating everywhere as not being on daylight savings time from 1 January. January, apparently, is the new April, and 1 January is now 1 April ;).
That's what I'm thinking too, it was the same thing that occurred around the start of daylight savings time back in October.
My T3 has firmware dated 2015-12-23 01:58
Except that 1 January isn't around the start (or end) of daylight savings time. :(
Quote from: prl on December 28, 2015, 05:51:20 PM
Except that 1 January isn't around the start (or end) of daylight savings time. :(
Correct! ;)
Just to confirm that Adelaide is an hour out too from 1 January - my T2 wants to record everything an hour after IceTV says it's on.
(I'm not sure why prl wants Adelaide to be 30 mins out rather than an hour out - our hour of time zone difference from the east is confusing enough, without only adjusting half an hour for daylight savings ... although I guess if we had a half-hour adjustment for daylight savings it would make sure that absolutely everyone gets upset, the ones who want us to switch to eastern time, the ones who want us to stay as is, AND the ones who want us to be an hour the other way. A perfect system, loathed equally by all.)
Quote from: prl on December 28, 2015, 05:08:01 PM
In some detail:
I have 5 min pre-padding and 25 min post-padding, Beyonwiz T4, beta firmware 2015-12-23.
On 1 Jan:
Series recording for Better Homes and Gardens (Prime7 19:00-20:30) is showing up as a timer on our T4 set for 19:55-21:55 (should be 18:55-20:55 with padding), and that is reflected in My Week as a one-off recording for Movie: As Good as it Gets (20:30-23:25).
If anyone's home at IceTV, could they please look into this problem?
Yeah, now that I had a better look, mine are exactly the same
Quote from: tjcurnow on December 28, 2015, 06:00:24 PM
... I'm not sure why prl wants Adelaide to be 30 mins out rather than an hour out - our hour of time zone difference from the east is confusing enough, without only adjusting half an hour for daylight savings ... although I guess if we had a half-hour adjustment for daylight savings it would make sure that absolutely everyone gets upset, the ones who want us to switch to eastern time, the ones who want us to stay as is, AND the ones who want us to be an hour the other way. A perfect system, loathed equally by all.
I don't know why prl said it either. He might have said he got it confused with Lord Howe Island, which is not only in a half-hour standard time zone (+10:30), but also has a 30-minute shift for DST. However, they don't have any FTA TV.
Quote from: prl on December 28, 2015, 05:11:43 PM
Quote from: mac37 on December 28, 2015, 05:05:44 PM
Mine are all OK on the Sunshinecoast (Including Brisbane Channels).
I'm beginning to think that IceTV is treating everywhere as not being on daylight savings time from 1 January. January, apparently, is the new April, and 1 January is now 1 April ;).
Yep, I was about to post exactly the same thing... Opened up 'My Week' and said 'Oh, not again'.
....and have several series recordings showing as 'queued' that are only a few days away (i.e. Jan 1 or later). Curiously, other series recordings scheduled as late as next Monday are fine.
I'm having the same problem in Sydney. Today is the first post-Christmas working day for many. Hopefully that includes someone at IceTV.
Quote from: digmans on December 29, 2015, 09:16:48 AM
I'm having the same problem in Sydney. Today is the first post-Christmas working day for many. Hopefully that includes someone at IceTV.
IceTV support is closed until 4 Jan. We can only hope yhat Faniel sees this and acts on it before Friday.
I'm only seeing this problem on our Beyonwiz T4, not on our DPs. Is it a problem with the new server? Is anyone seeing it on any devices not on the new server (i.e devices other than Beyonwiz T series and perhaps SKIPPA?
Quote from: prl on December 29, 2015, 09:25:26 AM
I'm only seeing this problem on our Beyonwiz T4, not on our DPs. Is it a problem with the new server? Is anyone seeing it on any devices not on the new server (i.e devices other than Beyonwiz T series and perhaps SKIPPA?
I am also using Toppy 5k (still :-[) and that is fine and so is Windows 7 Media Center
Just to re-iterate.
Sunshinecoast (including retransmitted Brisbane) Channels are all scheduled correctly for January programs.
This is the case for Topfield, Humax and Beyonwiz T2. ;D
Quote from: mac37 on December 29, 2015, 11:53:53 AM
Just to re-iterate.
Sunshinecoast (including retransmitted Brisbane) Channels are all scheduled correctly for January programs.
This is the case for Topfield, Humax and Beyonwiz T2. ;D
I think that's why prl suggested it could be a daylight savings issue as the only people affected seem to be in those states that have daylight savings. It doesn't seem to be an issue in WA as I'm sure tezza would have posted by now.
Hi Guys,
I am having a look at this one now, not 100% sure where the problem lies though as it's not affecting all users on T series Beyonwiz's, and at a first glance I can't see any SKIPPA users that are reporting an issue (these are the only PVR's on the new API).
Will report back shortly.
Thanks Daniel for the update.
Quote from: kazz on December 27, 2015, 05:16:23 PM
They're all on the T4 but not on the T3.
kazz, what software versions are on your T4 and on your T3? Go to "Menu > Information > About" then note the "Last Upgrade"
fastcars' T3 has firmware dated 2015-12-23 01:58 and it has the issue. My T4 has firmware dated 2015-12-23 01:50 and it has the issue. So T3 and T4 firmware dated 2015-12-23 has the issue.
It seems like the recent (latest?) T series software has reset daylight saving time after the start of 2016. It is like it has forgotten that daylight savings has already started and is still in effect. Thus why QLD (and WA) people who don't have daylight savings are not experiencing the issue. It is the same result as the issue that occurred around the start of daylight saving time back in October.
Hi Guys,
It looks like there was a small logic loophole in the daylight savings calculations in the start of a new year in the new API. A fix has been rolled out for it and the system is going through now and re-scheduling any shows for the coming week so all incorrect timers should be updated to the correct ones within the next couple of hours.
Thanks, Daniel.
Thanks Daniel, but under to quote Mr Fraser, life wasn't meant to be easy. Seems (for mine) it is mostly fixed, but it seems Chl 31 is still out by an hour. I don't understand how this is possible, but it is the case.
Before I noticed that, I also noticed that most of the random single timers have disappeared, but (again) not all of them. In fact, I suspect that these are new ones. There are only a few of them, but they are there, non the less.
Also (and I am not sure if this is a separate issue, or connected) I also have some blank timers. Agaun, not many... The first one is today
I've made screen shots of them all, I have one too many, will attach it next post
P.S. to the previous post ;)
Hmm. To complicate matters. Having another look at this screenshot, there is another timer for Channel 31, for Monday morning and that is not out by an hour! Now I am really confused!
Incidentally, forgot to mention; my T4 has firmware dated 2015-12-23 01:50
It looks like the problem has been fixed for me (Canberra guide, Beyonwiz T4).
All fixed for my T2 in Adelaide. Thanks Daniel, you can go back to being on holiday now ;)
Tim
Quote from: Dave at IceTV on December 29, 2015, 01:49:09 PMIt seems like the recent (latest?) T series software has reset daylight saving time after the start of 2016. It is like it has forgotten that daylight savings has already started and is still in effect. Thus why QLD (and WA) people who don't have daylight savings are not experiencing the issue. It is the same result as the issue that occurred around the start of daylight saving time back in October.
Could you please clarify if this phenomenon, if caused by the "recent (latest?) T series software", applies to timers set in the T series from the OTA EPG? It doesn't look like it to me. If it doesn't, then should we perhaps suggest that the phenomenon is confined to timers set from the IceTV plugin?
I can confirm that all my IceTV scheduled timers are now ok.
Thanks Daniel and Dave @ IceTV for your resolution to this issue.
Well, my weird problems remain. Am I the only one left now with the missing and random single timers?
Quote from: raymondjpg on December 29, 2015, 07:29:09 PM
Quote from: Dave at IceTV on December 29, 2015, 01:49:09 PMIt seems like the recent (latest?) T series software has reset daylight saving time after the start of 2016. It is like it has forgotten that daylight savings has already started and is still in effect. Thus why QLD (and WA) people who don't have daylight savings are not experiencing the issue. It is the same result as the issue that occurred around the start of daylight saving time back in October.
Could you please clarify if this phenomenon, if caused by the "recent (latest?) T series software", applies to timers set in the T series from the OTA EPG? It doesn't look like it to me. If it doesn't, then should we perhaps suggest that the phenomenon is confined to timers set from the IceTV plugin?
I don't know of any problem with DST in the latest Beyonwiz T series firmware (and by latest I mean the 2015-12-23 01:58 beta firmware): after all, they continued displaying the correct times for the EPG. Daniel's post about the problem (http://forum.icetv.com.au/iceforum/general-discussions/1/icetv-timers-set-for-and-after-jan-1st-are-being-incremented-by-1-hour/4899/msg25845#msg25845) and its fix reads to me that the problem was in the IceTV servers that provide the data to the Beyonwiz T series and that it was fixed by a fix on the servers. There was certainly no Beyonwiz firmware update that fixed the problem.
Quote from: prl on December 30, 2015, 09:50:01 AMDaniel's post about the problem (http://forum.icetv.com.au/iceforum/general-discussions/1/icetv-timers-set-for-and-after-jan-1st-are-being-incremented-by-1-hour/4899/msg25845#msg25845) and its fix reads to me that the problem was in the IceTV servers that provide the data to the Beyonwiz T series and that it was fixed by a fix on the servers. There was certainly no Beyonwiz firmware update that fixed the problem.
Yes. That post does indicate to me that the problem was with the IceTV servers. Maybe it was posted while I was responding to the previous post by Dave at IceTV. Maybe it was already there. In any case Dave's post was what alarmed me. As it happens there would appear to be no problem with the Beyonwiz firmware update nor any need to fix a problem that did not exist at the BW end.
Everything is now good for my Beyonwiz T3 in Sydney.
Quote from: simoncasey on December 29, 2015, 12:02:50 PM
It doesn't seem to be an issue in WA as I'm sure tezza would have posted by now.
Huh? wah? Did I miss something? ;D
Quote from: prl on December 30, 2015, 09:50:01 AM
Quote from: raymondjpg on December 29, 2015, 07:29:09 PM
Quote from: Dave at IceTV on December 29, 2015, 01:49:09 PMIt seems like the recent (latest?) T series software has reset daylight saving time after the start of 2016. It is like it has forgotten that daylight savings has already started and is still in effect. Thus why QLD (and WA) people who don't have daylight savings are not experiencing the issue. It is the same result as the issue that occurred around the start of daylight saving time back in October.
Could you please clarify if this phenomenon, if caused by the "recent (latest?) T series software", applies to timers set in the T series from the OTA EPG? It doesn't look like it to me. If it doesn't, then should we perhaps suggest that the phenomenon is confined to timers set from the IceTV plugin?
I don't know of any problem with DST in the latest Beyonwiz T series firmware (and by latest I mean the 2015-12-23 01:58 beta firmware): after all, they continued displaying the correct times for the EPG. Daniel's post about the problem (http://forum.icetv.com.au/iceforum/general-discussions/1/icetv-timers-set-for-and-after-jan-1st-are-being-incremented-by-1-hour/4899/msg25845#msg25845) and its fix reads to me that the problem was in the IceTV servers that provide the data to the Beyonwiz T series and that it was fixed by a fix on the servers. There was certainly no Beyonwiz firmware update that fixed the problem.
Yeh. I hadn't updated the firmware on my T4 for a week or two, so I didn't have the 23/12/15 FW, but I did have the IceTv scheduling problem. And, it was fixed when Daniel and the guys changed stuff at the IceTv end.
I think the attribution above should be:
Quote from: mkwilson on January 01, 2016, 10:22:33 AM
Quote from: prl on December 30, 2015, 09:50:01 AM
Quote from: raymondjpg on December 29, 2015, 07:29:09 PM
Quote from: Dave at IceTV on December 29, 2015, 01:49:09 PMIt seems like the recent (latest?) T series software has reset daylight saving time after the start of 2016. It is like it has forgotten that daylight savings has already started and is still in effect. Thus why QLD (and WA) people who don't have daylight savings are not experiencing the issue. It is the same result as the issue that occurred around the start of daylight saving time back in October.
Could you please clarify if this phenomenon, if caused by the "recent (latest?) T series software", applies to timers set in the T series from the OTA EPG? It doesn't look like it to me. If it doesn't, then should we perhaps suggest that the phenomenon is confined to timers set from the IceTV plugin?
I don't know of any problem with DST in the latest Beyonwiz T series firmware (and by latest I mean the 2015-12-23 01:58 beta firmware): after all, they continued displaying the correct times for the EPG. Daniel's post about the problem (http://forum.icetv.com.au/iceforum/general-discussions/1/icetv-timers-set-for-and-after-jan-1st-are-being-incremented-by-1-hour/4899/msg25845#msg25845) and its fix reads to me that the problem was in the IceTV servers that provide the data to the Beyonwiz T series and that it was fixed by a fix on the servers. There was certainly no Beyonwiz firmware update that fixed the problem.
Yeh. I hadn't updated the firmware on my T4 for a week or two, so I didn't have the 23/12/15 FW, but I did have the IceTv scheduling problem. And, it was fixed when Daniel and the guys changed stuff at the IceTv end.
;)
I think I have sort of figured something out, but not being a programmer, I don't understand the reason.
If you look at this post of mine
http://forum.icetv.com.au/iceforum/general-discussions/1/icetv-timers-set-for-and-after-jan-1st-are-being-incremented-by-1-hour/4899/msg25850#msg25850 (http://forum.icetv.com.au/iceforum/general-discussions/1/icetv-timers-set-for-and-after-jan-1st-are-being-incremented-by-1-hour/4899/msg25850#msg25850) the first screen shot there, there is a timer there that is an hour out.
I have since deleted that timer manually, as that was the only way I could get the correct timer to generate (disabling and re-enabling the IceTV plug in didn't fix it.
Sooo, looking at "MyWeek" I noticed that I still have random timers. I made a screen shot (edited, only leaving the random timers) then went to check on the t4 to see if these timers are there.
That's when I discovered something.
The random timers correspond with a problem on the T4 (there being two timers for the one show, one being an hour out) In the second instance, the random timer remains, even though I have manually deleted the wrong timer from the T4. In fact, in that instance, the correct timer refused to generate until I manually deleted the incorrect one, which is not the case with the Saturday timer (see attached)
So, I hope that someone with more knowledge than I have can understand the reason for this and if there is a fix. Sure, I can delete the second timer again, but I still don't understand what causes the random timers and how to get rid of those
I think the first recommendation is don't delete IceTV timers on the T4. You should only delete them on IceTV. If you delete them on the T4, then IceTV will treat that as you saying you don't want to record that episode, and wont resend them back again.
It would be good to see what the corresponding my week looks like on IceTV so the different timers can be reconciled and to see of they are single recordings that have come from the T4 or part of a series recording.
Once cause for the current issue could be that when we had the problem with the IceTV timers being out by an hour, you tried to correct that by deleting and adding timers directly on the T4 and now that it has been resolved, there are still a number of extra single episode timers that are still hanging around from that problem.
Quote from: simoncasey on January 01, 2016, 07:57:37 PM
I think the first recommendation is don't delete IceTV timers on the T4. You should only delete them on IceTV. If you delete them on the T4, then IceTV will treat that as you saying you don't want to record that episode, and wont resend them back again.
It would be good to see what the corresponding my week looks like on IceTV so the different timers can be reconciled and to see of they are single recordings that have come from the T4 or part of a series recording.
Once cause for the current issue could be that when we had the problem with the IceTV timers being out by an hour, you tried to correct that by deleting and adding timers directly on the T4 and now that it has been resolved, there are still a number of extra single episode timers that are still hanging around from that problem.
Ok I don't think I explained myself properly.
One of the shows out by an hour was the Hungarian show on Chanel 31 on Sunday at 4.30 pm. It was showing as 5.30 There were also lots of random recordings (some before the 1st Jan)
When IceTV fixed the problem, that Hungarian program didn't get fixed, remained at 5.30 (albeit without a name) I noted that most of the random recordings also disappeared with the fix, but also noted that lots of programs (before and after the 1st) lost their names.
So, in an attempt to fix that program, I reloaded the IceTV plugin, but that didn't fix it. So, I deleted the incorrect timer and reloaded it again. That did fix that one timer; it created the correct timer. I did notice that the blank timers remained blank, but TBH, I didn't look at individual shows that closely.
Yesterday, I noticed that another Hungarian program (this time on SBS) that is supposed to be on at 8am Saturdays, had the correct timer set, but it also still had the incorrect one at 9am as well. That is when I discovered that the random recording in "MyWeek" clashed with that incorrect timers.
On looking further, I discovered that the second random recording clashed with Sunday's incorrect timer, even though I had already deleted it.
I did send screen shots of all these, but here they are again, hopefully more clearly. Hmm, maybe not so clearly, had to reduce them in size, to get them to fit.
I did not delete the incorrect timer for Saturday, want to see what will happen
Ok, I will have to send the screenshot separately, for some reason it insists that they are too large, even though I have definitely reduced them to under 300kb
Here are the attachments that are meant to be with the post above
Just checked - both the correct and the incorrect timer recorded this morning (not the random timer though)
Quote from: csutak40 on January 02, 2016, 07:44:27 PM
Just checked - both the correct and the incorrect timer recorded this morning (not the random timer though)
I noticed this with the last wiz a lot, that if icetv sent a wrong timeslot and subsequently fixed it, that the system never deleted the original mistake so that you ended up with two timers (assuming no overlap which wasn't allowed on the older wiz series). I just wonder if this is what happened here as i had a few random timers that were near what i was expecting to record?
Quote from: tonymy01 on January 03, 2016, 10:40:19 AM
Quote from: csutak40 on January 02, 2016, 07:44:27 PM
Just checked - both the correct and the incorrect timer recorded this morning (not the random timer though)
I noticed this with the last wiz a lot, that if icetv sent a wrong timeslot and subsequently fixed it, that the system never deleted the original mistake so that you ended up with two timers (assuming no overlap which wasn't allowed on the older wiz series). I just wonder if this is what happened here as i had a few random timers that were near what i was expecting to record?
That must be what happened.