Jump to content


Photo

OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers


  • Please log in to reply
15 replies to this topic

#1 possibly2

  • Member
  • 9 posts

+1
Neutral

Posted 2 July 2019 - 14:51

Hi,

 

First, many thanks for this great image and congrats with the 7.1 release!

 

I have a few small VU single tuner no HDD boxes using a VU multi-tuner box as their main recording device. Using the Partnerbox extension for years had the 1st Partnerbox entry as their default recording device. After upgrading to 7.1 apparently this makes enigma2 go into some deadlock with no UI (still TV picture) when creating anew timer on the small VU boxes from EPG when having the remote Partnerbox as the default recording device. Need to kill the enigma2 process to make it restart to gain back control.

 

Changing the config to have the local device as default recording device in Partnerbox and then manually changing each timer when creating it to the Partnerbox entry works so the issue is apparently only related to having a Partnerbox entry as the default one.

 

Tried to restart enigma2 in troubleshooting mode but I'm not sure if this produced any helpful debug?

 

[eDVBSatelliteEquipmentControl] sat 3592 found
[eDVBSatelliteEquipmentControl] ret1 10000
[eDVBSatelliteEquipmentControl] ret5 10000
[eDVBSatelliteEquipmentControl] ret 10000, score old 0
[eDVBSatelliteEquipmentControl] score new 10000
[eDVBSatelliteEquipmentControl] final score 10005
[RemoteChannelStreamConverter] fallback to default translation for Remote channel stream converter
[Skin] Processing screen: EPGSelection
[Skin] Processing screen: SimpleSummary
[eHdmiCEC] received message
[ActionMap] Keymap 'EPGSelectActions' -> Action = 'yellow'
[ActionMap] Keymap 'EPGSelectActions' -> Action = 'timerAdd'
[TIMER] record time changed, start prepare is now: Sat Jul  6 10:57:40 2019
[eHdmiCEC] received message
[eHdmiCEC] received message
[eHdmiCEC] received message 8F
[eHdmiCEC] send message 90 00
[eHdmiCEC] received message
[eHdmiCEC] send message 90 00
connectionLost? [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion: Connection lost.
]
[eDVBCAService] free slot 0 demux 0 for service 1:0:19:1BEC:44:46:E080000:0:0:0:
[eDVBCAService] free service 1:0:19:1BEC:44:46:E080000:0:0:0:
[eDVBServicePlay] timeshift
[eTSMPEGDecoder] decoder state: play, vpid=ffffffff, apid=ffffffff
[eDVBPCR0] DEMUX_STOP ok
[eDVBPCR0] destroy
[eDVBVideo0] DEMUX_STOP  ok
[eDVBVideo0] VIDEO_STOP ok
[eDVBVideo0] destroy
[eDVBAudio0] AUDIO_STOP ok
[eDVBAudio0] DEMUX_STOP ok
 
Please let me know if there is anything else I can do to troubleshoot further to locate the issue.
 
 
P.
 


Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #2 WanWizard

  • Forum Moderator
    PLi® Core member
  • 48,380 posts

+821
Excellent

Posted 2 July 2019 - 15:12

What is the output of "dmesg" when this happens?

 

BTW, you no longer need Partnerbox for this, this functionality is built into Enigma these days (menu, setup, service and searching, fallback tuner).


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #3 littlesat

  • PLi® Core member
  • 49,168 posts

+527
Excellent

Posted 2 July 2019 - 15:27


connectionLost? [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion: Connection lost
]

Edited by littlesat, 2 July 2019 - 15:30.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #4 littlesat

  • PLi® Core member
  • 49,168 posts

+527
Excellent

Posted 2 July 2019 - 15:29

Could be the repeated timer bool/interger bug we solved recently, where parnerbox does not give us the complete debug.

Finding the repeated timer that causes it could be a solution.

In addition when the client box is a pure client box without tuners you can also consider to swap to fallbacktuner... with settings/epg + timer support.


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #5 Dimitrij

  • PLi® Core member
  • 6,551 posts

+210
Excellent

Posted 2 July 2019 - 17:09

littlesat

"Enable Partnerbox-Function in TimerEvent" --> Yes

"Enable first Partnerbox-entry in Timeredit as default" -->Yes

Menu--> Timer --> Add(green button):

 File "/usr/lib/enigma2/python/Plugins/Extensions/Partnerbox/RemoteTimerEntry.py", line 315, in RemoteTimer__init__
    RemoteTimernewConfig(self)
  File "/usr/lib/enigma2/python/Plugins/Extensions/Partnerbox/RemoteTimerEntry.py", line 402, in RemoteTimernewConfig
    if self["config"].getCurrent() == self.timerRemoteEntry:
AttributeError: 'TimerEntry' object has no attribute 'timerRemoteEntry'

or

Single EPG --> Add timer

 

Need to kill the enigma2 process to make it restart to gain back control.

 

 

I think the problem is here Partnerbox - fixed compatibility with FallbackTimer - thx littlesat

I do not know the solutions.


Lunix3-4K/VU+solo4k(thanks guys to gisclub.tv)


Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #6 Dimitrij

  • PLi® Core member
  • 6,551 posts

+210
Excellent

Posted 2 July 2019 - 18:38

https://github.com/O...221109b021eL346

this line need add now

	self.timerentry_remote = ConfigSelection(default = default, choices = self.entryguilist)
+       baseTimercreateConfig(self)

Lunix3-4K/VU+solo4k(thanks guys to gisclub.tv)


Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #7 littlesat

  • PLi® Core member
  • 49,168 posts

+527
Excellent

Posted 2 July 2019 - 20:45

So need the partnetbox plugin some adaptions?

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #8 Dimitrij

  • PLi® Core member
  • 6,551 posts

+210
Excellent

Posted 3 July 2019 - 05:01

So need the partnetbox plugin some adaptions?

yes

	self.timerentry_remote = ConfigSelection(default = default, choices = self.entryguilist)
+       baseTimercreateConfig(self)

But I do not know how it will affect the FallbackTimer.


Edited by Dimitrij, 3 July 2019 - 05:05.

Lunix3-4K/VU+solo4k(thanks guys to gisclub.tv)


Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #9 littlesat

  • PLi® Core member
  • 49,168 posts

+527
Excellent

Posted 3 July 2019 - 06:49

Just try it please (as far I can see by looking just to the code it should not interfere) + when you use partnerbox you do not want fallback tuner???
However this proves (again) that function stealing plugins are not done!...
I would say please offer a merge request

Edited by littlesat, 3 July 2019 - 06:51.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #10 jeanclaude

  • Senior Member
  • 767 posts

+27
Good

Posted 3 July 2019 - 11:56

 

BTW, you no longer need Partnerbox for this, this functionality is built into Enigma these days (menu, setup, service and searching, fallback tuner).

I have 3 local boxes, and I use partnerbox to set timers on the 2 other boxes. Can fallback tuner do the same (without changing the fallback tuner IP address in the setup menu every time I want to switch from remote box 1 to remote box 2) ? I didn't think so .......


Edited by jeanclaude, 3 July 2019 - 11:58.

DreamBox 7000S+8000HD (eindelijk), openPLi, CCcam, 85 cm schotel, draaibare opstelling en VEEL te weinig slaap.

Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #11 littlesat

  • PLi® Core member
  • 49,168 posts

+527
Excellent

Posted 3 July 2019 - 12:05

Nope... but still on the timerlist even in partnerbox you can only see one 'server' box added to the timerlist. As far I know you also cannot program repeated timers. Only on timer edit you can select an IP from one of the partnerboxes. 

But fallbacktuner is not intended to do such complicated configurations. It was intended for one master box (with eg FBC tuners and the harddisk) and (pure) client boxes in the rest of the house. Actually I think you should not care and think on which box you program the timer.

Of course alternativaly at least in the timerlist we can consider to add a quicklink or so to the fallbacktuner configuration. Then you are able to instantly change the partner box from the timerlist (not from the edittimer screen) to be able to add the timers from a different box. You do not have the target box in timerEdit, however it also alows to quickly see the timers of a different box in the list + it is a relativaly easy change. (results in we can also do it with fallbacktimer, but slightly different). When this is added than partnerbox becomes fully out of scope.

 

In addition it was considered to add a config for fallbacktuner where you can set different urls based on type (with type here I mean DVB-S/T/C/ATSC). when this is added you also solve the issue with one box having e.g. DVB-T and another having DVB-S... you can fallback to the tuner that has the type. But still centralize the settngs for example on a central server box.

 

Plus I'm considering to add a switch to the fallback tuner config that automatically mounted the harddrive of the serverbox as harddisk (when the serverbox has a hdd). When it is password protected it takes the password from the OWIF.

 

I hope you understand what I meant

 

At least some thinks we consider to add in OpenPLi 8.0 (or 7.2)


Edited by littlesat, 3 July 2019 - 12:10.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #12 jeanclaude

  • Senior Member
  • 767 posts

+27
Good

Posted 3 July 2019 - 14:46

But fallbacktuner is not intended to do such complicated configurations. It was intended for one master box (with eg FBC tuners and the harddisk) and (pure) client boxes in the rest of the house. Actually I think you should not care and think on which box you program the timer.

this would indeed be ideal, you just indicate that you want to make a recording and let enigma decide on which box the recording will be executed - all timers and all tuners would then have to go into one big single resource pool with all the locally available receivers in it - but that's not how it works yet !

indeed, in the EPG list you will only see the timer indicators of the local receiver plus one partnerbox entry - but this can be quickly changed by using the "red" button on the EPG list. But this is (for me) less important as I know more or less what timers I've set.

it's the timer edit screen which is the most important. If I set a timer and I get a timer conflict, I can quickly assign the timer to one of the other boxes defined with partnerbox. As long as this easy of setting timers to any of the locally defined boxes is not possible with fallbacktuner, I will continue to use partnerbox, and many others with me.


DreamBox 7000S+8000HD (eindelijk), openPLi, CCcam, 85 cm schotel, draaibare opstelling en VEEL te weinig slaap.

Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #13 littlesat

  • PLi® Core member
  • 49,168 posts

+527
Excellent

Posted 3 July 2019 - 17:02

The quick change via eg red button is something we also can do... what we cannot do is put a list on the timeredit screen... that will be local or the remote you selected.
As also the retrieve settings and epg depends on it maybe we need to add a temporary ‘config’ when we make this

Edited by littlesat, 3 July 2019 - 17:04.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #14 Dimitrij

  • PLi® Core member
  • 6,551 posts

+210
Excellent

Posted 3 July 2019 - 17:08

[partnerbox] fix init first remote config


Lunix3-4K/VU+solo4k(thanks guys to gisclub.tv)


Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #15 littlesat

  • PLi® Core member
  • 49,168 posts

+527
Excellent

Posted 3 July 2019 - 17:15

Merged

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: OpenPLi 7.1 - issue with Partnerbox entries as default device when creating timers #16 possibly2

  • Member
  • 9 posts

+1
Neutral

Posted 7 July 2019 - 14:18

Thanks guys!

 

Added the baseTimercreateConfig(self) line to the code on the boxes that create remote timers and it works just fine now.

 

Problem solved!  :thumbs-up:






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users