KNX - stuck with item config

Hi folks,

I’m stuck with getting KNX doing things and ask for your help or pointing me to articles I should have read.

Setup in a nutshell:

  • openhab 1.8, running on my mac
  • KNX binding enabled
  • calimero logging enabled according to the binding-wiki ()
  • GIRA KNX IP Router

According to the log openhab and KNX talking to each other. If a press a switch on the wall a lamp goes on or off and the log shows „indication from 1.1.57“ and also from 1.1.4.

1.14 is the address written on the actor (model hager TXA207C). The other one seems to be the switch.

2016-03-12 15:15:54.050 [INFO ] [tuwien.auto.calimero ] - [ManagedService Update Queue] KNXnet/IP Tunneling 192.168.1.33:3671: establish connection from /192.168.1.34:50445 to /192.168.1.33:3671
2016-03-12 15:15:54.052 [INFO ] [tuwien.auto.calimero ] - [ManagedService Update Queue] KNXnet/IP Tunneling 192.168.1.33:3671: wait for connect response from /192.168.1.33:3671 …
2016-03-12 15:15:54.156 [INFO ] [tuwien.auto.calimero ] - [KNXnet/IP receiver] KNXnet/IP Tunneling 192.168.1.33:3671: using server-assigned data endpoint /192.168.1.33:3671
2016-03-12 15:15:54.156 [INFO ] [tuwien.auto.calimero ] - [ManagedService Update Queue] KNXnet/IP Tunneling 192.168.1.33:3671: connection established
2016-03-12 15:16:28.815 [INFO ] [tuwien.auto.calimero ] - [KNXnet/IP receiver] link 192.168.1.33:3671: indication from 1.1.57
2016-03-12 15:16:54.156 [DEBUG] [tuwien.auto.calimero ] - [KNXnet/IP heartbeat monitor] KNXnet/IP Tunneling 192.168.1.33:3671: sending connection state request, attempt 1
2016-03-12 15:16:59.912 [INFO ] [tuwien.auto.calimero ] - [KNXnet/IP receiver] link 192.168.1.33:3671: indication from 1.1.57
2016-03-12 15:17:54.156 [DEBUG] [tuwien.auto.calimero ] - [KNXnet/IP heartbeat monitor] KNXnet/IP Tunneling 192.168.1.33:3671: sending connection state request, attempt 1
2016-03-12 15:18:54.158 [DEBUG] [tuwien.auto.calimero ] - [KNXnet/IP heartbeat monitor] KNXnet/IP Tunneling 192.168.1.33:3671: sending connection state request, attempt 1
2016-03-12 15:19:54.162 [DEBUG] [tuwien.auto.calimero ] - [KNXnet/IP heartbeat monitor] KNXnet/IP Tunneling 192.168.1.33:3671: sending connection state request, attempt 1
2016-03-12 15:20:48.309 [INFO ] [tuwien.auto.calimero ] - [KNXnet/IP receiver] link 192.168.1.33:3671: indication from 1.1.59
2016-03-12 15:20:48.459 [INFO ] [tuwien.auto.calimero ] - [KNXnet/IP receiver] link 192.168.1.33:3671: indication from 1.1.4
2016-03-12 15:20:54.162 [DEBUG] [tuwien.auto.calimero ] - [KNXnet/IP heartbeat monitor] KNXnet/IP Tunneling 192.168.1.33:3671: sending connection state request, attempt 1
2016-03-12 15:21:02.609 [INFO ] [tuwien.auto.calimero ] - [KNXnet/IP receiver] link 192.168.1.33:3671: indication from 1.1.59
2016-03-12 15:21:02.759 [INFO ] [tuwien.auto.calimero ] - [KNXnet/IP receiver] link 192.168.1.33:3671: indication from 1.1.4

Frankly, I hoped that the knx log is more specific and telling me what the switch is sending to the actor so that I could have transferred to openhab items and rules.

So how to come from here to switching the lamp from openhab?

First fundamental question: do I sent a „switch on“ command to the switch or to the actor? Might sound stupid, but some of my switches have an LED indicating if the light is on or not.

Lets assume we send it to the actor:

What I found is a description of the ETS settings of the TXA207C containing functions and a object list. And in that list there is for example a number 0 Name Output 1 ON / OFF length 1 bit C R W U. That looks like something I might need.

How does this translate to KNX datapoint and how then to a KNX item?

Sorry for maybe stupid questions and maybe ignorance against existing documentation, but I don’t get it.

For communication with knx you need to know the GroupAdresses, you can get them from a Group Monitor such as in eibd SDK or implemented in ETS. openHAB only shows GA which are configured in .items. All in all the best way is to have the full Documentation of the knx installation, especially the GA assignment and DPT. DPT is the type of data (Bit, 2-Bit, 4-Bit, Byte a.s.o.) and how to construe the data (e.g. temperature, voltage, current or windspeed for float values).

Thanks. Got the address for one switch and got it running.

More questions will follow when I get the rest of the ETS settings :slight_smile: