Attributes:
Constants:
The FailedDevice class provides information about Leap Motion hardware that has been physically connected to the client computer, but is not operating correctly.
Failed devices do not provide any tracking data and do not show up in the Controller.devices() list.
Get the list of failed devices using Controller.failed_devices.
Note that FailedDevice objects can be invalid, which means that they do not contain valid information and do not correspond to a physical FailedDevice. Test for validity with the FailedDevice.is_valid property. However, the only way to get an invalid FailedDevice object is to create one yourself.
New in version 2.3.2.
Constructs a FailedDevice object.
An uninitialized FailedDevice object does not contain valid data. Get valid FailedDevice objects from a FailedDeviceList object obtained using the Controller.failed_devices property.
New in version 2.3.2.
| Type: | int |
|---|
The reason for device failure.
The following failure reasons are defined:
New in version 2.3.2.
| Type: | string |
|---|
The device plug-and-play id string.
New in version 2.3.2.
Compare FailedDevice object equality.
Two FailedDevice objects are equal if and only if both FailedDevice objects represent the exact same FailedDevice and both FailedDevices are valid.
New in version 2.3.2.
Compare FailedDevice object inequality.
Two FailedDevice objects are equal if and only if both FailedDevice objects represent the exact same FailedDevice and both FailedDevices are valid.
New in version 2.3.2.
An invalid FailedDevice object.
New in version 2.3.2.
The cause of the error is unknown.
New in version 2.3.2.
The device has a bad calibration record.
New in version 2.3.2.
The service cannot establish the required USB control.
New in version 2.3.2.
Not currently used.
New in version 2.3.2.
The device firmware is corrupt or failed to update.
New in version 2.3.2.
The device is unresponsive.
New in version 2.3.2.
The service cannot establish the required USB control interfaces.
New in version 2.3.2.