==General==
This project is approaching in solid betastage. It runs fine on my machineInstallation requires a little Linux knowledge. If you like it, however I need more feedback from the community to be sure that like it's stable enough for the general publicon facebook: http://www. So, please test and report your experience!facebook.com/pages/Amahi-Energy-Saver/218015224890441?sk=wall
3. As root, run
{{Code|Code=
./installfiles/aes-install.sh
}}
4. Navigate to When the installation is finished, reboot the computer. The config app is accessible at
{{Code|Code=
cd http:/usr/share/aeshda:6500
}}
and run
{{Code|Code=
./aes.rb --shownetworkhosts
}}
to show and select to add any currently active network host to the list of monitored hosts. Run
{{Code|Code=
./aes.rb --showmonitoredhosts
}}
to check the monitored hosts and delete the ones you want to remove.
5. As root, run
{{Code|Code=
service aes start
}}
to start the service. Be careful, when you start the service the sytem MAY go to sleep when you don't expect it. Once it works as you want it, run
{{Code|Code=
chkconfig aes on
}}
to make the service start on boot.
==Integration with Amahi calendar==
1. Open a terminal In the config app, select ical in the Calendar field. 2. Hit the "Apply button in the config app 3. Connect your client to the new calendar. NOTE: Please read this article if you are unsure how to do this: [[Calendars]] 4. Use your favourite calendar client to populate the calendar with events. Done! Your HDA will now wake up and stay powered on your hdaaccording to the events defined in the aes calendar. ==Selecting ShutdownType== The different options for ShutdownType are explained here:<br><br>
2 DeactivatedAmahi Energy Saver is running in the background, however it will never shutdown or suspend the HDA. Type {{Code|Code=su}} PoweroffThis is a full shutdown and provide your root passwordshould work on most systems. Some mainboards do not allow scheduled wakeup when using this method.<br><br>
3 ACPI_S1Legacy ACPI S1 state. Type {{Code|Code=cd /usr/share/aes}}Support depends on mainboard and Fedora support<br><br>
4. Type {{Code|Code= ACPI_S3Legacy ACPI S3 state./aes --calendar ical}}Support depends on mainboard and Fedora support<br><br>
4b ACPI_S4Legacy ACPI S4 state. To be sure, restart the service by typing {{Code|Code=service aes restart}}Support depends on mainboard and Fedora support<br><br>
5. Only required for 0.3.6 and below: Open your HDA dashboard and go memSuspend to "Settings" -memory, is intended to replace ACPI S1 but is not widely supported yet<br><br> "Calendars".
6. Only required for 0.3.6 and below: Add a new calendar named diskSuspend to disk, is intended to replace ACPI S4 but is not widely supported yet<codebr>aes</codebr>
7. Connect your client standbySuspend to the new calendar. NOTE: Please read this article if you are unsure how memory, is intended to do this: [[Calendars]]replace ACPI S3 but is not widely supported yet<br><br>
8. Use your favourite calendar client to populate When selecting the calendar with events.shutdown type the following procedure is suggested:<br><br>
* Start with Poweroff to do basic checking and configuration. Since this is the safest version, it should also be your resort in case of problems.<br><br>
* Once things are working, select either of the ACPI_S1..3 depending on what level of suspend you want<br><br>
Done! Your HDA will now wake up and stay powered on according to * If you are brave or the events defined in the aes calendarACPI options don't work, try mem, disk or standby.<br><br>
==Logs==
Logs are located in /usr/share/aes and named aes.log*
==OBSELETE: Command Line Interface==*Note: Currently root Root privileges are required to execute the CLI command. Navigate to /usr/share/aes to use the CLI correctly.
{{Code|Code=
}}
Displays command line help
==Selecting ShutdownType==
The different options for ShutdownType are explained here:<br><br>
Poweroff
This is a full shutdown and should work on most systems. Some mainboards do not allow scheduled wakeup when using this method.<br><br>
ACPI_S1
Legacy ACPI S1 state. Support depends on mainboard and Fedora support<br><br>
ACPI_S3
Legacy ACPI S3 state. Support depends on mainboard and Fedora support<br><br>
ACPI_S4
Legacy ACPI S4 state. Support depends on mainboard and Fedora support<br><br>
mem
Suspend to memory, is intended to replace ACPI S1 but is not widely supported yet<br><br>
disk
Suspend to disk, is intended to replace ACPI S4 but is not widely supported yet<br><br>
standby
Suspend to memory, is intended to replace ACPI S3 but is not widely supported yet<br><br>
When selecting the shutdown type the following procedure is suggested:<br><br>
* Start with Poweroff to do basic checking and configuration. Since this is the safest version, it should also be your resort in case of problems.<br><br>
* Once things are working, select either of the ACPI_S1..3 depending on what level of suspend you want<br><br>
* If you are brave or the ACPI options don't work, try mem, disk or standby.<br><br>
==Windows client==
5. Done! You should now be able to start your HDA by right clicking on the icon in the symbol bar and select "Wake now"
==Logs==
Logs are located in /usr/share/aes and named aes.log*
