19 replies to this topic

[40H3X]

Ik kijk net naar de EPG Import Log (show log) van EPGImport, omdat ik twijfel of deze op de gezette tijd is gelopen. Helaas, begrijp ik de "tijds" aanduidingen niet, kan iemand daar duidelijkheid in brengen.

[WanWizard]

Ik zie daar helemaal geen tijdsaanduiding?

[doglover]

Kijk gewoon naar het configuratie scherm, daat staat onderaan vermeld wanneer de laatste import gelopen heeft.

Zie de aangehechte screenshot.

 

In de log zelf staan geen tijden:

[EPGImport] ### thread is ready ### Events: 291431
[EPGImport] imported 291431 events
[EPGImport] Save last import date and count event
[EPGImport] Wait for parse autotimers 30 sec.
[EPGImport] Run start parse autotimers
[EPGImport] #### Finished ####
[EPGImport] Run check deep standby after import

Attached Files

•  1_0_1_2758_7FC_2_11A0000_0_0_0.jpg   167.94KB   1 downloads

[40H3X]

Ik zie daar helemaal geen tijdsaanduiding?

Dan hen ik de log text verkeerd geïnterpreteerd, "[EPGImport] autostart (0) occured at 15xxxxxxxx.82" zag ik als tijdsaanduiding

[WanWizard]

Probleem met die log is dat hij nooit compleet is. Waarom geen idee, maar lastig is het wel.

 

As dat een lang nummer is, dan is het waarschijnlijk unixtime. Dat kun je hier omzetten in iets leesbaars. 

[40H3X]

Dank, daar was ik al bang voor dat het de tijd +sinds 1-1-1970 ofzo is )...

Edited by 40H3X, 7 February 2018 - 12:02.

[40H3X]

 

Kijk gewoon naar het configuratie scherm, daat staat onderaan vermeld wanneer de laatste import gelopen heeft.

Zie de aangehechte screenshot.

 

In de log zelf staan geen tijden:

[EPGImport] ### thread is ready ### Events: 291431
[EPGImport] imported 291431 events
[EPGImport] Save last import date and count event
[EPGImport] Wait for parse autotimers 30 sec.
[EPGImport] Run start parse autotimers
[EPGImport] #### Finished ####
[EPGImport] Run check deep standby after import

 

Het plaatje is helder, maar die tijdsaanduiding mist hier op de Uno 4K SE, blijkbaar loopt de automatische instelling om de gezette tijd niet, trouwens ik heb onder de andere plugin (EMPGImport Filter v1.12) dit beeld

 

in de ui.py zie ik zo even niet iets vreemds....

skin = """<screen name="EPGSelectEPGSourcesScreen" position="fill" zPosition="2" flags="wfNoBorder" title="Select EPG sources" >
        <panel name="PigTemplate"/>
        <panel name="ButtonTemplate_RG"/>   
        <widget name="list" position="590,110" size="600,485" scrollbarMode="showOnDemand" />
    </screen>"""

Attached Files

•  Filter.jpg   81.48KB   1 downloads

Edited by 40H3X, 7 February 2018 - 12:08.

[doglover]

Die plugin is niet aangepast aan een fullHD skin.

 

Ik wel eens een aanpassing gepost voor deze plug-in om deze in fullHD te laten werken.  Maar weet niet meer waar.

Het eenvodudigste is even tijdelijk een 1280x720 skin gebruiken zoals OpenPLi HD (1/2)

 

Willy

[doglover]

Het plaatje is helder, maar die tijdsaanduiding mist hier op de Uno 4K SE, blijkbaar loopt de automatische instelling om de gezette tijd niet,

 

 

 

Mischien heb jij last van het fenomeen zoals in onze FAQ's beschreven is:

 

* No epg is imported after the box comes out of deepstandby.

 

When using deepstandby, and autotimer, there could be a problem with the automatic update.

This is because  when the box starts, the system time is not set properly until the box is tuned to a channel.  Now if you use autotimer, this tuning to a channel could take a minute longer as usual, because of autotimer.running.  Now the XMLTV importer sets a wrong update time, because the system time is still incorrect

The solution is to install the systemtime plugin and select upon startup to set system time by NTP server.

Lately this does not seem to work anymore.  Another workaround is:

 

Edit /var/bin/enigma2.sh and add before the line:

 

# hook to execute scripts always before enigma2 start

 

the next line:

ntpdate time.nist.gov > /tmp/ntdate.log

This also works if you prepare a /usr/bin/enigma2_pre_start.sh file and place the above command into that file.   The advantage is that this solution survives an image update. (if you use autobackup and add this file to the backup list)

