OH2.3 using KNX2 - delay between switching devices

Add-ons Bindings
1

I managed to install openhab 2 with knx 2 binding as described in the topic:

So I am running the 2.3 beta release.

When I Test in the PaperUI at controls the two switches following happens:

  1. The first switching happens at once
  2. The next switching of any device needs about 6 seconds
  3. I I wait 6 seconds or more the next switching happens at once

There is no difference when I use the “<” reading tag. (e.g. “0/0/40+0/0/41” or “0/0/40+<0/0/41”.

Does anybody know what I am doing wrong?

Thany you?

grafik

{
  "knx:ip:778def75": {
    "class": "org.eclipse.smarthome.core.thing.internal.BridgeImpl",
    "value": {
      "label": "KNX/IP Gateway",
      "channels": [],
      "configuration": {
        "properties": {
          "useNAT": false,
          "readRetriesLimit": 3,
          "ipAddress": "192.168.88.60",
          "localIp": "192.168.88.63",
          "autoReconnectPeriod": 60,
          "type": "TUNNEL",
          "localSourceAddr": "1.1.54",
          "readingPause": 50,
          "portNumber": 3671,
          "responseTimeout": 10
        }
      },
      "properties": {},
      "uid": {
        "segments": [
          "knx",
          "ip",
          "778def75"
        ]
      },
      "thingTypeUID": {
        "segments": [
          "knx",
          "ip"
        ]
      },
      "location": "N152"
    }
  },
  "knx:device:b790b931": {
    "class": "org.eclipse.smarthome.core.thing.internal.ThingImpl",
    "value": {
      "label": "Licht",
      "bridgeUID": {
        "segments": [
          "knx",
          "ip",
          "778def75"
        ]
      },
      "channels": [
        {
          "acceptedItemType": "Switch",
          "kind": "STATE",
          "uid": {
            "segments": [
              "knx",
              "device",
              "b790b931",
              "K1"
            ]
          },
          "channelTypeUID": {
            "segments": [
              "knx",
              "switch"
            ]
          },
          "label": "Küche alle",
          "configuration": {
            "properties": {
              "ga": "0/0/40+0/0/41"
            }
          },
          "properties": {},
          "defaultTags": []
        },
        {
          "acceptedItemType": "Switch",
          "kind": "STATE",
          "uid": {
            "segments": [
              "knx",
              "device",
              "b790b931",
              "B1"
            ]
          },
          "channelTypeUID": {
            "segments": [
              "knx",
              "switch"
            ]
          },
          "label": "Büro alle",
          "configuration": {
            "properties": {
              "ga": "0/0/25+0/0/26"
            }
          },
          "properties": {},
          "defaultTags": []
        }
      ],
      "configuration": {
        "properties": {
          "pingInterval": 600,
          "readInterval": 0,
          "fetch": false
        }
      },
      "properties": {},
      "uid": {
        "segments": [
          "knx",
          "device",
          "b790b931"
        ]
      },
      "thingTypeUID": {
        "segments": [
          "knx",
          "device"
        ]
      },
      "location": "Siemens N152"
    }
  }
}
2

Hello,

I still have the problem that between the KNX commands send from openhab is a delay time of arround 6 seconds.

Does anybody has an idea what is wrong?

3

Hey,
did you see something in the logs?
Enable KNX Debug log via openhab console and run this:

log:set TRACE org.openhab.binding.knx
log:set TRACE calimero

after that see openhab.log for whats going on.

4

Did you solve the issue?
I am facing a similar problem when using habpanel (also on OH2.3 with knx2 binding). For instance, I have a rollershuter widget which has ng-click = sendCmd… In the log using the above statements I can see that the command is pushed onto the BUS after about 6s. At the same time, when using the basic interface, the command is send (most of the time) faily quickly in about one second. The same behaviour shows up randomly with a simple light toggle button in habpanel. The behaviour is however not even reproducilbe, sometimes command work very fast, other time very slow…
I do not believe it has to do with hardware, since I am running openhab and the interface for testing on a fast computer (i7-4790K, 4GHz, 32GB), besides openhab1 with knx1 runs nicely on a raspberry pi and connects to the knx bus very fast, so does the ETS software, meaning I also do not believe that there is something wrong with the knx setup (since the log entry show up about 6s after the click, the action is then executed pretty much right away when it shows up in the log).
If anybody has some ideas, I would appreciate to hear them. Thanks!

5

Hallo,
ich habe nachdem der Fehler aufgetreten ist die Suche eingestellt, zudem es sich um eine nicht offizielle Version gehandelt hat… Seit ein paar Wochen ist OpenHab in der aktuellen Version (2.3) installiert. So richtig getestet ob es funktioniert habe ich noch nicht, momentan experimentiere ich mit HabPanel und anderen Plugins.

6

Well, now it looks like it has nothing to do with habpanel. The delay shows up also in basicui and paperui.

7

Hallo,
jetzt habe ich es ausprobiert und es funktioniert. Der Unterschied sind folgende Einstellungen:
localIp="",
localSourceAddr=“0.0.0”

8

Ah, jetzt klappt es (auch mit einer anderen localSourceAddr). Vielen Dank!

9

Hi,

I’m facing the same problems:

  1. I have 3 roller shutter located one next to the other and I connected all of them using virtual switch - when I open them I just send 3 commands one after the other. There is delay between the opening of the roller shutter.

  2. I connected the system to Goole Home and defined a room that contains 4 lights: I’m telling the Google Home to turn on the room-> then it says “turning on 4 things” and there is the delay between turning on the lights. I tried to do the same with virtual switch and it behaves the same

I tried to change the LocalIp as it is in your solution and nothing worked after that :frowning_face:

Any help will be appreciated

Here is my knx configuration file:

KNX gateway IP address

(optional, if serialPort or connection type ‘ROUTER’ is specified) mac address 00246d009c6c

ip=10.0.0.24

Local KNX Binding bus address.

Use it, when two or more openHAB Instances are connected to the same KNX bus.

(optional, defaults to 0.0.0)

busaddr=1.1.255

Ignore local KNX Events, prevents internal events coming from

‘openHAB event bus’ a second time to be sent back to the ‘openHAB event bus’.

Note: To send back events second time is a Bug, but for backward compatibility, the behavior is not changed.

For new installations, its recommend to set “ignorelocalevents=true”

(optional, defaults to false)

ignorelocalevents=true

KNX IP connection type. Could be either TUNNEL or ROUTER (optional, defaults to TUNNEL)

Note: If you cannot get the ROUTER mode working (even if it claims it is connected),

use TUNNEL mode instead with setting both the ip of the KNX gateway and the localIp.

type=TUNNEL

KNX gateway port (optional, defaults to 3671)

Note: If you use eibd, setting to 6720

port=3671

Local endpoint to specify the multicast interface, no port is used (optional)

localIp=10.0.0.30

Serial port of FT1.2 KNX interface (ignored, if ip is specified)

Valid values are e.g. COM1 for Windows and /dev/ttyS0 or /dev/ttyUSB0 for Linux

#serialPort=

Pause in milliseconds between two read requests on the KNX bus during

initialization (optional, defaults to 50)

#pause=

Timeout in milliseconds to wait for a response from the KNX bus (optional,

defaults to 10000)

#timeout

Number of read retries while initialization items from the KNX bus (optional,

defaults to 3)

#readRetries

Seconds between connect retries when KNX link has been lost

0 means never retry, it will only reconnect on next write or read request

Note: without periodic retries all events will be lost up to the next read/write

request

(optional, default is 0)

#autoReconnectPeriod=30

Auto refresh feature

Number of entries permissible in the item refresher queue.

(optional, defaults to 10000)

#maxRefreshQueueEntries=

Number of parallel threads for refreshing items. (optional, defaults to 5)

#numberOfThreads=

Seconds to wait for an orderly shutdown of the auto refresher’s

ScheduledExecutorService. (optional, defaults to 5)

#scheduledExecutorServiceShutdownTimeoutString=

Use NAT (Network Address Translation)

(optional; defaults to false)

#useNAT=true