19 replies to this topic

[Youpla]

I configured sleep timers so that my device goes to deep standby at night, and then wakeup on morning. I did this because the DUO² stays hot even in standby mode (and it consumes power for nothing).

 

But instead of waking up to standby mode, it goes straight to active mode.

Any way to configure this ?

[littlesat]

Why do you need the wake up in the first place?

However there is an option to startup the box in standby mode...
Maybe we should consider also to add this option in the sleep timer config. Now it is somewhere hidden in a menu

Edited by littlesat, 26 August 2018 - 12:13.

[Youpla]

I want to wake up because I don't want to wait for my device to boot when I need it. Ideally I would leave it in standby mode all the time, if it wasn't for the heat.

 

 

I already tried the option you are talking about (system -> setup ->  customize -> startup to standby), but this morning my device woke up in normal mode (although the option works when booting manually).

[Trial]

Hi,

I think the solution is more or less easy.  Create a zap timer with the OpenWebIF. There it is possible to set the after event state for zap timer directly. I do not know if it still works.

 

ciao

[Youpla]

Hi,

I think the solution is more or less easy.  Create a zap timer with the OpenWebIF. There it is possible to set the after event state for zap timer directly. I do not know if it still works.

 

ciao

 

It's more a workaround than a solution, but thanks anyway for the idea.

 

Did anybody manage to set a wake-up to deep standby timer ?

[littlesat]

Wake up before using it also uses energy... and the box will boot within a minute or so...

[Pr2]

Hi,

 

Youpla is correct this is clearly a bug, I have done many test and here is how it works today.

 

I defined a wake-up timer and put the Zgemma H7C into deep standby.

2 minutes before the scheduled wake up time the box start itself and is put into Standy (which is nice), the earlier startup is nice because it ensure that at the specified time the box is fully ready.

 

So the box is in standy (what is expected) but at the precise schedule time the box wakeup itself without taking care of the wake in standby parameter.

 

So this is clearly a bug because I second Youpla in its approach of using wakeup timer, I never use it because I also want that my box start immediately when I press the button.

If this option is fixed I will also consider to put my box into deep-standby.

 

Pr2

[Pr2]

Hi,

 

Ticket created:

 

https://devtools.ope....org/issues/361

 

Pr2

[Youpla]

It's definitely a bug. I tried the tip given in the screenshot below (which is supposed to fix my exact problem) and it doesn't work.

 

Edited by Youpla, 29 August 2018 - 12:44.

[littlesat]

Sorry I don't understand the issue....

[Pr2]

The issue is very simple:

 

There is an option that specify the OpenPLi state when it starts.

If enabled OpenPLi is supposed to stay in standby mode (for exemple after a power outage, a crash, an init 4/init 3,...)

 

When you use Deep-standby  you expect that this parameter is properly taken into account.

So when waking up from deep-standby with a timer (as foreseen by default) I expect my mox to stay in standby until I use the remote control to turn it on.

 

This is not the case!  The box start itself 2 minutes before the defined time to be fully ready at the specified time (this is really nice) and stay in standby (until there that's what we expect).  But some some reason at the precise wake-up time the box turn itself on.

This is not the expected behavior since we explicitly ask that it always start into standby.

 

We want that the box wake-up from the deep standby at the specified time, not at it start playing a service and turn on the TV (if HDMI-CEC is enabled).

 

Please check the ticket on devtools I have explained how to reproduce the bug.

 

Pr2

[littlesat]

Could also be bug depended... as for some boxes it cannot be predicted if it was a wakeup on timer -or- a manual wakeup....

[littlesat]

Sounds like someone need a huge amount of time to find the cullpit here....

But you say the box booted 2 min before and goes to standby and than wakes up again later... First we really need some log data...

[Pr2]

Hi have understood what the logic was when creating this wakeup screen:

The screen was designed for people that want to be awake by the TV!  It was not designed just to "wake up the stb" from the deep-standby.

 

So in fact, what is missing is an option to just wake up the box from deep-standby.

 

But yes I can confirm for sure that it 1st it goes into standby and then wake up so there are 2 timers involved, the 1st one is sent to the front-end (it seems to me that it is define 2 minutes before the real timer) and another one, I think within OpenPLi that this time turn on the the box. 

[littlesat]

It should be caused by the timer spaghetti code in RecordTimer.py... And because it is not easy to create log data after a reboot difficult to troubleshoot. It might even be triggered by one of the latest changes in the code here.

Edited by littlesat, 29 August 2018 - 14:41.

[Dimitrij]

When use wakeup timer --> "Yes, only from deep standby"/"yes" and not wakeup TV:

don't use option "Regard deep standby as standby" HDMI-CEC setup

or

option "Startup to Standby"  use "No, except Wakeup timer"

[littlesat]

Indeed except should keep it...

[Pr2]

When use wakeup timer --> "Yes, only from deep standby"/"yes" and not wakeup TV:
don't use option "Regard deep standby as standby" HDMI-CEC setup
or
option "Startup to Standby"  use "No, except Wakeup timer"

 
Sorry but I need to set: Regard deep standby as standby otherwise when I go in the menu and choose Deep standby my TV stay on which is not what I expect.

Yes the parameter you mention: option "Startup to Standby"  use "No, except Wakeup timer" should do its job but it doesn't seem to at least when I test it.

Anyway my choice is:  "Startup to Standby" : "Yes"

Since I often update my box remotely from telnet I don't want the box to be on after restart.

[littlesat]

Sounds like a new option needs to be added....

[littlesat]

This is the inital commit of this feature...

https://github.com/O...7872b6c6fe2d13a

Sounds like we need to add an option always... and when we check yes also include always.... or something like that...

Edited by littlesat, 29 August 2018 - 15:43.