I've DSM 5.0 and the newest APM installed.
The time I set in the powerdown page is suppose to shutdown at 22:00, but the time seen on the welcome page is 23:00.
This occurred today maybe/because of the change from winter to summertime perhaps?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for reporting the issue. It is indeed due to daylight saving day.
The computation gets wrong because I split the computation between date part (e.g. mon-sun) and time part (e.g. ... at 22:00) then add time offset (e.g. 22 * 3600) to computed date timestamp.
When daylight saving day occurs, e.g. today, this gives:
timestamp1 for today at 00:00 (the date part computation) + 22 * 3600, but since at 2am, it was already 3am, this makes the timestamp be 23:00.
Will try to fix this in a simple manner sooner or later (I have 6 months for that :-) )
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've DSM 5.0 and the newest APM installed.
The time I set in the powerdown page is suppose to shutdown at 22:00, but the time seen on the welcome page is 23:00.
This occurred today maybe/because of the change from winter to summertime perhaps?
Thank you for reporting the issue. It is indeed due to daylight saving day.
The computation gets wrong because I split the computation between date part (e.g. mon-sun) and time part (e.g. ... at 22:00) then add time offset (e.g. 22 * 3600) to computed date timestamp.
When daylight saving day occurs, e.g. today, this gives:
timestamp1 for today at 00:00 (the date part computation) + 22 * 3600, but since at 2am, it was already 3am, this makes the timestamp be 23:00.
Will try to fix this in a simple manner sooner or later (I have 6 months for that :-) )
Thanks for your answer.
And indeed, now the time is correctly show at the welcome page.
Just fixed the issue. Will be available in next release ... should be ok for next daylight saving :-)