IceTV Forum

IceTV Guide for IceTV enabled PVRs => Beyonwiz => Topic started by: raymondjpg on October 11, 2017, 08:16:44 PM

Title: IceTV - Notification of failed timer
Post by: raymondjpg on October 11, 2017, 08:16:44 PM
I have been getting some emailed IceTV - Notification of failed timers lately for a Beyonwiz DP-P2. I don't know how long I have subscribed to this error notification service but it seems to me that it was working fine for a while until I started to get these notifications recently.

They appear when a timer has already been set in the P2 but needs to be updated with a new start time from the IceTV server. Although I receive an IceTV - Notification of failed timer, and there is an error triangle next to the timer on the My Week web page, the new timer seems to have been set correctly in the P2.

Clearly something is not working as it should, and I would like to know if it is something that I need to address at my end, or if it is something that IceTV needs to address at theirs.
Title: Re: IceTV - Notification of failed timer
Post by: prl on October 13, 2017, 05:04:52 PM
That's a long-standing problem with IceTV on the DP series.
Title: Re: IceTV - Notification of failed timer
Post by: raymondjpg on October 13, 2017, 05:58:38 PM
That's a long-standing problem with IceTV on the DP series.


Though I have only noticed it recently. I have been advised by Colin O'Brien that "IceTV is working on our own work-around. Please bear with us as at least the show does record and only note the warning if it's a tuner collision or maybe a completely cancelled show.  I'd expect we will have a solution I've before November 1."
Title: Re: IceTV - Notification of failed timer
Post by: raymondjpg on November 12, 2017, 12:25:46 PM
I have been advised by Colin O'Brien that "IceTV is working on our own work-around. Please bear with us as at least the show does record and only note the warning if it's a tuner collision or maybe a completely cancelled show.  I'd expect we will have a solution I've before November 1."

Looks like it has been fixed.