RDM Devices#
Note
The endpoints listed on this page require a project to be loaded on the controller.
All properties described below relating to an RDM device’s status are obtained by the Status Monitor.
RDM Devices Overview#
GET#
Get an overview of RDM devices including their statuses.
GET /api/rdm_devices[?fixture=fixtureNumber][&offline=true][&unpatched=true]
fixture can be used the filter the response to devices patched to a single fixture. Set offline to true to return only offline devices, or set unpatched to true to return only unpatched devices.
One of fixture, offline, or unpatched is required, and no two parameters may be provided together.
Returns a JSON array of objects with the following attributes:
Attribute |
Value Type |
Description |
Value Example |
|---|---|---|---|
|
string |
RDM device UID |
|
|
number |
User number of the fixture this device is assigned to, or |
|
|
array of objects |
Issues found with this RDM device. See Device Issues. |
|
|
string |
Combined universe key and address (see Universe Key String Format). Only included if |
|
|
object |
RDM parameters cached from the latest status monitor run. Only included if |
|
|
string |
|
|
|
string |
ISO 8601-formatted timestamp of the last status update, or |
|
|
string |
A unique identifier for the RDM device variant. See Device Variant String Format. |
|
RDM Device#
GET#
Get a single RDM device including its status.
GET /api/rdm_devices/{deviceId}
Returns a JSON object with the same properties as contained in the RDM Devices Overview GET response.
PUT#
Patch an unpatched RDM device.
PUT /api/rdm_devices/{deviceId}/patch
The payload is a JSON object with the following attributes:
Attribute |
Value Type |
Description |
Value Example |
|---|---|---|---|
|
string |
The patch action to perform. |
|
Assign#
Assign a new RDM device to a fixture. When action is assign, the following additional attributes are required:
Attribute |
Value Type |
Description |
Value Example |
|---|---|---|---|
|
number |
User number of the fixture this RDM device will be assigned to. |
|
Replace#
Replace an offline RDM device. When action is replace, the following additional attributes are required:
Attribute |
Value Type |
Description |
Value Example |
|---|---|---|---|
|
string |
The RDM UID of the device to replace. |
|
Device Issues#
The status monitor tracks patch issues for each patched RDM device. The following issues are detected, discriminated by the issue field:
Address Mismatch#
The DMX start address of the RDM device does not match any patched addresses for the parent fixture on the universe upon which it was discovered.
Attribute |
Value Type |
Description |
Value Example |
|---|---|---|---|
|
string |
Issue type discriminator. |
|
|
array of integers |
Valid DMX start addresses for this device on the current universe. |
|
Output Mismatch#
The RDM device was discovered on an output upon which the parent fixture is not patched.
Attribute |
Value Type |
Description |
Value Example |
|---|---|---|---|
|
string |
Issue type discriminator. |
|
|
array of strings |
Valid outputs for this device. See Universe Key String Format. |
|
Device Variant String Format#
An RDM device variant string is structured as follows, with each of the 3 tokens formatted as decimal integers.
{manufacturer ID}-{model ID}-{software version ID}
Universe Key String Format#
A universe key string takes the form:
protocol:indexfor protocolsdmx,pathport,sacn,art-net;protocol:kinetPowerSupplyNum:kinetPortfor protocolkinet;protocol:remoteDeviceType:remoteDeviceNumfor protocolrio-dmx;protocol:remoteDeviceType:remoteDeviceNum:portfor protocolsedn,edn-spi.
Where:
kinetPowerSupplyNumis an integer;kinetPortis an integer;remoteDeviceTypecan berio08,rio44orrio80,edn10oredn20;remoteDeviceNumis an integer;portis an integer.
For example:
"dmx:1""rio-dmx:rio44:1"