Alert Logs - Revision history

Wierdbeard65 at 07:48, 2 May 2010

2010-05-02T07:48:35Z

←Older revision		Revision as of 07:48, 2 May 2010
Line 2:		Line 2:
	[[Category: Automation]]		[[Category: Automation]]
	[[Category: Security]]		[[Category: Security]]
			{{versioninfo}}
	This lists all the alerts, security, fire, air quality, etc. The detection time is when the sensor was triggered. The expiration time is when the event was actually fired, or alarm sounded. This is the detection time plus however many seconds you specified in the 'Delay before Alarm' field. If someone entered their PIN code on an Orbiter before the expiration time, then the 'reset before expiration' box will be checked, meaning the alarm was never actually sounded. These events are, therefore, normal occurrences. Every time you enter the home, triggering a sensor, but successfully turn the alarm off before the time expires and the alarm sounds, an entry will appear in this log with that box checked.		This lists all the alerts, security, fire, air quality, etc. The detection time is when the sensor was triggered. The expiration time is when the event was actually fired, or alarm sounded. This is the detection time plus however many seconds you specified in the 'Delay before Alarm' field. If someone entered their PIN code on an Orbiter before the expiration time, then the 'reset before expiration' box will be checked, meaning the alarm was never actually sounded. These events are, therefore, normal occurrences. Every time you enter the home, triggering a sensor, but successfully turn the alarm off before the time expires and the alarm sounds, an entry will appear in this log with that box checked.

	Reset time is the first time that a user entered the pin code on an Orbiter after an alert, and the User column indicates who entered the PIN code. This way, if there was a problem, you can see who was the first person to return home after that alert.		Reset time is the first time that a user entered the pin code on an Orbiter after an alert, and the User column indicates who entered the PIN code. This way, if there was a problem, you can see who was the first person to return home after that alert.

Rwilson131 at 21:38, 22 November 2007

2007-11-22T21:38:53Z

←Older revision		Revision as of 21:38, 22 November 2007
Line 1:		Line 1:
	[[Category: Admin Website]]		[[Category: Admin Website]]
	[[Category: Automation]]		[[Category: Automation]]
			[[Category: Security]]
	This lists all the alerts, security, fire, air quality, etc. The detection time is when the sensor was triggered. The expiration time is when the event was actually fired, or alarm sounded. This is the detection time plus however many seconds you specified in the 'Delay before Alarm' field. If someone entered their PIN code on an Orbiter before the expiration time, then the 'reset before expiration' box will be checked, meaning the alarm was never actually sounded. These events are, therefore, normal occurrences. Every time you enter the home, triggering a sensor, but successfully turn the alarm off before the time expires and the alarm sounds, an entry will appear in this log with that box checked.		This lists all the alerts, security, fire, air quality, etc. The detection time is when the sensor was triggered. The expiration time is when the event was actually fired, or alarm sounded. This is the detection time plus however many seconds you specified in the 'Delay before Alarm' field. If someone entered their PIN code on an Orbiter before the expiration time, then the 'reset before expiration' box will be checked, meaning the alarm was never actually sounded. These events are, therefore, normal occurrences. Every time you enter the home, triggering a sensor, but successfully turn the alarm off before the time expires and the alarm sounds, an entry will appear in this log with that box checked.

	Reset time is the first time that a user entered the pin code on an Orbiter after an alert, and the User column indicates who entered the PIN code. This way, if there was a problem, you can see who was the first person to return home after that alert.		Reset time is the first time that a user entered the pin code on an Orbiter after an alert, and the User column indicates who entered the PIN code. This way, if there was a problem, you can see who was the first person to return home after that alert.

Rwilson131 at 21:32, 22 November 2007

2007-11-22T21:32:41Z

←Older revision		Revision as of 21:32, 22 November 2007
Line 1:		Line 1:
	~~<p>~~This lists all the alerts, security, fire, air quality, etc. The detection time is when the sensor was triggered. The expiration time is when the event was actually fired, or alarm sounded. This is the detection time plus however many seconds you specified in the 'Delay before Alarm' field. If someone entered their PIN code on an Orbiter before the expiration time, then the 'reset before expiration' box will be checked, meaning the alarm was never actually sounded. These events are, therefore, normal ~~occurrencies~~. Every time you enter the home, triggering a sensor, but successfully turn the alarm off before the time expires and the alarm sounds, an entry will appear in this log with that box checked.~~</p>~~		[[Category: Admin Website]]
	~~<p>~~Reset time is the first time that a user entered the pin code on an Orbiter after an alert, and the User column indicates who entered the PIN code. This way, if there was a problem, you can see who was the first person to return home after that alert.~~</p>~~		[[Category: Automation]]
			This lists all the alerts, security, fire, air quality, etc. The detection time is when the sensor was triggered. The expiration time is when the event was actually fired, or alarm sounded. This is the detection time plus however many seconds you specified in the 'Delay before Alarm' field. If someone entered their PIN code on an Orbiter before the expiration time, then the 'reset before expiration' box will be checked, meaning the alarm was never actually sounded. These events are, therefore, normal occurrences. Every time you enter the home, triggering a sensor, but successfully turn the alarm off before the time expires and the alarm sounds, an entry will appear in this log with that box checked.

			Reset time is the first time that a user entered the pin code on an Orbiter after an alert, and the User column indicates who entered the PIN code. This way, if there was a problem, you can see who was the first person to return home after that alert.

Jerry finn at 16:00, 16 March 2007

2007-03-16T16:00:40Z

←Older revision		Revision as of 16:00, 16 March 2007
Line 1:		Line 1:
	<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table><p>This lists all the alerts, security, fire, air quality, etc. The detection time is when the sensor was triggered. The expiration time is when the event was actually fired, or alarm sounded. This is the detection time plus however many seconds you specified in the 'Delay before Alarm' field. If someone entered their PIN code on an Orbiter before the expiration time, then the 'reset before expiration' box will be checked, meaning the alarm was never actually sounded. These events are, therefore, normal occurrencies. Every time you enter the home, triggering a sensor, but successfully turn the alarm off before the time expires and the alarm sounds, an entry will appear in this log with that box checked.</p>		<p>This lists all the alerts, security, fire, air quality, etc. The detection time is when the sensor was triggered. The expiration time is when the event was actually fired, or alarm sounded. This is the detection time plus however many seconds you specified in the 'Delay before Alarm' field. If someone entered their PIN code on an Orbiter before the expiration time, then the 'reset before expiration' box will be checked, meaning the alarm was never actually sounded. These events are, therefore, normal occurrencies. Every time you enter the home, triggering a sensor, but successfully turn the alarm off before the time expires and the alarm sounds, an entry will appear in this log with that box checked.</p>
	<p>Reset time is the first time that a user entered the pin code on an Orbiter after an alert, and the User column indicates who entered the PIN code. This way, if there was a problem, you can see who was the first person to return home after that alert.</p>		<p>Reset time is the first time that a user entered the pin code on an Orbiter after an alert, and the User column indicates who entered the PIN code. This way, if there was a problem, you can see who was the first person to return home after that alert.</p>

Jerry finn at 11:19, 14 March 2007

2007-03-14T11:19:25Z

←Older revision		Revision as of 11:19, 14 March 2007
Line 1:		Line 1:
	<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table><p>This lists all the alerts, security, fire, air quality, etc. The detection time is when the sensor was triggered. The expiration time is when the event was actually fired, or alarm sounded. This is the detection time plus however many seconds you ~~specifed~~ in the 'Delay before Alarm' field. If someone entered their PIN code on an Orbiter before the expiration time, then the 'reset before expiration' box will be checked, meaning the alarm was never actually sounded. These events are, therefore, normal ~~occurances~~. Every time you enter the home, triggering a sensor, but successfully turn the alarm off before the time expires and the alarm sounds, an entry will appear in this log with that box checked.</p>		<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table><p>This lists all the alerts, security, fire, air quality, etc. The detection time is when the sensor was triggered. The expiration time is when the event was actually fired, or alarm sounded. This is the detection time plus however many seconds you specified in the 'Delay before Alarm' field. If someone entered their PIN code on an Orbiter before the expiration time, then the 'reset before expiration' box will be checked, meaning the alarm was never actually sounded. These events are, therefore, normal occurrencies. Every time you enter the home, triggering a sensor, but successfully turn the alarm off before the time expires and the alarm sounds, an entry will appear in this log with that box checked.</p>
	<p>Reset time is the first time that a user entered the pin code on an Orbiter after an alert, and the User column indicates who entered the PIN code. This way, if there was a problem, you can see who was the first person to return home after that alert.</p>		<p>Reset time is the first time that a user entered the pin code on an Orbiter after an alert, and the User column indicates who entered the PIN code. This way, if there was a problem, you can see who was the first person to return home after that alert.</p>

Wikiadmin: Imported document

2006-06-05T16:45:55Z

Imported document

New page

<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table><p>This lists all the alerts, security, fire, air quality, etc. The detection time is when the sensor was triggered. The expiration time is when the event was actually fired, or alarm sounded. This is the detection time plus however many seconds you specifed in the 'Delay before Alarm' field. If someone entered their PIN code on an Orbiter before the expiration time, then the 'reset before expiration' box will be checked, meaning the alarm was never actually sounded. These events are, therefore, normal occurances. Every time you enter the home, triggering a sensor, but successfully turn the alarm off before the time expires and the alarm sounds, an entry will appear in this log with that box checked.</p>
<p>Reset time is the first time that a user entered the pin code on an Orbiter after an alert, and the User column indicates who entered the PIN code. This way, if there was a problem, you can see who was the first person to return home after that alert.</p>