dfox (11-03-18)
Here's a debug version of PowerTimer.py
PowerTimer.zip
This needs to go into /usr/lib/enigma2/python (take a copy of the PowerTimer.pyo which is already there, so you can put that back in place when you delete the PowerTimer.py after testing).
You also need to enable debug logs (if you don't have them on) and restart the GUI (to bring the new code into use). Then wait until you think the box should have shutdown and look at the debug log.
It should contain entries that say why it has backed-off the shutdown, like this:
Code:< 10628.704> [GML] ADS backoff - Clients streams active < 11386.693> [GML] ADS backoff - Recording < 12096.837> [GML] ADS backoff - Not in standby for auto
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
dfox (12-03-18)
Birdman I have sent you the debug logs.
thanks
I now know what the problem is (at least I think I do....).
It appears that if you change a repeating timer to an autorepeat one the repeating part is left in place (just confirmed that now). But part of the PowerTimer.py code assumed it would be 0 (my fault from a change some time ago).
I'll get that fixed (done, but need to test it)- and also:
- ensure that the back-off time for autorepeat timers is never set to more than the autorepeat (currently it can be, up to 30mins)
- look at why Deleteing a running timer just disables it - you have to Delete them twice
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
dfox (22-03-18)
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
dfox (22-03-18)
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
dfox (22-03-18)
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
Well, here's one. This fixes that actual problem reported by the OP.
More to follow. Some more tidying up ideas have appeared....Code:https://github.com/OpenViX/enigma2/pull/240
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
This one ensures that all auto* repeating timers start repeating from the time enigfma2 starts up (well, 30s later) rather than first wating for anything left over from the last enigma2 run.
This, and pull 242 mentioned above, should mean that auto[deep]standby timers will now be activated in at most the repeat time (after inactivity/standby setting as appropriate).Code:https://github.com/OpenViX/enigma2/pull/243
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD