64
edits
Changes
From Amahi Wiki
no edit summary
When the system is to be used again, simply wake it up with WOL (ref. http://en.wikipedia.org/wiki/Wake-on-LAN). There are many tools to generate WOL packets, and it is even possible to wake your server over the internet (good link: http://www.wakeonlan.me/).
==One Click installation==
The easiest way is to install Amahi Energy Saver via the Amahi One Click installation. Please see here: http://www.amahi.org/apps/amahi-energy-saver ==DownloadManual installation==Alternatively you can install manually:
Download the latest tested and released version here: http://code.google.com/p/amahienergysaver/downloads/list
https://github.com/jayrockk/Amahi-Energy-Saver
1. Copy the tar.gz file from the download page to some folder and unpack it with
[[Image:AES_Sunbird_6.jpg]]<br>
==MythTV integration (version 0.8.12 and later)==
Before Amahi Energy Saver suspends the HDA, it checks with MythTV server if any recordings are scheduled and if so sets the wake up timer accordingly. If the recording folder is one of the shares, it is ensured that Amahi Energy saver will not suspend the HDA while a recording is ongoing.
Please note that MythTV installation itself is non-trivial. The above assumes that MythTV is correctly installed and working.
==Let other apps control Amahi Energy Saver (version 0.8.12 and later)==
Sometimes you may wish to prevent Amahi Energy Saver from suspending the HDA while some other action is ongoing. There are two simple interfaces to achieve that.
1. Script interface
Amahi Energy Saver regularly checks the directory /usr/share/aes-lock for scripts and executes them. If any of the scripts returns an errorlevel of 1, the HDA will not be suspended. Both Bash (*.sh) and Ruby (*.rb) are supported.
The scripts can be extremely simple. In pseudocode a script looks like this:
{{Code|Code=
if (condition)
exit 1
else
exit 0
end
}}
2. Lock files
Amahi Energy Saver regularly checks the directory /usr/share/aes-lock for files with suffix '.lock'. As long as any such file exists, Amahi Energy Saver will not suspend the HDA. This is useful for other applications that support events. One Event may trigger the creation of the lock file, and another one may delete the lock file.
E.g., the event that shall cause the HDA to stay awake no matter what can call
{{Code|Code=touch /usr/share/aes-lock/some.lock}}
When the job is finished, the respective event should call
{{Code|Code=rm -r /usr/share/aes-lock/some.lock}}
Make sure to use individual names for the lock files, so that you don't accidentally delete the lock file of another application.
==Selecting ShutdownType==
==Logs and LogAnalyzer==
Depending on the version installed the logs are located in /usr/share/aes or /var/hda/web-apps/html/aes/lib. * From version 0.8.12 onwards, the log files have been moved to /var/log. In any case the files are named named aes.log*
In order to view the Amahi Energy Saver logs in the LogAnalyzer (ref. http://www.amahi.org/apps/loganalyzer) navigate on your LogAnalyzer homepage to "Admin Center" then "Sources" and finally klick "Add new Source". Configure the new source for the Energy Saver logs as shown in the screenshot below (note that the directory may have to be adjusted, see above):
4. Hit the "OK" butten, then right click on the symbol again, select "Exit" and and restart the program as described in 1.
5. Done! You should now be able to start your HDA by right double clicking on the icon in the symbol bar and select "Wake now"
