id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,mlocked 2918,mythshutdown and mythbackend both use same setting for WakeupTimeFormat,adrian.wilkins@…,Isaac Richards,"The recommended program for the backend to set wakeup time is mythshutdown. The recommended program for setting wakeup time in the NVRAM is nvram-wakeup. mythshutdown insists on ISO-8601 date format for it's parameter. (yyyy-MM-ddThh:mm:ss) nvram-wakeup insists on time_t (seconds since epoch) Settings appear correct in the relevant dialogs because of hostname prevalence. Backend logs reveal that mythbackend is passing time_t to mythshutdown --setwakeup however. I have worked around this by setting ""both"" (local and NULL host) settings to ISO-8601 and the nvram-wakeup command to {{{date -d ""`echo $time | sed ""s/T/ /""`"" +%s | xargs nvram-wakeup -A -s}}} (the sed is necessary because GNU date cannot parse ISO-8601 despite being able to generate it). The fact that you can have perfectly correct settings in the dialogs that do not work needs sorting out (perhaps make a second setting for the time format, or even just allow the user to define time formats to use with tokens like time_1$ time_2$, etc.",defect,closed,minor,unknown,mythtv,head,medium,fixed,,,0