This is the description of the MQTT 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 MQTT API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
1 2 3 4 5 | # Change XYZ to the UID of your RGB LED Bricklet
setup:
# Set light blue color
publish '{"r": 0, "g": 170, "b": 234}' to tinkerforge/request/rgb_led_bricklet/XYZ/set_rgb_value
|
All published payloads to and from the MQTT bindings are in JSON format.
If an error occures, the bindings publish a JSON object containing the error message as member _ERROR
.
It is published on the corresponding response topic: .../response/...
for .../request/...
and .../callback/...
for .../register/...
.
request/
rgb_led_bricklet/
<UID>/
set_rgb_value
¶Request: |
|
---|---|
Response: |
|
Sets the r, g and b values for the LED.
request/
rgb_led_bricklet/
<UID>/
get_rgb_value
¶Request: |
|
---|---|
Response: |
|
Returns the r, g and b values of the LED as set by request/rgb_led_bricklet/<UID>/set_rgb_value
.
request/
rgb_led_bricklet/
<UID>/
get_identity
¶Request: |
|
---|---|
Response: |
|
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. If symbolic output is not disabled, the device identifier is mapped to the corresponding name in the format used in topics.
The display name contains the RGB LED's name in a human readable form.