Bemerkung
Die openHAB-Dokumentation ist nur auf Englisch verfügbar.
Warnung
The openHAB bindings are still in beta, but the development was stopped.
This is the description of the openHAB API bindings for the One Wire Bricklet. General information and technical specifications for the One Wire Bricklet are summarized in its hardware description.
An installation guide for the openHAB API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Download (ExampleReadDS18B20Temperature.rules)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 | rule "Read DS18B20 Temperature"
when
System started // Replace with trigger of your choice
then
// Change XYZ to the UID of your One Wire Bricklet
val owActions = getActions("tinkerforge", "tinkerforge:brickletonewire:XYZ")
owActions.brickletOneWireWriteCommand(0, 78) // WRITE SCRATCHPAD
owActions.brickletOneWireWrite(0) // ALARM H (unused)
owActions.brickletOneWireWrite(0) // ALARM L (unused)
owActions.brickletOneWireWrite(127) // CONFIGURATION: 12-bit mode
owActions.brickletOneWireWriteCommand(0, 68) // CONVERT T (start temperature conversion)
createTimer(now.plusSeconds(1), [| // Wait for conversion to finish
owActions.brickletOneWireWriteCommand(0, 190) // READ SCRATCHPAD
val tLow = owActions.brickletOneWireRead().get("data") as int
val tHigh = owActions.brickletOneWireRead().get("data") as int
var float temperature = tLow + (tHigh * 256)
// Negative 12-bit values are sign-extended to 16-bit two's complement
if (temperature > 4096) {
temperature = temperature - 65536
}
// 12-bit mode measures in units of 1/16°C
logInfo("Example", "Temperature: " + temperature / 16.0 + "°C")
])
end
|
UID:
- tinkerforge:brickletonewire:[UID]
Required firmware version:
- 2.0.0
Firmware update supported:
- yes
Channels: Actions: Parameters:
- Communication LED Configuration – Type: Choice, Default: Show Communication
- The communication LED configuration. By default the LED shows 1-wire communication traffic by flickering. You can also turn the LED permanently on/off or show a heartbeat.
- Options: Off, On, Show Heartbeat, Show Communication
- Status LED Configuration – 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
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:brickletonewire:[UID]")
val hwVersion = actions.brickletOneWireGetIdentity().get("hardwareVersion") as short[]
logInfo("Example", "Hardware version: " + hwVersion.get(0) + "." + hwVersion.get(1) + "." + hwVersion.get(2))
brickletOneWireSearchBus
()¶Return Map: |
|
---|
Returns a list of up to 64 identifiers of the connected 1-Wire devices. Each identifier is 64-bit and consists of 8-bit family code, 48-bit ID and 8-bit CRC.
To get these identifiers the Bricklet runs the SEARCH ROM algorithm, as defined by Maxim.
The following constants are available for this function:
For status:
brickletOneWireResetBus
()¶Return Map: |
|
---|
Resets the bus with the 1-Wire reset operation.
The following constants are available for this function:
For status:
brickletOneWireWrite
(int data)¶Parameters: |
|
---|---|
Return Map: |
|
Writes a byte of data to the 1-Wire bus.
The following constants are available for this function:
For status:
brickletOneWireRead
()¶Return Map: |
|
---|
Reads a byte of data from the 1-Wire bus.
The following constants are available for this function:
For status:
brickletOneWireWriteCommand
(long identifier, int command)¶Parameters: |
|
---|---|
Return Map: |
|
Writes a command to the 1-Wire device with the given identifier. You can obtain
the identifier by calling SearchBus()
. The MATCH ROM operation is used to
write the command.
If you only have one device connected or want to broadcast to all devices you can set the identifier to 0. In this case the SKIP ROM operation is used to write the command.
The following constants are available for this function:
For status:
brickletOneWireGetCommunicationLEDConfig
()¶Return Map: |
|
---|
Returns the configuration as set by the thing configuration
The following constants are available for this function:
For config:
brickletOneWireGetChipTemperature
()¶Return Map: |
|
---|
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.
brickletOneWireGetStatusLEDConfig
()¶Return Map: |
|
---|
Returns the configuration as set by the thing configuration
The following constants are available for this function:
For config:
brickletOneWireGetSPITFPErrorCount
()¶Return Map: |
|
---|
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.
brickletOneWireReset
()¶Calling this function will reset the Bricklet. All configurations will be lost.
After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!
brickletOneWireGetIdentity
()¶Return Map: |
|
---|
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.