Each event that occurs on the system is recorded. An event that is an action initiated by an administrator is called an audit event and is managed separately from other event types. Audit events are described in Monitoring Audit Log. Sometimes, an action may result in one or more events. There may be a separate event for when an action was started, when it was completed successfully or failed, or when it was aborted. Other events occur due to periodic actions that are performed by the system or fixture.
For example, periodically, a fixture performs a health self-check. If it detects any problem, it then communicates the problem to Manage, which may generate an event. Likewise, Manage performs periodic health check actions, and if it detects a problem, it may generate an event.
Note that some problem detections do not cause an event to be reported. If a problem is a persistent fault condition, then an event will only be reported the first time it is detected. For example, if the ballast in a fixture ceases to function, then the first time it is detected, the event fixture out is reported. Until the fault condition is cleared, no additional events are reported for the condition.
The events can be accessed from the Events tab by selecting either Facilities or Profiles.
Below is a list of the events, and where appropriate, the possible action(s) that the administrator should pursue to resolve each fault condition:
Attached Storage Backup – Informational report about the daily scheduled backup. The daily backup runs every day at 1:00 am and 4:00 am, backing up the system file to an external storage drive. If the system does not find an attached storage device to the EM server, the backup script stores the backup file on the server and generates a critical event.
Auto Recovering Lost Sensors – The daily auto-recovery runs every day at 2:00 am to recover unreachable commissioned sensors and recommissions them by sending the configured wireless settings to these sensors. During this time, the following event messages are sent.
Attempting to find and recover sensors that lost communication: This event is sent at the beginning of the sensor recommission operation for a gateway.
xx:yy:zz sensor could not be recovered: xx:yy:zz is the sensor's MAC address that failed to acknowledge recommissioning.
Attempt to recover lost sensors is complete. Discovered ‘NN’ number of sensors that failed to communicate. Recovered ‘NN’ number of sensors.
Recommissioning failed: Gateway did not move to the default channel. This is an alarm with the severity of ‘Major’ as this is a serious network condition warning.
BACnet – Informational reports about the service that supports the BACnet protocol. The service is started when the EM is started, such as after system power on, or after system image upgrade. The event types are:
Service started
Service stopped
Configuration changed
Bad Profile – Reported by a Fixture (SU).
The fixture determined a corrupted value in a profile in RAM and reported it to Manage. Try power cycling the fixture. If the problem is not resolved, then replace the sensor (SU) of the fixture.
The fixture determined a corrupted value in a profile in ROM and reported it to Manage (which means that flash memory in the SU is corrupted). Try power cycling the fixture. If the problem is not resolved, then replace the sensor (SU) of the fixture.
Commissioning – Informational reports on the commissioning process, which is initiated by an administrator. The event types are:
Started
Start failed
Timed out due to inactivity
Aborted
Succeeded
Discovery – Informational reports on the discovery process for devices (sensors, gateways, and ERCs), which is initiated by an administrator. The event types are:
Started
Start failed
Timed out before finding a specified count of fixtures
Found specified count of fixtures
Download Power Usage Characteristics – When used in conjunction with the Lamp Outage function, it detects lamps that do not conform to the specified behavior.
Demand Response Condition – Informational reports on the DR process, which is initiated by an administrator.
ERC Commissioning – Information on ERC commissioning.
ERC Discovery – Message about the discovery of an ERC via a Gateway.
ERC Upgrade – This event relates to the image upgrade of an ERC.
Erroneous energy reading – The problem is detected, and an event is created when the energy usage reported by a fixture during a five-minute interval is too high. The reported energy usage is discarded, and a value is computed for the energy usage of the five-minute interval.
Fixture associated Group Changed – Not in use.
Fixture Configuration Upload – This implies that fixture details are being uploaded externally, usually for a fixture discovered from EMConfig.
Fixture CPU Usage is High – The problem is detected and reported by the fixture, and Manage creates an event. This could indicate a damaged Sensor unit (SU). Try replacing it.
Fixture CU Failure – The problem is reported by the fixture, and Manage creates an event. Try power cycling the fixture. If the problem is not resolved, replace the cable between the Control Unit and the sensor. If the problem persists, first try replacing the CU, and if the problem persists, then replace the sensor.
Fixture Emergency Lighting Test – Reports that the emergency lighting test on the fixture has ended.
Fixture Group Change – This implies that a fixture is being assigned to a group or switch.
Fixture Hardware Failure – The problem is detected and reported by the fixture, and the EM creates an event. The fixture report will specify the state, the sub-system or component where the problem occurred, and the fault type. The state could be at power-on-self-test (POST) time, initial time, or runtime. It also reports the fault type. Typically, this issue is resolved by replacing the SU.
Fixture Image checksum failure – The fixture detected that the checksum for its image is incorrect. Try power cycling the fixture. If the problem persists, then try upgrading the image. If the problem still persists, then replace the SU.
Fixture out – Reports that occur when an SU is periodically reporting its energy usage, and the first time it is detected that either the ballast or bulbs are out for a fixture. Typically, this must be resolved by replacing the component that has ceased functioning.
Fixture too hot – The problem is detected and reported by the fixture, and Manage creates an event. The temperature reported by the fixture is included in the event report. To resolve, check for unusual heat sources. If none are found, this could indicate a defective temperature sensor in the SU. Try replacing the SU.
Fixture Upgrade – Informational reports on the image upgrade process for a fixture, which is initiated by an administrator. The event types are:
Image upgrade initiated
Image upgrade didn’t start
Image upgrade started
Image upgrade aborted
Image upgrade succeeded
Image upgrade failed
Gateway configuration error – The problem is detected, and an event is created. This event occurs when the configured and current wireless parameters are different on the gateway. After reporting, the EM auto-corrects the problem by sending the configured wireless parameters to the gateway. To resolve, try power cycling the gateway. When done, make sure that the gateway gets an IP Address. Verify by pinging the gateway from the EM or from a system on the building network.
Gateway Connection Failure – The problem is detected, and an event is created by the EM when an SSL connection cannot be established with the gateway because it is unreachable or the SSL authentication fails.
Gateway unreachable – This implies that the gateway is not reachable from the EM.
Gateway Upgrade – Informational reports on the image upgrade process for a gateway, which is initiated by an administrator. The event types are:
Image upgrade started
Image Upgrade didn’t start
Image upgrade aborted
Image upgrade succeeded
Image upgrade failed
Network Notification – This implies that network assignments have been changed.
Placed Fixture Upload – This implies that a fixture is being uploaded with a Mac Id that is already commissioned.
Plugload High Current- This generates an alarm when the plugload current (in Amperes) is higher than the specified limit.
Profile Mismatch- This event is triggered when a profile push or a group profile push does not go through due to a mismatch in the profiles of fixtures and fixture groups.
Profile Mismatch User Action – This event is triggered during a profile push or a group profile push when although the sensor profile matches the group profile, the sensor profile checksum does not match the scheduled sensor profile checksum or the global profile checksum.
Push profile – The fixture profile has changed, but it has not yet been stored on the fixture. This occurs when a fixture is powered off, or there is no network connectivity between the fixture and EM, and when the fixture’s profile is changed in the EM.
Scheduler – During an EM image upgrade, the scheduler is stopped and later restarted. Additionally, if it is found to be not running, the system health checker will restart the scheduler.
Sftp Remote Backup – Informational report about the daily scheduled backup. The daily backup runs every day at 1:00 am, and 4:00 am, backing up the system file to a remote server using a secure file transfer protocol. A critical event is sent if the system cannot upload the backup file to the remote server but has stored it on the server.
Wireless Parameters – This event is generated when a fixture or a plugload is deleted, but per minute statistics are still available from the Gateway operating in a normal mode.
