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 NFC/RFID Bricklet. General information and technical specifications for the NFC/RFID 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 (ExampleScanForTags.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 33 34 35 36 37 38 39 40 41 | // For this example create an item linked to the state channel of your NFC RFID Bricklet.
import java.util.List;
import java.util.stream.Collectors;
val READER_STATE_IDLE = 128
val READER_STATE_REQUEST_TAG_ID_READY = 130
val READER_STATE_REQUEST_TAG_ID_ERROR = 194
val TAG_TYPE_TYPE2 = 2
rule "NFC"
when
// Change XYZ_State to the created item name
Item XYZ_State changed
then
val stateVal = XYZ_State.state as Number
val int state = stateVal.intValue
// Change XYZ to the UID of your NFC RFID Bricklet
val nfc = getActions("tinkerforge", "tinkerforge:brickletnfcrfid:XYZ")
if (state == READER_STATE_IDLE || state == READER_STATE_REQUEST_TAG_ID_ERROR) {
nfc.brickletNFCRFIDRequestTagID(TAG_TYPE_TYPE2)
} else if (state == READER_STATE_REQUEST_TAG_ID_READY) {
logInfo("Example", "tag id ready")
val ret = nfc.brickletNFCRFIDGetTagID()
val tagType = ret.get("tagType")
val tagID = ret.get("tid") as List<Short>
val tagLength = ret.get("tidLength")
val tag = String.join(" ", tagID.stream().limit(tagLength).map([i | String.format("0x%02X", i)]).collect(Collectors.toList()));
logInfo("Example", "tag id:" + tag)
// Read tag ID again in one second.
createTimer(now.plusSeconds(1), [|nfc.brickletNFCRFIDRequestTagID(2 as short)])
}
end
|
UID:
- tinkerforge:brickletnfcrfid:[UID]
Required firmware version:
- 2.0.0
Firmware update supported:
- yes
Channels: Actions:
State
¶The current state of the bricklet. Calling actions is only allowed in idle, ready and error states (e.g. all states >= 128). The following states are defined:
Type:
- Number:Dimensionless
UID:
- tinkerforge:brickletnfcrfid:[UID]:BrickletNFCRFIDState
Read only:
- Yes
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:brickletnfcrfid:[UID]")
val hwVersion = actions.brickletNFCRFIDGetIdentity().get("hardwareVersion") as short[]
logInfo("Example", "Hardware version: " + hwVersion.get(0) + "." + hwVersion.get(1) + "." + hwVersion.get(2))
brickletNFCRFIDRequestTagID
(short tagType)¶Parameters: |
|
---|
To read or write a tag that is in proximity of the NFC/RFID Bricklet you first have to call this function with the expected tag type as parameter. It is no problem if you don't know the tag type. You can cycle through the available tag types until the tag gives an answer to the request.
Currently the following tag types are supported:
After you call RequestTagID()
the NFC/RFID Bricklet will try to read
the tag ID from the tag. After this process is done the state will change.
You can either register the State
channel or you can poll
State
to find out about the state change.
If the state changes to RequestTagIDError it means that either there was
no tag present or that the tag is of an incompatible type. If the state
changes to RequestTagIDReady it means that a compatible tag was found
and that the tag ID could be read out. You can now get the tag ID by
calling GetTagID()
.
If two tags are in the proximity of the NFC/RFID Bricklet, this
function will cycle through the tags. To select a specific tag you have
to call RequestTagID()
until the correct tag id is found.
In case of any Error state the selection is lost and you have to
start again by calling RequestTagID()
.
The following constants are available for this function:
For tagType:
brickletNFCRFIDGetTagID
()¶Return Map: |
|
---|
Returns the tag type, tag ID and the length of the tag ID
(4 or 7 bytes are possible length). This function can only be called if the
NFC/RFID is currently in one of the Ready states. The returned ID
is the ID that was saved through the last call of RequestTagID()
.
To get the tag ID of a tag the approach is as follows:
RequestTagID()
State
or
State
channel)GetTagID()
The following constants are available for this function:
For tagType:
brickletNFCRFIDGetState
()¶Return Map: |
|
---|
Returns the current state of the NFC/RFID Bricklet.
On startup the Bricklet will be in the Initialization state. The initialization will only take about 20ms. After that it changes to Idle.
The functions of this Bricklet can be called in the Idle state and all of the Ready and Error states.
Example: If you call RequestPage()
, the state will change to
RequestPage until the reading of the page is finished. Then it will change
to either RequestPageReady if it worked or to RequestPageError if it
didn't. If the request worked you can get the page by calling GetPage()
.
The same approach is used analogously for the other API functions.
The following constants are available for this function:
For state:
brickletNFCRFIDAuthenticateMifareClassicPage
(int page, short keyNumber, short[] key)¶Parameters: |
|
---|
Mifare Classic tags use authentication. If you want to read from or write to
a Mifare Classic page you have to authenticate it beforehand.
Each page can be authenticated with two keys: A (key_number
= 0) and B
(key_number
= 1). A new Mifare Classic
tag that has not yet been written to can be accessed with key A
and the default key [0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF]
.
The approach to read or write a Mifare Classic page is as follows:
RequestTagID()
State
or State
channel)GetTagID()
and check if the
expected tag was found, if it was not found go back to step 1AuthenticateMifareClassicPage()
with page and key for the pageState
or State
channel)RequestPage()
or WritePage()
to read/write pageThe following constants are available for this function:
For keyNumber:
brickletNFCRFIDWritePage
(int page, short[] data)¶Parameters: |
|
---|
Writes 16 bytes starting from the given page. How many pages are written depends on the tag type. The page sizes are as follows:
The general approach for writing to a tag is as follows:
RequestTagID()
State
or
State
channel)GetTagID()
and check if the
expected tag was found, if it was not found got back to step 1WritePage()
with page number and dataState
or
State
channel)If you use a Mifare Classic tag you have to authenticate a page before you
can write to it. See AuthenticateMifareClassicPage()
.
brickletNFCRFIDRequestPage
(int page)¶Parameters: |
|
---|
Reads 16 bytes starting from the given page and stores them into a buffer.
The buffer can then be read out with GetPage()
.
How many pages are read depends on the tag type. The page sizes are
as follows:
The general approach for reading a tag is as follows:
RequestTagID()
State
or State
channel)GetTagID()
and check if the
expected tag was found, if it was not found got back to step 1RequestPage()
with page numberState
or State
channel)GetPage()
to retrieve the page from the bufferIf you use a Mifare Classic tag you have to authenticate a page before you
can read it. See AuthenticateMifareClassicPage()
.
brickletNFCRFIDGetPage
()¶Return Map: |
|
---|
Returns 16 bytes of data from an internal buffer. To fill the buffer
with specific pages you have to call RequestPage()
beforehand.
brickletNFCRFIDGetIdentity
()¶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.