Node-red-contrib-xkeys_backlight NPM

node-red-contrib-xkeys_backlight

This is another in a collection of Node-RED nodes which enable access to X-keys physical devices using the Device Control Data Protocol (DCDP).

Dedicated Node-RED nodes for each X-key event of interest (button, jog, joystick, etc.) will communicate, using MQTT, with a lightweight DCDP server, whose sole purpose is to mediate access to any physically attached X-keys devices.

This xkeys_backlight node encapsulates Backlight operations of enabling or disabling the Hue Cannels for any or specific X-keys devices.

Installation

This node requires dcdp-server version 0.1.1 to be running. Please follow the instructions at the dcdp-server development repository to install it or, to upgrade an existing installation, see the dcdp-server upgrade instructions.

The node-red-contrib-xkeys_backlight node itself is best installed from Node-RED's Palette manager. Go to the Palette manager's Install tab and search for node-red-contrib-dcdp_backlight; then Install it once found. If not found, press the Refresh module list button (two semicircular arrows) and search again.

When installed, a new xk Backlight node will be found in the palette tab in the dedicated Xkeys category.

Usage

The node's configuration editor can be used to set the target Xkeys device, as well as the target button(s) to operate on. Settings in the configuration editor may be overridden by settings the relevant field in the msg.payload of an incoming node. A msg.payload containing only an action field activates backlights with whatever settings are currently configured in the configuration editor. The msg.payload expected by the xkey_backlight node is as follows:

{ action: STARTSTOP, control_id: ID, flashing: YESNO, hue_channels: CHANNELS, pid_list: [e1,e2,..,eN] | pid: PID, unit_id:UID, duplicate_id:DUPID}

where

STARTSTOP is either of "start" or "stop". This is the only required field. All other fields are optional and, if not provided, the configured settings of the node are used.
ID indicates which button(s) to operate on. Multiple buttons may be targeted by entering comma separated ID numbers in this field e.g. 1,3,6,7 whereas an empty buttonid value indicates that all available backlights should be targeted.
YESNO is one of true or false
CHANNELS is a string describing the which channels will be active e.g. ff0000 => red, 0000ff => blue. Not all devices are capable of all hues.
PID is the Product Id of the device. Alternatively and array of device PIDs may be specified instead using the pid_list field.
UID is the Unit Id of the device.
DUPID is the Duplicate Id of the device (allocated by the DCDP server to distinguish devices with same PID & UID).

An example flow is provided in the examples directory to demonstrate activation of the xkeys_backlight node.

the first method is via the toggle switches attached to the node itself.
a second method is to use Inject nodes with appropriately crafted msg.payloads.

The lower example uses the second method so that an xkeys_button node activates the xkeys_backlight node by via a function node (labeled Button to Backlight) which is configured to use the button node's "down" and "up" actions to activate the red and blue channels respecitvely, as well as setting a pidlist derived from whichever physical device is activating the _button node.

Note the use of an xkeys_intensity node set the intensity of each channel. In this case the blue and red intensities are both set to maximum.

Issues

When configuring the node, a drop down list of possible devices shoud be available. If not, instead displaying just a note to Press Deploy button to see device list, first follow that advice. If that is unsuccessful (still no list of possible devices), then check the status of the xkeys-server by running the command sudo systemctl status xkeys-server in a terminal. Typical output of a normally running xkeys-server will be:

pi@pi3b:~ $ sudo systemctl status dcdp-server
● dcdp-server.service - Run dcdp-server as background service
Loaded: loaded (/etc/systemd/system/dcdp-server.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2021-10-14 09:31:55 AEST; 23h ago

whereas a non-running dcdp-server will show something like:

pi@pi3b:~ $ sudo systemctl status dcdp-server
● dcdp-server.service - Run dcdp-server as background service
Loaded: loaded (/etc/systemd/system/dcdp-server.service; enabled; vendor preset: enabled)
Active: failed (Result: timeout) since Fri 2021-10-15 08:41:37 AEST; 19s ago

If necessary, (re)start the dcdp-server with sudo systemctl restart xkeys-server