Sorry s3n0, I was busy yesterday and I can't respond. I read your response but I have not well understood, I'm not easy in English. So, I have to use a translator.
I found the problem this night. I wrote a script which awake the box. I shall explain it below.
For the CEC settings, they are activated. They ran well since a lot of years and it's convenient.
When I have timers which run in the night, they don't awake the box unless there is not "record" in a parameter but "zap".
For "Shutdown timer" parameters, there are all in red.
In fact, I use "init 4" and "init 3" in my script. As an application (which was installed a few days ago) changed my favorites an other parameters several times a day, and when the box restarts, it was boring. Then I found a script in the crontab which modified the favorites and I desactivated it. This was good for the several times a day.
But I didn't find when the box restart even if I searched in \etc\init.d the "bad" script. I shall try later.
So, when the box restarts, the "bad" script changes my favorites, erase the TNT frequencies... Another personal script copies the good parameters files in /etc/enigma2. And I have to "close" OpenPli, copy files and restarts OpenPli otherwise there are no changes on the screen.
I didn't know the OpenPli restart awakes the box .
For the script which is launched in the night, I also used "init 4" and "init 3. That's why the box awakes. I deleted the init commands and the box didn't awake this night .
And I found why the modification date of some files changed when the script was running. When OpenPli is closed, it saves some parameters as timers, settings...
Wouaw ! It takes me a long time to write this note !