Hello,
since ca. two weeks i have problems with broken records from Deepstandby.
example the problem:
-Timer added at 0.30-1.00Uhr with lead time from 2min
-from 22.00Uhr the Box is in Deepstandby
-Box boot at 0.28Uhr and go to Standby
-0.30Uhr record begin with furthermore Standby
-0.33Uhr box turn off in Deepstandby without shutdown
On the other Day i have 2 records with 2 minutes running time, instead of the planned 30min.
Since the Time as the problem comes i had installed the systemplugin "autoshutdown" from feed and update the Box per onlineupdate.
Before 3days i have deinstall "autoshotdown" to test without the plugin, but the problem remains.
It affects not all timerrecords, because sometimes they work. Usually the second record works, after the error from the first timer at the night.
On the HDD no crashlog. I have ativate the debuglog on an Error Event. Hope you can help.
View attachment Enigma2-17-01-2013_15-11-42.log
Gruss Lothar
since ca. two weeks i have problems with broken records from Deepstandby.
example the problem:
-Timer added at 0.30-1.00Uhr with lead time from 2min
-from 22.00Uhr the Box is in Deepstandby
-Box boot at 0.28Uhr and go to Standby
-0.30Uhr record begin with furthermore Standby
-0.33Uhr box turn off in Deepstandby without shutdown
On the other Day i have 2 records with 2 minutes running time, instead of the planned 30min.
Since the Time as the problem comes i had installed the systemplugin "autoshutdown" from feed and update the Box per onlineupdate.
Before 3days i have deinstall "autoshotdown" to test without the plugin, but the problem remains.
It affects not all timerrecords, because sometimes they work. Usually the second record works, after the error from the first timer at the night.
On the HDD no crashlog. I have ativate the debuglog on an Error Event. Hope you can help.
View attachment Enigma2-17-01-2013_15-11-42.log
Gruss Lothar
