startup to standby

[CRMS]

Post #6 iii) can get you to deep standby.

Yes, I have seen that. But my box is on a boat and switched off much/most of the time. When switched on for a future event, say in the middle of the night, I'd prefer it to start in DS and wait to record and then it goes back to DS afterwards.
Actually, I'd like to have 2 options when running the plug in:
Standby Enable/Disable and Deep Standby Enable/Disable.
I've managed to open the ipk and data.tar with Notepad++. But need to work out what line(s) to duplicate and amend. Plus the text for Deep Standby??

[ccs]

Yes, I have seen that. But my box is on a boat and switched off much/most of the time. When switched on for a future event, say in the middle of the night, I'd prefer it to start in DS and wait to record and then it goes back to DS afterwards.
Actually, I'd like to have 2 options when running the plug in:
Standby Enable/Disable and Deep Standby Enable/Disable.
I've managed to open the ipk and data.tar with Notepad++. But need to work out what line(s) to duplicate and amend. Plus the text for Deep Standby??

Timers can be configured to go to deep standby when finished. I use it all the time..

Have you got the source of the plugin? You can't edit the ipk with notepad++.

[CRMS]

Timers can be configured to go to deep standby when finished. I use it all the time..

Have you got the source of the plugin? You can't edit the ipk with notepad++.

Plugin at https://www.linuxsat-support.com/thr...by/#post619789

Edit with Notepad++ at https://www.linuxsat-support.com/thr...pk-windows-pc/

But I'll try the Power Timer as you describe.

[CRMS]

Power timer "autodeepstandby" works fine. Anyway to reduce minimum time of 10 mins to 5 or 2??

[ccs]

It looks like 10 is hardwired in as the minimum, I think a "manual" deep standby allows you less time before warning you that timers are due soon.

[Orlandox]

Hello,

enigma2-plugin-extensions-startuptostandby_experimental-git20120501-r0_all.ipk doesn't work anymore with OpenViX 6.1.003. Can someone fix it, please ?

enigma2-plugin-extensions-startuptostandby_experimental-git20120501-r0_all.ipk

[Huevos]

Where is the source repo for this plugin?

[Orlandox]

I got it from here : https://www.linuxsat-support.com/thr...ndby#post50970

Maybe it came from here : https://github.com/pli3/plugins-enig...artuptostandby

The best solution would be that this function is added to the system (system settings), so you can select if the box will start to standby or not. I think it is done to OpenPli.

[ccs]

.....you've not tried a power timer then?

w.jpg

[ccs]

Maybe I should have read post #1 from 14 months ago.

How often do you get power cuts?

[Orlandox]

Maybe I should have read post #1 from 14 months ago.

How often do you get power cuts?

Living in the country side where power is cut when ever wind is moving leaves on trees So very often. My other box ( UNO 4K SE) is also switching tv on through HDMI-CEC.

[birdman]

It's needs some minor changes for Python3.

In plugin.py:

• The two print statements need () around the strings they are printing.
• One import needs to be changed (a "." added to indicate a local import) on line 5
  

  from .StartupToStandbyConfiguration import StartupToStandbyConfiguration

Then it works.

[Orlandox]

It's needs some minor changes for Python3.

In plugin.py:

• The two print statements need () around the strings they are printing.
• One import needs to be changed (a "." added to indicate a local import) on line 5
  

  from .StartupToStandbyConfiguration import StartupToStandbyConfiguration

Then it works.

@birdman, thank you very much !!!

StartupToStandby.rar

[ccs]

Living in the country side where power is cut when ever wind is moving leaves on trees So very often. My other box ( UNO 4K SE) is also switching tv on through HDMI-CEC.

Cheers, I'd be tempted to keep my boxes in deep standby when not in use, power cuts could easily damage them.

[birdman]

It's needs some minor changes for Python3.
....
Then it works.

Although there's a bug in the packaging for the plugin too.
The Py3 compilation produces *.pyc files, not *.pyo ones, but the ipk file has *.pyo files in it.
So, if you remove the package (as I did after testing it) opkg just removes the files it installed (all it knows about). So the *.py and *.pyo files get removed, but the *.pyc files remain in place. And hence you still have the plugin installed, even after you removed it!

It needs a post-rm file to delete the installation directory (and shouldn't supply *.pyo/*.pyc files at all).