Emergency Report Status Definitions

When viewing the Emergency Report or the CSV downloaded report, the following status are defined below: 

Report Status

Queued: The new test details need to be synced to the devices. 
Scheduled: The device has been programmed with the new test details.
Partially Queued/Scheduled: Some of the devices in the group need to be synced with the new test details.
Passed: The device passed the test.
Failed: The device failed the test as per the reason shown in the results field.
Action Required: Occurs when the test is in the current active window and has at least one failure. These failures can be rectified and retested within the same active window to clear the failures, i.e. battery or lamp failures can be replaced and a repair can be ran on the device with the re-test option selected to run the test again.
Delay Exceeded: The result from the device did not get synchronised to the cloud before the Test execution timeout.
Completed: All the devices have synchronised their results back to the cloud within the allotted time. This does not imply the test passed.
Cancelled: The test was cancelled and the device was told to abort the pending scheduled test. 

Results

When a test ends, it may end with a number of different Results, which describe how the test ended. Not all of these results imply failure.

No Results: The test passed successfully.

Comms Error: The Device could not be reached.
Dali Short: There is likely a short on the DALI line.
Lamp Failure: A problem was detected with the attached luminaire.
Em Lamp Failure: A problem was detected with the luminaire attached to an Emergency device.
In Bootloader: The device was bootloading during the test.
Circuit Failure: Device reporting based on the manufacture circuit test.
Control Gear Failure: Device reporting based on the manufacture circuit test.
Battery Duration Failure: The battery ran out before the test completed.
Battery Failure: Battery has failed either due to not present to not responding. 
Not Synced To Device: The device/control system didn't connect to the cloud in time or the control system instructed the device to test but when queried didn't run a test. In the case of the online control system, instructions to start a test are repeated at regular intervals. Issues could be that the device is in a comms error or one of the many states that the devices firmware prevents a test running (Eg. some devices won't let a test run if its in lamp failure).
Test Failed: The test failed.
Synced No Result:  The results were not synced from the device before the test timeout. This could be  because the device never started a test and was pending the entire period, or the device was not contactable to receive results from.
Missing Device: Device is no longer attached to the control system.
Not An Emergency Device: The device is not the type  
Duplicate Device: Multiple devices reporting the same identification.
Automatic Testing Not Supported: The device does not support automated testing, and would have to be tested manually.
Device Removed: The device was removed before test window completed.
User Completed: The test was completed as a result of user action. This can happen when resolving test schedule conflicts.
Device Replaced: The device was replaced during the test window completed.
Device Moved: The device was moved before the test window completed.