This is the description of the Shell API bindings for the RGB LED Bricklet. General information and technical specifications for the RGB LED Bricklet are summarized in its hardware description.
An installation guide for the Shell API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
| 1 2 3 4 5 6 7 | #!/bin/sh
# Connects to localhost:4223 by default, use --host and --port to change this
uid=XYZ # Change XYZ to the UID of your RGB LED Bricklet
# Set light blue color
tinkerforge call rgb-led-bricklet $uid set-rgb-value 0 170 234
 | 
Possible exit codes for all tinkerforge commands are:
argparse module is missingThe common options of the call and dispatch commands are documented
here. The specific command structure is shown below.
call rgb-led-bricklet [<option>..] <uid> <function> [<argument>..]¶| Parameters: | 
 | 
|---|
The call command is used to call a function of the RGB LED Bricklet. It can take several
options:
--help shows help for the specific call command and exits--list-functions shows a list of known functions of the RGB LED Bricklet and exitsdispatch rgb-led-bricklet [<option>..] <uid> <callback>¶| Parameters: | 
 | 
|---|
The dispatch command is used to dispatch a callback of the RGB LED Bricklet. It can
take several options:
--help shows help for the specific dispatch command and exits--list-callbacks shows a list of known callbacks of the RGB LED Bricklet and exitsrgb-led-bricklet <uid> <function> [<option>..] [<argument>..]¶| Parameters: | 
 | 
|---|
The <function> to be called can take different options depending of its
kind. All functions can take the following options:
--help shows help for the specific function and exitsGetter functions can take the following options:
--execute <command> shell command line to execute for each incoming
response (see section about output formatting
for details)Setter functions can take the following options:
--expect-response requests response and waits for itThe --expect-response option for setter functions allows to detect
timeouts and other error conditions calls of setters as well. The device will
then send a response for this purpose. If this option is not given for a
setter function then no response is sent and errors are silently ignored,
because they cannot be detected.
rgb-led-bricklet <uid> <callback> [<option>..]¶| Parameters: | 
 | 
|---|
The <callback> to be dispatched can take several options:
--help shows help for the specific callback and exits--execute <command> shell command line to execute for each incoming
response (see section about output formatting
for details)rgb-led-bricklet <uid> set-rgb-value <r> <g> <b>¶| Parameters: | 
 | 
|---|---|
| Output: | 
 | 
Sets the r, g and b values for the LED.
rgb-led-bricklet <uid> get-rgb-value¶| Output: | 
 | 
|---|
Returns the r, g and b values of the LED as set by set-rgb-value.
rgb-led-bricklet <uid> get-identity¶| Output: | 
 | 
|---|
Returns the UID, the UID where the Bricklet is connected to, the position, the hardware and firmware version as well as the device identifier.
The position can be 'a', 'b', 'c', 'd', 'e', 'f', 'g' or 'h' (Bricklet Port). A Bricklet connected to an Isolator Bricklet is always at position 'z'.
The device identifier numbers can be found here.