In the past week or so, I have seem numerous failures when trying to schedule recordings on my Beyonwiz V2 device. I set these up using IceTV on the web or iPhone.
Normally, these only occur when there is a genuine conflict (3 shows, 2 tuners) but I am seeing others now.
This Friday for example, all 6 shows throughout the day have failed. One error message for "Planet America's Fireside Chat" at 8:00pm is:
"There was an error scheduling this show to device Beyonwiz V2.Timer conflict: 'Have You Been Paying Attention?', '8 Out Of 10 Cats Does Countdown'. This show is part of a series recording. "
"Have you Been Paying Attention" is not even being broadcast on the day.
Any suggestions please?
The process that checks for timer conflicts only cross-checks between the new timer that's to be added and timers that are in the Beyonwiz's timer list. While it's true that Have You Been Paying Attention? isn't scheduled to run on Fri 1 Nov, have you checked to see whether a timer for it has somehow got into your timer list?
If so, is it a misnamed timer for a show that you do want to record at that time, or is it a timer that's somehow been set for the wrong date?
We have seen this in the past when a tuner has 'disappeared' from the Beyonwiz while it is running. Are you using the USB tuner at all? Can you try rebooting the Beyonwiz and then rescheduling the failed timer. You can check how many tuners the Beyonwiz can currently see by going into the main menu then into "Information" and then "Devices".
If it fails again you will need to check the tuners within the Beyonwiz to ensure they are all working correctly.
To test whether tuners are actually running properly, it's a bit tedious. You need a time when no recordings are running or expected to start during the time it takes for the test. Then:
- Check the current tuner in use. OK from live TV, and if no recordings are running, a single tuner should be indicated as a green letter A-D just to the left of the infobar panel that shows signal strength/quality. The signal panel is at the far right-hand end end of the infobar and has two coloured bar indicators, each with a percentage on the right-hand end of the bar. The tuner here will usually be tuner A, but it won't necessarily be tuner A. If the infobar is removed too quickly, press OK again while the infobar is showing and show the detailed second infobar. This will lock the infobar display. Press OK a third time, or press EXIT to remove the second infobar display.
- If the tuner indicated in step 1 is working, note it as OK, otherwise as having a problem.
- In MENU>Setup>Tuners>Tuner allocation>Preferred tuner, use LEFT/RIGHT to change to a tuner that hasn't been checked so far, and then GREEN Save to set the preferred tuner. EXIT back to live TV.
- Change the channel to a channel from a different broadcaster from the one currently showing on live TV. This forces tuner allocation to happen and to select the new preferred tuner. The should infobar will now show the new tuner. Note whether it's working properly.
- If all tuners haven't been checked yet, go back to step 3. Otherwise, go back to step 3, but simply change the preferred tuner back to Tuner A, and then you're done.
Definitely worth checking the tuners, but it's still strange that the conflict error message included a timer that shouldn't be there.
Thanks for the replies Peter and Daniel. I'll try these steps when at home tonight.
Over the past week I have had recordings that were rescheduled due to conflicts - nothing new. I can't remember the details but it is possible that they were scheduled for the Friday in my example.
A reboot would certainly be a good start.
Yes, checking the tuners is a good start. In my experience the T2 is prone to loosing its USB tuner. The V2 and U4 only do this infrequently.
I often get timer conflict notifications from my T2s but the program records anyway.
Quote from: IanL-S on October 28, 2024, 11:24:19 AMIn my experience the T2 is prone to loosing its USB tuner.
The OP has a V2, but it's still worth them checking the tuners.
Quote from: prl on October 28, 2024, 10:09:14 AMDefinitely worth checking the tuners, but it's still strange that the conflict error message included a timer that shouldn't be there.
This is how it happens, and is the best indicator of a tuner 'disappearing' as the actual error is for timers earlier in the week that were ok in the past when they got set, but 'now' it's an error. When this happens every single new timer that gets set will just come up with an incorrect timer conflict error.
"Tuner gone missing" doesn't explain a conflict with a timer that's not expected to be there (Have you Been Paying Attention?).
Quote from: prl on October 28, 2024, 03:37:36 PM"Tuner gone missing" doesn't explain a conflict with a timer that's not expected to be there (Have you Been Paying Attention?).
My understanding is that whenever a timer is scheduled the conflict handler checks all timers within the system, and there is just a queue for errors, so if a timer wasn't a conflict in the past but now is because of a change in the tuner configuration the conflicting timer is still in the system as set but when it gets to checking the timer that is trying to be set there is already a 'conflict' listed in the system so it causes this new timer to be marked as a 'conflict incorrectly.
But again, none of that explains why there's a conflict with a timer that's not meant to be there at all!
I expect that when juergen looks at the timer list, there will be a conflicting timer for Have You Been Paying Attention, and then there is a question about how it got there when it's not supposed to be there.
Quote from: prl on October 28, 2024, 04:42:55 PMBut again, none of that explains why there's a conflict with a timer that's not meant to be there at all!
I expect that when juergen looks at the timer list, there will be a conflicting timer for Have You Been Paying Attention, and then there is a question about how it got there when it's not supposed to be there.
Because when that timer was originally set there was no conflict... but now there is, and it stuffs up all newly set timers.
I may have been a little extreme but took the following steps:
- Rebooted the PVR
- Deleted all timers
- Deactivated IceTV on the PVR
- Removed all timers for this week from the IceTV app
- Resynced IceTV (did this twice to remove all timers)
- Added some timers via the app and resynced
This appears to have worked. I did get a conflict but that was a genuine one so I resolved that as I normally would.
Although all appears to be working, here is some more info:
Regarding the tuners. I haven't been using a USB tuner for a while and the two inbuilt tuners have been tested and confirmed to be working.
There were some erors in the IceTV log like the following:
Can not update timer: 500 Server Error: Internal Server Error for url:
http://api.icetv.com.au/shows/timers/1730060354?email_address=w*****&token=22f****....&application_version=20211007
{"errors":[{error_code":11,"error_msg":"EIT ID cannot be changed for a timer"}]}
Also, the conflict email mentioned problems with the same show for three different days - example screenshot attached.screenshot.jpg
Quote from: Daniel Hall at IceTV on October 28, 2024, 08:27:36 PMBecause when that timer was originally set there was no conflict... but now there is, and it stuffs up all newly set timers.
My question about the Have You Been Paying Attention timer was more "Why is it there?" than "Why is there a conflict?" But juergen didn't mention anything about the HYBPA timer, nor whether all expected tuners are available on his V2 in his most recent post.
Quote from: prl on October 29, 2024, 10:01:17 AMMy question about the Have You Been Paying Attention timer was more "Why is it there?" than "Why is there a conflict?" But juergen didn't mention anything about the HYBPA timer, nor whether all expected tuners are available on his V2 in his most recent post.
I have two tuners on the V2 and after going through the steps given by Daniel, can confirm that they both work. An additional USB tuner is not plugged in so is not an issue.
I recorded HYBPA on the Monday and that may have been the victim of an earlier conflict. However, I can't see it being repeated any time until Sunday 3 Nov.
Have you checked the timer list on the V2 (TIMER on the remote) to see whether there is a timer (or more than one) set for Have You Been Paying Attention in the timer list, and what the start/end dates/times are for the timer, because HYBPA is involved in conflicts on 3 different days?
Quote from: prl on October 29, 2024, 11:11:15 AMHave you checked the timer list on the V2 (TIMER on the remote) to see whether there is a timer (or more than one) set for Have You Been Paying Attention in the timer list, and what the start/end dates/times are for the timer, because HYBPA is involved in conflicts on 3 different days?
Peter, I deleted all timers from the V2 and in the iOS app before adding any new ones so don't have access to that anymore.
All is working as expected at present.
My T2 sometimes has symptons similar to your V2. Timers that conflict with events that are nowhere near the target time. This generates a great many yellow triangles in My Week in IceTV.
My cause is generally when the T2 has crashed (usually due to full disk errors).
The only solution is what you have attempted. Disable IceTV, delete all timers manually, resend all timers from IceTV (My Recorders), Re-enable IceTV and refetch all timers. It's painful but it works.
I can't recall it ever happening to my V2 even when it has a hissy fit. Could be selective memory though!
I tend to assume my T2 does it because it runs FW 17.5 (for reasons!).