N5200pro: Power Mgmt not working?

[Grumpftl]

Hello to everybody,
I'm using the 5200pro with 2.00.04.
I'd like to use the power management to switch the box off at 01:00 am. I'll wake it up via WOL if I need something stored on the box.
So I programmed the "Schedule Power On/Off" times. Ive tried the following:
1.) I set the first coloumn to "switch off" and the time to "01:00", the second column was left blank
2.) I left the first coloumn blank and added the "switch off" and "01:00" to the second coloumn.

The box switches off at 01:00 BUT: It switches itself ON AGAIN every day at 6:30 pm !!
I do not now why, nobody was at home, nobody used the LAN. And the same occures every day!
Anybody with the same experience? Where comes the "on"-Event from?

Thank you,
Grumpftl

[Lindsay]

We too have found that power management performs strangely if both the on and off times are not set.

See our post at:

h**p://forums.hexus.net/thecus-care-hexus/119708-5200-pro-powers-up-06-00-its-own.html

which has not been resolved in 2.00.04

It's not a major problem by any means but one of those "loose ends" that should be sorted out.

We are based in GMT timezone. Our mystery power on occurred at approx 06.01 GMT every day.

(Sorry had to use the ** as we have not made 5 posts here yet!)

[Grumpftl]

Ok, so it's not me getting something wrong, but the box itself :-)

Well, I would'nt call it "not a major problem" if a devices switches itself on without any cause. Imagine your coffee-machine behaves like this ...

But ok, I think the whole thing is like a building site :-\

[Lindsay]

As a matter of passing interest - what timezone are you in?

[Grumpftl]

It's GMT+1 - located in Germany, Timezone "Berlin Amsterdam ... etc."

[QF006]

You are not alone, mine also switches on itself if only switch-off times are programmed. Mine switches on at 0:00 (AEST). I think the problem is that the timer chip itself doesn't have a calendar and so it generates an interrupt which powers on the unit. The unit then does not check why it was powered on. It could power off itself if it found out that this was a power-off entry.

Does anyone know what timer chip they use in the N5200 Pro ?

Cheers
Siggy

[Thecus - Yvon]

Dear Sir,

Would you please provide us more detail information for us analysis for you? as like what firmware version and what kind of behavior on your NAS.

[Blub]

Hi,

my Thecus shows the same behavior as described above. I can add some additional information:

With my N5200 Pro RouStor and FW 2.00.08 the Thecus started each night at 00:01:19 a.m. !

Now, with FW 2.00.14 it already starts at 8:10:57 p.m.

Cheers
Blub

[Grumpftl]

Dear Sir,

Would you please provide us more detail information for us analysis for you? as like what firmware version and what kind of behavior on your NAS.

Nothing to add to the postings above - still running 2.00.08, but if you need something from the box simply tell me what you need and I'll get it.
Perhaps one of the issues is that there is just one time occupied, the other left blank? See descriptions above ...

CU
Grumpftl

[QF006]

I filled in both columns, with the same time, to make sure. The behaviour was the same, the box powered on at the power-off time.
[Edit: the box powered on at 00:00, i.e. midnight, the power-off time was 02:00 (am)]
Siggy

[Thecus - Yvon]

Dear Sir,

If possible please provide the CONF.BIN to http://esupport.thecus.com for us to duplicate issue on our site, and we could download from SYSTEM->CONFGIG MGMT->DOWNLOD->CONF.BIN

[BramWithaar]

Yvon, i have exactly the same problem, different power on time. I created i ticket on the site you mentioned and uploaded my conf.bin.
Ticket id: JRN-526388

Solving this issue would be very appreciated. Scheduled power off isn't very usefull right now ;-)

[BramWithaar]

Thecus responded on my ticket: "This is a known issue and it will be fixed in the future version firmware, and sorry for the inconvenience."

[QF006]

This would be good news, I won't hold my breath though :-).
In this post http://forums.hexus.net/thecus-care-...ml#post1481022 they suggested that my hardware is bad. Luckily I am not the only one who wanted to use that feature in this way so maybe we will get a solution finally.

Siggy