Difference between revisions of "Common Events Examples"

From LinuxMCE
Jump to: navigation, search
(New page: I've begun dealing with Events and Events handler and I'm describing few common events I've added to my setup. Please contribute yours as well...)
 
Line 1: Line 1:
 +
[[Category: Admin Website]]
 +
[[Category: Automation]]
 +
 
I've begun dealing with Events and Events handler and I'm describing few common events I've added to my setup. Please contribute yours as well...
 
I've begun dealing with Events and Events handler and I'm describing few common events I've added to my setup. Please contribute yours as well...
 +
 +
 +
[[Image:TimedEvents.jpg|thumb|200px|Timed Events Admin Page]]
 +
This is how you tell LinuxMCE to do certain tasks at specific times or at regular intervals.  For example, you may want to do something every hour, or at 9:00am on Sundays.
 +
<br style="clear:both;"/>
 +
 +
===House Mode Based Events===
 +
==Coming Home==
 +
 +
==Going To Sleep==
 +
 +
==Waking Up==
 +
 +
==Editing a Time Event==
 +
[[Image:EditTimedEvents.jpg|thumb|200px|Edit Timed Events Admin Page]]
 +
Simply choose the room for which you would like this Timed Event associated and at the bottom of the page you will see a drop down menu of all of the device in your system.  Choose the device you want to activate and then chose the command you would like to issue that device.  After adding this event, click Update to save the information.
 +
 +
If you would like to use this event as an alarm clock, choose what rooms this event should act as an alarm clock in. It will appear on the Orbiters' sleeping menu and you can turn the alarm on or off. Please note that currently, this function is only available via UI1 as there is no sleeping menu accessible on UI2.
 +
<br style="clear:both;"/>
 +
 +
==Advanced Menu==
 +
[[Image:AdvancedTimedEvents.jpg|thumb|200px|Advanced Timed Events Admin Page]]
 +
 +
This menu becomes available only after you have added the first Timed Event, but it does give you access to some predefined events that you can edit.
 +
Take the example of Sunset.  By clicking the commands text, you can now associate any device with this Timed Event.  After adding the device, you will receive a drop down menu with commands to issue this device.  This allows you to customize your system to your liking.
 +
 +
Please note that testing any advanced event will likely result in their deletion. This is a bug currently.

Revision as of 02:17, 17 July 2008


I've begun dealing with Events and Events handler and I'm describing few common events I've added to my setup. Please contribute yours as well...


Timed Events Admin Page

This is how you tell LinuxMCE to do certain tasks at specific times or at regular intervals. For example, you may want to do something every hour, or at 9:00am on Sundays.

House Mode Based Events

Coming Home

Going To Sleep

Waking Up

Editing a Time Event

Edit Timed Events Admin Page

Simply choose the room for which you would like this Timed Event associated and at the bottom of the page you will see a drop down menu of all of the device in your system. Choose the device you want to activate and then chose the command you would like to issue that device. After adding this event, click Update to save the information.

If you would like to use this event as an alarm clock, choose what rooms this event should act as an alarm clock in. It will appear on the Orbiters' sleeping menu and you can turn the alarm on or off. Please note that currently, this function is only available via UI1 as there is no sleeping menu accessible on UI2.

Advanced Menu

Advanced Timed Events Admin Page

This menu becomes available only after you have added the first Timed Event, but it does give you access to some predefined events that you can edit. Take the example of Sunset. By clicking the commands text, you can now associate any device with this Timed Event. After adding the device, you will receive a drop down menu with commands to issue this device. This allows you to customize your system to your liking.

Please note that testing any advanced event will likely result in their deletion. This is a bug currently.