KNX binding problem

Add-ons Bindings
1

I’m quite a while playing around with the knx binding in OH1 and OH2 and get this not working properly.

When I try to switch to ON this is done fine but group address is 5 times sent to the KNX bus. When I try to turn off immediately this is not because the bus is still running. When I wait 10 seconds and then try to switch it OFF its ok.

Log file

2015-12-28 16:39:02.291 [WARN ] [.b.knx.internal.bus.KNXBinding:140  ] - Value 'ON' could not be sent to the KNX bus using datapoint 'command DP 1/1/0 Licht_sluis, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2015-12-28 16:39:05.297 [ERROR] [.b.knx.internal.bus.KNXBinding:148  ] - Value 'ON' could not be sent to the KNX bus using datapoint 'command DP 1/1/0 Licht_sluis, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2015-12-28 16:39:08.302 [WARN ] [.b.knx.internal.bus.KNXBinding:140  ] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 1/1/0 Licht_sluis, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2015-12-28 16:39:11.308 [ERROR] [.b.knx.internal.bus.KNXBinding:148  ] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 1/1/0 Licht_sluis, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2015-12-28 16:39:14.353 [WARN ] [.b.knx.internal.bus.KNXBinding:140  ] - Value 'ON' could not be sent to the KNX bus using datapoint 'command DP 1/1/0 Licht_sluis, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2015-12-28 16:39:17.360 [ERROR] [.b.knx.internal.bus.KNXBinding:148  ] - Value 'ON' could not be sent to the KNX bus using datapoint 'command DP 1/1/0 Licht_sluis, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2015-12-28 16:39:17.390 [DEBUG] [.b.knx.internal.bus.KNXBinding:113  ] - Received update (item='Licht_sluis', state='OFF')
2015-12-28 16:39:20.397 [WARN ] [.b.knx.internal.bus.KNXBinding:140  ] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 1/1/0 Licht_sluis, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2015-12-28 16:39:23.402 [ERROR] [.b.knx.internal.bus.KNXBinding:148  ] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 1/1/0 Licht_sluis, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2015-12-28 16:39:23.409 [DEBUG] [.b.knx.internal.bus.KNXBinding:113  ] - Received update (item='Licht_sluis', state='ON')
2015-12-28 16:39:26.415 [WARN ] [.b.knx.internal.bus.KNXBinding:140  ] - Value 'ON' could not be sent to the KNX bus using datapoint 'command DP 1/1/0 Licht_sluis, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2015-12-28 16:39:29.421 [ERROR] [.b.knx.internal.bus.KNXBinding:148  ] - Value 'ON' could not be sent to the KNX bus using datapoint 'command DP 1/1/0 Licht_sluis, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received

Items.

Switch Licht_sluis "Sluis " (gC) { knx="1.001:1/1/0+1/1/1" }

2

I can not imagine that this is just right?
I suppose oh should immediately respond to a command and not only after 10 seconds?

I do not know what I’m doing wrong.
The same is with the OH 1.8

If I send a command will oh handle it directly. In my ETS monitor I see four commands. When this command; s processed it acts only upon the next.

Are there more people with the same problem or am I the only one?

3

The same is here.
I´m trying to set up a new openhab environment on a virtual machine with latest stable version (I mean it is 1.7.1). The knx-binding item reaction is extremly slow and the messages - as @Ferryb4 wrote above - are written in the openhab.log file.

My productive openhab system (V. 1.5) is running well and respones as fast as it should!

Any suggestions?

Thanks!

4

Thank you David

I also tried my configuration with v1.5.1 and then the binding works perfectly without a hitch.

I hope someone has an explanation for this?

5

So what you all are saying is that despite this topic is in the openHAB 2 category, the problem exists in openHAB 1 as well and thus it is a problem of the binding since 1.7 and not with the openHAB 2 runtime, right? Shall I move the topic to another category then?

6

Ah, I just noticed only now the linked topic in the correct category: Problem KNX binding v1.8

7

Thank you Kai.

I also created a topic in OH1.:grinning:

These may be both closed.

I have now found the problem.

The problem was that I set a # Local Binding KNX bus address.
If I turn it off all problems are solved and OH reacts fast.

Thanks for your support and fantastic software.

8

Thanks for the positive feedback - I am glad to hear that we don’t have a blocking issue a few days before the 1.8 release!