Neu: Duo2 beständig im Deepstandby trotz Elektro Plugin wegen neuem Image?

    Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

    • Neu: Duo2 beständig im Deepstandby trotz Elektro Plugin wegen neuem Image?

      Guten Abend zusammen,

      seit ein paar Wochen habe ich ein Problem, das unsere Familie nicht mag. Durch die Osterferien Kamm ich erst jetzt zum Testen und überlege.
      „Plötzlich“ geht unsere Duo2 beim Ausschalten immer direkt in den Deepstandby und ist zu Zeiten im Deepstandby, in denen die Box im Standby sein sollte.
      Standby- und Deepstandby-Zeiten hatte ich vor Jahren mit dem Elektro-Plugin definiert. Nun geprüft: Dieses ist noch immer so definiert und das Plugin steht auf „aktiviert“.

      Etwa zu der Zeit, als die Box immer nach dem Ausschalten in den Deepstandby ging und zu definierten Zeiten nicht mehr inden Standby wechselte, hatte ich den Fernseher (neuer B&O) gewechselt und damit auch den sogenannten PUC, der es erlaubt die Duo2 mit der Fernbedienung des Fernsehers zu steuern. Darum hatte ich zuerst den Fehler dort gesucht.

      Nun habe ich aber die Box mit der Original-VU+Fernbedienung und mit e2RemotePro aus und eingeschaltet und das Problem ist auch damit aufgetreten.

      Dann erinnerte ich mich, dass ich damals auch das Image upgedated hatte. Das hatte ich länger nicht gemacht.
      Was für mich damals neu war, war der Menüpunkt „Aufgaben“. Seit wann gibt es den?

      Nun habe ich mir das mal angeschaut und ich sehe darin Aufgaben, wie Einschalten und Standby.
      Ist das nun eine neue Möglichkeit Zeiten des Standy und Deepstandby zu definieren?

      Und wird deshalb das Elektro-Plugin nun nicht mehr unterstützt. Oder ist das nun blöde Spekulationen meinerseits.

      Vielen Dank für Eure Hilfe und Euer mitdenken.

      Solomon
    • Ist nun gelöst.

      Vermutlich dadurch, dass ich im Elektro-Plugin etwas umgestellt und dann erneut gespeichert hatte.
      Schon irgendwie dubios.

      Würde „Aufgaben“ das gleiche übernehmen können?
    • Hallo Experten,

      ich habe ein ähnliches Problem. Installiert ist bei mir Image VTi 13.0.9 2018-04-10-vti-master. Ich verwende seit Jahren Elektro-Plugin. Das hat immer gut geklappt. Seit einigen Monaten, fährt aber meine Box so nach Lust und Laune in Deepstandby. Ich habe schon den Eletro-Plugin deinstalliert, was aber leider nicht geholfen hat.
      Hat jemand eine Idee was das sein konnte?

      misiek77
    • fährt aber meine Box so nach Lust und Laune in Deepstandby
      DAS glaube ich dir nicht, die Box hat einen Anlass dafür
      Hat jemand eine Idee was das sein konnte?
      ja
      eine Einstellung, welche du nicht oder falsch gesetzt hast
      entweder du gehst mögliche Einstellungen durch (autom. Ausschalten,Aufnahmen, VTi-Aufgaben und alle Plugins, welche autom. Aufgaben erledigen), oder du erstellst debug und schaust dort nach (Menü -> VTi -> Einstellungen system -> Seite 5/5)
      ============================================================================================
    • Edit by hgdo: unnötiges Komplettzitat bei Direktantwort entfernt

      Danke. Debug habe ich schon eingeschaltet, jetzt nur noch auf das Ergebnis warten. Aut. Ausschalten ist alles deaktiviert. Bei den Aufnahmen habe ich nichts gefunden wo ich Deepstandby einstellen konnte. Sonst habe ich noch EPG Import was ich noch kontrollieren muss.
      Ich melde mich wieder später hier.

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von hgdo ()

    • Neu: Duo2 beständig im Deepstandby trotz Elektro Plugin wegen neuem Image?

      So, Debug.log ist da. Ich werde aber nicht schlau daraus. Die Box geht in Deepstandby nachdem die Timer-Aufnahme beendet wurde. Dann wird noch 'wakeup time' eingestellt auf 13:55 (Zeile 171). So war das damals auch in Elektro-Plugin eingestellt, aufwachen um 13:55 Uhr, aber den habe ich deinstalliert. Ich sehe es nur, dass auf der Box immer noch irgendein Script läuft. Eine Leiche von Elektro-Plugin? Vielleicht findet hier jemand was, was ich nicht sehen kann:

      Spoiler anzeigen
      01:00:00.117 [e2-python] [TIMER] record event 5
      01:00:00.121 [e2-python] [TIMER] record event 1
      01:00:00.141 [e2-core] loading streaminfo for /media/hdd/movie/20180703 2329 - Film.ts
      01:00:00.249 [e2-python] [remove callback]
      01:00:00.253 [e2-core] [eDVBCAService] free slot 0 demux 1 for service 1:0:19:3779:44C:13E:820000:0:0:0:
      01:00:00.253 [e2-core] demux 1 mask 02 prevhash 03e9021e
      01:00:00.253 [e2-core] [eDVBCAService] don't build/send the same CA PMT twice
      01:00:00.256 [e2-python] [SILENT_REC] we are in auto mode
      01:00:00.257 [e2-python] [TIMER] activating state 2
      01:00:00.257 [e2-python] [TIMER] go to deep standby
      01:00:00.261 [e2-python] [SILENT_REC] we are already in standby
      01:00:00.266 [e2-python] Looking for embedded skin
      01:00:01.001 [e2-python] [TIMER] activating state 3
      01:00:01.002 [e2-python] [TIMER] stop recording
      01:00:01.002 [e2-python] ProcessRepeated
      01:00:01.003 [e2-python] localrepeatedbegindate: Tue Jul 3 01:00:00 2018
      01:00:01.004 [e2-python] localbegin: Wed Jul 4 01:00:00 2018
      01:00:01.004 [e2-python] localend: Wed Jul 4 01:00:01 2018
      01:00:01.005 [e2-python] localnow: Wed Jul 4 01:00:02 2018
      01:00:01.005 [e2-python] Day: 0
      01:00:01.006 [e2-python] Day: 1
      01:00:01.006 [e2-python] Day: 2
      01:00:01.007 [e2-python] Day: 3
      01:00:01.007 [e2-python] Day: 4
      01:00:01.008 [e2-python] localbegin after addOneDay: Thu Jul 5 01:00:00 2018
      01:00:01.009 [e2-python] localend after addOneDay: Thu Jul 5 01:00:01 2018
      01:00:01.009 [e2-python] ProcessRepeated result
      01:00:01.010 [e2-python] Thu Jul 5 01:00:00 2018
      01:00:01.011 [e2-python] Thu Jul 5 01:00:01 2018
      01:00:01.011 [e2-python] [TIMER] record time changed, start prepare is now: Thu Jul 5 00:59:40 2018
      01:00:01.012 [e2-python] ProcessRepeated
      01:00:01.012 [e2-python] localrepeatedbegindate: Tue Jul 3 01:00:00 2018
      01:00:01.013 [e2-python] localbegin: Thu Jul 5 01:00:00 2018
      01:00:01.014 [e2-python] localend: Thu Jul 5 01:00:01 2018
      01:00:01.014 [e2-python] localnow: Wed Jul 4 01:00:02 2018
      01:00:01.015 [e2-python] Day: 0
      01:00:01.015 [e2-python] Day: 1
      01:00:01.016 [e2-python] Day: 2
      01:00:01.016 [e2-python] Day: 3
      01:00:01.017 [e2-python] Day: 4
      01:00:01.017 [e2-python] ProcessRepeated result
      01:00:01.018 [e2-python] Thu Jul 5 01:00:00 2018
      01:00:01.018 [e2-python] Thu Jul 5 01:00:01 2018
      01:00:01.021 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:00:01.022 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:01:41.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:03:21.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:05:01.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:06:41.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:08:21.002 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:10:01.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:11:41.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:13:21.002 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:15:01.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:16:41.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:18:21.002 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:20:01.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:21:41.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:23:21.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:25:01.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:26:41.002 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:28:21.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:28:45.183 [e2-core] no version filtering
      01:28:45.183 [e2-core] 0014: 70 00 00 00 00 00
      01:28:45.183 [e2-core] mask: fc 00 00 00 00 00
      01:28:45.183 [e2-core] mode: 00 00 00 00 00 00
      01:28:46.184 [e2-core] [eDVBLocalTimerHandler] diff is 0
      01:28:46.184 [e2-core] [eDVBLocalTimerHandler] diff < 120 .. use Transponder Time
      01:28:46.185 [e2-core] [eDVBLocalTimerHandler] not changed
      01:30:01.002 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:30:03.267 [e2-core] child has terminated
      01:30:03.267 [e2-core] pipes closed
      01:30:03.278 [e2-core] child has terminated
      01:30:03.279 [e2-core] pipes closed
      01:30:13.258 [e2-core] child has terminated
      01:30:13.258 [e2-core] pipes closed
      01:31:41.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:31:57.920 [e2-core] [eEPGCache] start caching events(1530660717)
      01:32:04.925 [e2-core] [eEPGCache] abort non avail viasat reading
      01:32:04.926 [e2-core] [eEPGCache] abort non avail mhw reading
      01:32:12.963 [e2-core] [eEPGCache] nownext finished(1530660732)
      01:33:21.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:33:35.045 [e2-core] [eEPGCache] schedule other finished(1530660815)
      01:33:35.112 [e2-core] [eEPGCache] schedule finished(1530660815)
      01:33:35.113 [e2-core] [eEPGCache] stop caching events(1530660815)
      01:33:35.113 [e2-core] [eEPGCache] next update in 60 min
      01:35:01.002 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:36:41.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:38:21.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:40:01.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:41:41.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:43:21.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:45:01.002 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:46:41.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:48:21.002 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:50:01.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:51:41.002 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:53:21.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:55:01.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:56:41.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:58:21.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      01:58:46.185 [e2-core] no version filtering
      01:58:46.185 [e2-core] 0014: 70 00 00 00 00 00
      01:58:46.186 [e2-core] mask: fc 00 00 00 00 00
      01:58:46.186 [e2-core] mode: 00 00 00 00 00 00
      01:58:46.191 [e2-core] [eDVBLocalTimerHandler] diff is 0
      01:58:46.192 [e2-core] [eDVBLocalTimerHandler] diff < 120 .. use Transponder Time
      01:58:46.192 [e2-core] [eDVBLocalTimerHandler] not changed
      02:00:01.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:01:41.002 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:03:21.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:05:01.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:06:41.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:08:21.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:10:01.002 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:11:41.002 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:13:21.002 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:15:01.002 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:16:41.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:18:21.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:20:01.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:21:41.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:23:21.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:25:01.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:25:01.111 [e2-core] +- 1/2 TID 4e
      02:25:02.207 [e2-core] ++ 2/2 TID 4e
      02:25:02.208 [e2-core] done!
      02:25:02.209 [e2-core] pcr of eit change: 13b89a03f
      02:25:02.209 [e2-core] [eDVBServiceRecord] now running: WM2018 (6900 seconds)
      02:25:02.210 [e2-python] [TIMER] record event 9
      02:25:02.210 [e2-core] doing version filtering
      02:25:02.211 [e2-core] 0012: 4e 37 79 19 00 00
      02:25:02.211 [e2-core] mask: ff ff ff 3f 00 00
      02:25:02.211 [e2-core] mode: 00 00 00 3e 00 00
      02:26:41.001 [e2-python] next real activation is Wed Jul 4 02:30:00 2018
      02:28:46.190 [e2-core] no version filtering
      02:28:46.190 [e2-core] 0014: 70 00 00 00 00 00
      02:28:46.190 [e2-core] mask: fc 00 00 00 00 00
      02:28:46.190 [e2-core] mode: 00 00 00 00 00 00
      02:28:46.206 [e2-core] [eDVBLocalTimerHandler] diff is -1
      02:28:46.207 [e2-core] [eDVBLocalTimerHandler] diff < 120 .. use Transponder Time
      02:28:46.327 [e2-core] [eDVBLocalTimerHandler] difference between linux time and RTC time is < 60 sec... so the transponder time looks ok
      02:28:46.327 [e2-core] [eDVBLocalTimerHandler] time update to 02:28:45
      02:28:46.328 [e2-core] [eDVBLocalTimerHandler] m_time_difference is -1
      02:28:46.328 [e2-core] [eDVBLocalTimerHandler] set Linux Time
      02:30:00.002 [e2-python] [TIMER] activating state 3
      02:30:00.002 [e2-python] [TIMER] stop recording
      02:30:00.003 [e2-core] stop recording!
      02:30:00.004 [e2-core] stopping thread.
      02:30:00.038 [e2-core] FILEPUSH THREAD STOP
      02:30:00.039 [e2-core] thread joined 0
      02:30:00.042 [e2-core] loading streaminfo for /media/hdd/movie/20180704 0054 - Film.ts
      02:30:00.100 [e2-core] fixed up 11e91dabf to 54b4cb (offset 0)
      02:30:00.101 [e2-core] fixed up 13b89a03f to 1d4c7a4b (offset 0)
      02:30:00.107 [e2-python] [TIMER] record event 5
      02:30:00.111 [e2-python] [TIMER] record event 1
      02:30:00.131 [e2-core] loading streaminfo for /media/hdd/movie/20180704 0054 - Film.ts
      02:30:00.237 [e2-python] [remove callback]
      02:30:00.240 [e2-core] [eDVBCAService] free slot 1 demux 1 for service 1:0:19:3779:44C:13E:820000:0:0:0:
      02:30:00.240 [e2-core] [eDVBCAService] free service 1:0:19:3779:44C:13E:820000:0:0:0:
      02:30:00.243 [e2-core] start release channel timer
      02:30:00.244 [e2-python] [SILENT_REC] we are in auto mode
      02:30:00.245 [e2-python] RecordTimer.TryQuitMainloop
      02:30:00.247 [e2-python] RecordTimer.staticGotRecordEvent(iRecordableService.evEnd)
      02:30:00.249 [e2-python] no starting records in the next 360 seconds... immediate shutdown
      02:30:00.251 [e2-python] [WOLSetup] Deep Standby with WOL.
      02:30:00.252 [e2-python] [WOLSetup] Support : True Enable : True WriteDevice : True
      02:30:00.292 [e2-python] next real activation is Wed Jul 4 13:59:40 2018
      02:30:00.800 [e2-python] 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.
      ]02:30:00.800 [e2-python]
      02:30:00.813 [e2-python] set wakeup time to 2018/07/04 13:55
      02:30:00.923 [e2-python] stopService
      02:30:00.978 [e2-python] [EPGImport] autostart (1) occured at 1530664200.98
      02:30:00.978 [e2-python] [EPGImport] Stop
      02:30:00.996 [e2-core] resolve: resolve ${sysconfdir}/enigma2/lamedb
      02:30:00.997 [e2-core] resolve: -> /etc/enigma2/lamedb
      02:30:00.997 [e2-core] ---- saving lame channel db
      02:30:01.090 [e2-core] saved 97 channels and 2649 services!
      02:30:01.092 [e2-core] release cached channel (timer timeout)
      02:30:01.092 [e2-core] [eDVBCAService] remove channel 0x27f3af0
      02:30:01.093 [e2-core] [eDVBLocalTimerHandler] remove channel 0x27f3af0
      02:30:01.093 [e2-core] [eEPGCache] remove channel 0x27f3af0
      02:30:01.094 [e2-core] stop release channel timer
      02:30:01.097 [e2-core] [eEPGCache] store epg to realpath '/media/hdd/epg.dat'
      02:30:01.169 [e2-core] [eEPGCache] 40316 events written to /hdd/epg.dat
      02:30:01.230 [e2-core] [EPGCache] finalize epg.dat file
      02:30:01.542 [e2-core] thread joined 0
      02:30:03.015 [e2-core] set RTC to previous valid time
      02:30:03.126 [e2-core] - (42) eServiceRecordDB
      02:30:03.126 [e2-core] - (42) eVTiApp
      02:30:03.127 [e2-core] [eVTiApp] ...shutdown
      02:30:03.127 [e2-core] - (41) eServiceFactoryM2TS
      02:30:03.127 [e2-core] - (41) eServiceFactoryMP3
      02:30:03.127 [e2-core] - (41) eServiceFactoryHDMI
      02:30:03.128 [e2-core] - (41) eServiceFactoryFS
      02:30:03.128 [e2-core] - (41) eServiceFactoryDVB
      02:30:03.128 [e2-core] - (41) eServiceFactoryDVD
      02:30:03.129 [e2-core] - (40) eServiceCenter
      02:30:03.130 [e2-core] - (35) CI Slots
      02:30:03.132 [e2-core] - (30) eActionMap
      02:30:03.133 [e2-core] - (21) input device driver
      02:30:03.138 [e2-core] - (21) Console RC Driver
      02:30:03.138 [e2-core] - (20) DVB-CI UI
      02:30:03.138 [e2-core] - (20) Hdmi CEC driver
      02:30:03.139 [e2-core] - (20) UHF Modulator
      02:30:03.139 [e2-core] - (20) RC Input layer
      02:30:03.139 [e2-core] - (20) misc options
      02:30:03.140 [e2-core] - (20) AVSwitch Driver
      02:30:03.140 [e2-core] - (15) eWindowStyleManager
      02:30:03.142 [e2-core] - (10) gRC
      02:30:03.142 [e2-core] waiting for gRC thread shutdown
      02:30:03.260 [e2-core] gRC thread has finished
      02:30:03.260 [e2-core] - (9) GFBDC
      02:30:03.461 [e2-core] - (9) gLCDDC
      02:30:03.461 [e2-core] - (9) Font Render Class
      02:30:03.461 [e2-core] - ( graphics acceleration manager
      02:30:03.462 [e2-core] - (5) Tuxtxt
      02:30:03.462 [e2-core] - (1) Background File Eraser
      02:30:03.463 [e2-core] reached rl -1

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von hgdo ()