This is the description of the openHAB API bindings for the RGB LED Matrix Bricklet. General information and technical specifications for the RGB LED Matrix Bricklet are summarized in its hardware description.
An installation guide for the openHAB API bindings is part of their general description.
Required firmware version:
Firmware update supported:
Channels: Actions: Parameters:
- Frame Duration – Type: integer, Default: 0, Min: 0, Max: 65535
- The frame duration in milliseconds. This configures how fast the Frame Started Channel will trigger. 0 disables the callback.
- Status LED Config – Type: Choice, Default: Show Status
- The status LED configuration. By default the LED shows communication traffic between Brick and Bricklet, it flickers once for every 10 received data packets. You can also turn the LED permanently on/off or show a heartbeat. If the Bricklet is in bootloader mode, the LED is will show heartbeat by default.
- Options: Off, On, Show Heartbeat, Show Status
This channel is triggered directly after a new frame render is started. You should send the data for the next frame directly after this listener was triggered.
- Trigger (system.trigger)
The RGB(W) values for the LEDs.
Command format is a ','-separated list of integers. The first integer is the index of the first LED to set, additional integers are the values to set. Values are between 0 (off) and 255 (on). If the channel mapping has 3 colors, you need to give the data in the sequence R,G,B,R,G,B,R,G,B,... if the channel mapping has 4 colors you need to give data in the sequence R,G,B,W,R,G,B,W,R,G,B,W...
The data is double buffered and the colors will be transfered to the LEDs when the next frame duration ends. You can set at most 2048 RGB values or 1536 RGBW values.
For example sending 2,255,0,0,0,255,0,0,0,255 will set the LED 2 to red, LED 3 to green and LED 4 to blue.
Actions can be used in rules by creating an action object. All actions return a Map<String, Object>. Returned values can be accessed by name, sometimes the type deduction needs some hints, as shown below:
val actions = getActions("tinkerforge", "tinkerforge:brickletrgbledmatrix:[UID]") val hwVersion = actions.brickletRGBLEDMatrixGetIdentity().get("hardwareVersion") as short logInfo("Example", "Hardware version: " + hwVersion.get(0) + "." + hwVersion.get(1) + "." + hwVersion.get(2))
Returns the red LED values as set by LED Values.
Returns the green LED values as set by LED Values.
Returns the blue LED values as set by LED Values.
Sets the 64 red LED values of the matrix.
Sets the 64 green LED values of the matrix.
Sets the 64 blue LED values of the matrix.
Returns the frame duration as set by the thing configuration.
If you set the frame duration to 0 (see the thing configuration), you can use this function to transfer the frame to the matrix.
Returns the current supply voltage of the Bricklet.
Returns the temperature as measured inside the microcontroller. The value returned is not the ambient temperature!
The temperature is only proportional to the real temperature and it has bad accuracy. Practically it is only useful as an indicator for temperature changes.
Returns the configuration as set by the thing configuration
The following constants are available for this function:
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
The errors counts are for errors that occur on the Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.
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). The Raspberry Pi HAT (Zero) Brick is always at position 'i' and the Bricklet connected to an Isolator Bricklet is always as position 'z'.
The device identifier numbers can be found here.