Fallback remote receiver - Bugs

[Snoete]

! Before you log an issue, have you updated to the most recent version?
Yes, Tested on the latest 7.6, and reported these Bugs in October 2024.

Describe the bug / Actual behaviour:

1. Default Fallback Timer
   In the Fallback Receiver Settings there is an option: "Select the timer from the fallback tuner by default".
   After activating the Fallback Receiver and restarting both receivers with this option ON the Fallback Timer is not selected by Default in the RecordTimer Settings screen.

2. Delete Fallback Timer
   It is not possible tot delete a Fallback Timer in the Record Timer Overview.
   See last screenshot.

Image/Box Model (please complete the following information):

• Version: 7.6
• BoxModel: VU+Duo 4K - VU+Duo 2 - ZGemma H.8.2H

[Snoete]

EDIT:
After selecting the Fallback Timer in the "Record Timer Settings" (see second screenshot) the Timer is created on the local receiver not on the Fallback Receiver. So sending a Timer (by default) to the Fallback Receiver doesn't work.

[MrServo]

Hi Snoete, we have changed details in OpenATV (new path specification in WebIF) and please test this version: /usr/lib/enigma2/python/Components/ImportChannels.py

ImportChannels.py

[Snoete]

Wil do that next weekend.

[Snoete]

First I Flashed to the latest OATV 7.6 than:

• Installed the new ImportChannels.py and restart,
• Checked if the new ImportChannels.pyc was created and threw away the .py file,
• Checked if the Fallback Receiver was active, and if the setting always send Timers to the Fallback Receiver was active.
• Made a new Timer in the Graphical EPG and had to activate Fallback Timer ON in the Timer Settings menu by Hand.
• The new Timer started to record on the local receiver not on the Fallback.

So in short, No Changes as far as I can See.
Can I check something here ?

[jbleyel]

Let me check this first.