Skip to content

Commit a6bb537

Browse files
authored
[irtrans] Adapt documentation (openhab#17521)
* Adapt documentation Signed-off-by: Leo Siepel <[email protected]>
1 parent ed45e75 commit a6bb537

File tree

1 file changed

+51
-16
lines changed

1 file changed

+51
-16
lines changed

bundles/org.openhab.binding.irtrans/README.md

+51-16
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,15 @@
11
# IRtrans Binding
22

3-
This binding integrates infrared receivers and blasters manufactured by IRtrans (www.irtrans.de)
3+
This binding integrates infrared receivers and blasters manufactured by IRtrans <www.irtrans.de>
44

55
## Supported Things
66

7-
The _ethernet_ Bridge supports the Ethernet (PoE) IRtrans transceiver equipped with an on-board IRDB database. Blasters and receivers are defined as Channels on the Bridge, but one can also define blasters as a _blaster_ child Thing on the Bridge.
7+
This binding supports the following Thing types
8+
9+
| Thing | Thing Type | Description |
10+
|----------|------------|----------------------------------------------------------------------------|
11+
| ethernet | Bridge | Ethernet (PoE) IRtrans transceiver equipped with an on-board IRDB database |
12+
| blaster | Thing | Child thing representing an IR Blaster |
813

914
## Discovery
1015

@@ -16,30 +21,60 @@ There is no specific binding configuration required.
1621

1722
## Thing Configuration
1823

19-
The _ethernet_ Bridge requires an _ipAddress_ IP address and _portNumber_ TCP port number in order to configure it. Optionally, one can add the following parameters to the configuration:
24+
### `ethernet` Bridge Configuration
25+
26+
| Parameter | Description | Config | Default |
27+
|-------------------|-------------------------------------------------------------------------------------------------------|----------|---------|
28+
| ipAddress | The IP address or hostname of the bridge | Required | - |
29+
| portNumber | The port number the bridge listens on | Required | - |
30+
| bufferSize | Buffer size used by the TCP socket when sending and receiving commands to the transceiver | Optional | 1024 |
31+
| responseTimeOut | Specifies the time milliseconds to wait for a response from the transceiver when sending a command | Optional | 100 |
32+
| pingTimeOut | Specifies the time milliseconds to wait for a response from the transceiver when pinging the device | Optional | 1000 |
33+
| reconnectInterval | Specifies the time seconds to wait before reconnecting to a transceiver after a communication failure | Optional | 10 |
2034

21-
_bufferSize_ : Buffer size used by the TCP socket when sending and receiving commands to the transceiver (default: 1024)
22-
_responseTimeOut_ : Specifies the time milliseconds to wait for a response from the transceiver when sending a command (default: 100)
23-
_pingTimeOut_ : Specifies the time milliseconds to wait for a response from the transceiver when pinging the device (default: 1000)
24-
_reconnectInterval_ : Specifies the time seconds to wait before reconnecting to a transceiver after a communication failure (default: 10)
35+
### `blaster` Thing Configuration
2536

26-
The _blaster_ Thing requires a _led_ parameter to specify on which infrared commands will be emitted, _remote_ the remote or manufacturer name which's commands will be allowed, as defined in the IRtrans server database that is flashed into the transceiver (can be ' \*' for 'any' remote), and _command_ the name of the command will be allowed, as defined in the IRtrans server database that is flashed into the transceiver (can be '*' for 'any' command).
37+
The `blaster` Thing reuires an `ethernet` (Bridge) before it can be used.
38+
39+
| Parameter | Description | Config | Default |
40+
|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|---------|
41+
| led | Specifies the led on which infrared commands will be emitted | Required | - |
42+
| remote | The remote or manufacturer name which's commands will be allowed, as defined in the IRtrans server database that is flashed into the transceiver (can be ' \*' for 'any' remote) | Required | - |
43+
| command | The name of the command will be allowed, as defined in the IRtrans server database that is flashed into the transceiver (can be '*' for 'any' command) | Required | - |
2744

2845
## Channels
2946

30-
The _ethernet_ Thing supports the following Channel Types:
47+
### `ethernet` Bridge Channels
48+
49+
| Channel Type ID | Item Type | Description | |
50+
|-----------------|-----------|-------------------------------------------------------------------------------------|--------------------------------------------|
51+
| blaster | String | Send (filtered) infrared commands over the specified blaster LED of the transceiver | [Channel configuration](#blaster-channel) |
52+
| receiver | String | Receive (filtered) infrared commands on the receiver LED of the transceiver | [Channel configuration](#receiver-channel) |
53+
54+
### `ethernet` Bridge Channel Configuration
55+
56+
#### `blaster` Channel
57+
58+
| Parameter | Description | Config | Default |
59+
|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|---------|
60+
| led | Specifies the led on which infrared commands will be emitted | Required | - |
61+
| remote | The remote or manufacturer name which's commands will be allowed, as defined in the IRtrans server database that is flashed into the transceiver (can be ' \*' for 'any' remote) | Required | - |
62+
| command | The name of the command will be allowed, as defined in the IRtrans server database that is flashed into the transceiver (can be '*' for 'any' command) | Required | - |
3163

32-
| Channel Type ID | Item Type | Description |
33-
|-----------------|-----------|-------------------------------------------------------------------------------------|
34-
| blaster | String | Send (filtered) infrared commands over the specified blaster LED of the transceiver |
35-
| receiver | String | Receive (filtered) infrared commands on the receiver LED of the transceiver |
64+
#### `receiver` Channel
3665

37-
The _blaster_ Channel Type requires a _led_ configuration parameter to specify on which infrared commands will be emitted, _remote_ the remote or manufacturer name which's commands will be allowed, as defined in the IRtrans server database that is flashed into the transceiver (can be '\*' for 'any' remote), and _command_ the name of the command will be allowed, as defined in the IRtrans server database that is flashed into the transceiver (can be '*' for 'any' command).
66+
| Parameter | Description | Config | Default |
67+
|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|---------|
68+
| remote | The remote or manufacturer name which's commands will be allowed, as defined in the IRtrans server database that is flashed into the transceiver (can be ' \*' for 'any' remote) | Required | - |
69+
| command | The name of the command will be allowed, as defined in the IRtrans server database that is flashed into the transceiver (can be '*' for 'any' command) | Required | - |
3870

39-
The _receiver_ Channel Type requires _remote_ the remote or manufacturer name which's commands will be allowed, as defined in the IRtrans server database that is flashed into the transceiver (can be '\*' for 'any' remote), and _command_ the name of the command will be allowed, as defined in the IRtrans server database that is flashed into the transceiver (can be '*' for 'any' command).
71+
### `blaster` Thing Channels
4072

41-
The _blaster_ Thing supports a _io_ Channel (of Item Type String) that allows to read infrared commands received by the blaster, as well as to write infrared commands to be sent by the blaster.
73+
| Channel Type ID | Item Type | Description | |
74+
|-----------------|-----------|---------------------------------------------------------------------------------------------------------------------------|--------------------------------------|
75+
| io | String | Allows to read infrared commands received by the blaster, as well as to write infrared commands to be sent by the blaster | [Channel configuration](#io-channel) |
4276

77+
*note*
4378
The IRtrans transceivers store infrared commands in a "remote,command" table, e.g. "telenet,power". Sending the literal text string "telenet,power" to the transceiver will make the transceiver "translate" that into the actual infrared command that will be emitted by the transceiver. A "remote,command" string sent to a Channel that does not match the defined filter will be ignored.
4479

4580
## Full Example

0 commit comments

Comments
 (0)