You may have to install ntpdate.  This can be done in a telnet session:

opkg update
opkg install ntpdate

*

[WanWizard]

If would probably be better to adapt the plugin, so it can delay the start until it has a time that is not in 1970?

 

And if you want to use NTP, I suggest you install the systemtime plugin, instead of manually installing NTP.

[40H3X]

Thanks to both, I installed the system time plugin and added the line in /usr/bin/enigma2.sh , I will report back what happens as it is step to importEPG from deepstandby at 03:00

# hook to execute scripts always before enigma2 start
ntpdate time.nist.gov > /tmp/ntdate.log
# added line to get time

Edited by 40H3X, 7 February 2018 - 18:10.

[WanWizard]

If you have installed the systemtime plugin, there is no need to edit anything.

 

By editing a system file, you have now either blocked any future updates on that file (if opkg detects you have changed it, and will not update it), or your edit is going after the next update (if opkg doesn't). 

[40H3X]

Ah, I've removed the added line, TX.

 

Back to the problem, in plugin there is no timestamp, so it seems the EPG update did not occur at the set time (03:00). The Unix timestamp, as WanWizard pointed out, gives 1518072497.23 eg. Thu, 08 Feb 2018 06:48:17 GMT, but I still don't comprehend what it points to.

Attached Files

•  EPG.jpg   100.56KB   0 downloads
•  EPGlog.jpg   84.12KB   0 downloads

[40H3X]

Btw the systemtime plugin was installed the correct way...

root@vuuno4kse:~# opkg list-installed enigma2-plugin-systemplugins-sy*
enigma2-plugin-systemplugins-systemtime - y-git4666+30d853b-r0.0
root@vuuno4kse:~#

[WanWizard]

I was referring to your modification of "/usr/bin/enigma2.sh", which isn't needed if you have the systemtime plugin active (and configured for internet time instead of transponder time).

 

So it does wake up, it does set the next wakeup time, but it doesn't import?

 

What I also find weird, is the double and triple log entry?

[40H3X]

What I also find weird, is the double and triple log entry?

 

Yes, that's odd?

BTW do you have the EPG Import filter installed? Out of the blue, maybe this plugin is the cause that the EPG doesn't update?

 

 

I was referring to your modification of "/usr/bin/enigma2.sh", which isn't needed if you have the systemtime plugin active (and configured for internet time instead of transponder time).

 

Ah, I've removed the added line, TX.

 

 

Sorry, that I wasn't clear enough, the above meant that I removed the line Willy suggested from /usr/bin/enigma2.sh

 

And I did not modify the systemtime plugin to internet time instead of transponder time, maybe that is the culprit?

Edited by 40H3X, 8 February 2018 - 15:41.

[WanWizard]

BTW do you have the EPG Import filter installed? Out of the blue, maybe this plugin is the cause that the EPG doesn't update?

 

No, wouldn't know what to filter. So quite possible.

 

 

Ah, I've removed the added line, TX.

Sorry, that I wasn't clear enough, the above meant that I removed the line Willy suggested from /usr/bin/enigma2.sh

And I did not modify the systemtime plugin to internet time instead of transponder time, maybe that is the culprit?

 

Either use the systemtime plugin and have that keep the time in sync by settting it to internet time, or install ntpdate manually, and use the line Willy suggested. But not both.

 

The advantage of the systemtime plugin is that it goes into the backup, so it is preserved when you flash. Your manual change isn't.

[doglover]

I think some people need a lesson in reading:

 

I said before:

 

The solution is to install the systemtime plugin and select upon startup to set system time by NTP server.

Lately this does not seem to work anymore.  (I do not know why this is)

 

An suggested as alternative the ntpdate line;

 

This also works if you prepare a /usr/bin/enigma2_pre_start.sh file and place the above command into that file.   The advantage is that this solution survives an image update. (if you use autobackup and add this file to the backup list)

 

 

Willy

[WanWizard]

There is nothing wrong with the systemtime plugin, I use it on a daily basis.

 

The problem with it "no longer working" is caused by Oscam, someone thought it wise to put code in to block any change of the time. So if the time is wrong when Oscam starts, you can no longer change it, and that includes changes by the plugin.

 

I have committed a fix for this to 4-release and 6.1-release yesterday, so an Oscam version will be in the feeds after the next build.

 

And yes, enigma2_pre_start.sh is to be used for the alternative.

[40H3X]

De Plugin EPGImport Filter is exit en de systemtime plugin staat op internet time, we gaan het zien...