[SOLVED] OpenHab2 KNX-usb Binding Issue

Hi all,

I’ve already managed to connect my raspberry Pi to my KNX-USB device via:

They are connected however I’m not able to see the KNX bindings popping up in my OPENHAB2 inbox.

I’ve already tried to setup the openhab2/conf/services/knx.cfg settings, however I’ve not managed to get it working. These are my knx.cfg settings:

# KNX gateway IP address  (optional, if serialPort or connection type 'ROUTER' is specified)
ip=192.168.1.10

# 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.128

# 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=ROUTER

# KNX gateway port (optional, defaults to 3671)
# Note: If you use eibd, setting to 6720
#port=

# Local endpoint to specify the multicast interface, no port is used (optional)
localIp=192.168.1.10

# 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

Does anyone have an idea of what is going wrong here?

Is my IP, bussaddress, localIP etc correct?
My static IP of my PI is: 192.168.1.10
The bus of my usb device is 1.1.128

Im really new to this so I hope I gave you guys enough information.

Thanx in advance!

Yarn

Hi,

The knx binding in the stable release, if that is what you are using, is a 1.x version binding, that means that nothing will pop up in your paper ui inbox, because in this version there are no things/channels to define.
The knx 1.x version binding uses items configured manually in the .items file you create.

Take a look here for the KNX binding configuration.
Version 2.x of the binding is still work in progress and has not yet been merged to the official repo (at least that is what I know so far).
BR,
George

2 Likes

Thx George!

I’ll try to configure it via .items.

grtz
Y

Hi all!

Well this Noob made some progress. I made a few Items and a nice sitemap. However, I’m not able to switch the lights (yet).

First of all, I am able to control my lights via knxtools.
If I type:

knxtool groupswrite ip:localhost 7/0/0 0

my livingroom light switches of! So KNX is correctly installed and works.

Now i’m trying to make knx work with openhab2. I made the following item:

Switch TestItem "Switch 1" <Switch> {knx="7/0/0"}

I already noticed that there are multiple ways to describe this knx device. For example adding listening an listening group address. However, I don’t know how to find these Listening Group Adresses. How can I find these LGA’s?

Second, it could be that my knx.cfg file is not correctly configured.

# KNX gateway IP address  (optional, if serialPort or connection type 'ROUTER' is specified)
ip=localhost

# 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.128

# 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=ROUTER

# KNX gateway port (optional, defaults to 3671)
# Note: If you use eibd, setting to 6720
#port=

# Local endpoint to specify the multicast interface, no port is used (optional)
#localIp=192.168.1.10

# 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

Is this file correctly configured?

So, long story short:

Q1: I don’t know how to find these Listening Group Adresses. How can I find these LGA’s?
Q2: Is my knx.cfg file correct

Thanks in advance,

Yarne

A1: The best way would be to ask your installer to provide you with a copy of the ETS Project File and load it up in ETS. Do you have the project file?
An alternative method would be to use bus monitor and sniff out all the LGAs… that’s a pain…

A2: Not accurate for Router mode. Use this:

ip=224.0.23.12
port=3671
type=ROUTER
localIp=192.168.1.10
busaddr=1.1.128
ignorelocalevents=true

It should work if knxd is running correctly and listening to EIBnet/IP Routing

Hi!
Thx Dim, I tried but it still doesn’t work.

Just to be sure:
I have an eibd USB device and knxd installed.

I used your configurations, but still no success. What am I possibly doing wrong?

Is there a log or anything to see why it doesn’t work? I tried to install calimero-tools but I couldn’t get it to work.

Gr
Yarne

Post your knxd command line parameters to check them.
You are not far away from success since you got knxtool working :slight_smile:

1 Like

Hi,

As @Dim said, the best way to approach your issue is to disclose the setup.
The hardware is not important right now as long as you have managed to connect using the calimero knxtools. I am pretty sure it’s only a matter of the knxd configuration in terms of port/ip!

BR,

George

Alright: I’ll ecaxtly show you my setup:

Made a static IP:

[Match]
Name=eth0
[Network]
#DHCP=v4
# static IP
# 192.168.1.10 netmask 255.255.255.0
Address=192.168.1.10/24
Gateway=192.168.1.1
DNS=192.168.1.1
# Route for Multicast Address EIB/KNX
[Route]
Destination=224.0.23.12/32

installed knxd via http://michlstechblog.info/blog/raspberry-pi-eibknx-ip-gateway-and-router-with-knxd/

pi@raspberrypi:~ $ findknxusb
Possible addresses for KNX USB devices:
device: 1:6:1:0:0 (Busch-Jaeger Elektro GmbH:KNX-USB Interface (Flush mounted))
pi@raspberrypi:~ $ ps ax|grep knxd
  609 ?        Ss     0:00 /usr/local/bin/knxd -p /run/knxd/knxd.pid --eibaddr=1.1.128 --client-addrs=1.1.129:1 -d -D -T -R -S -i --listen-local=/tmp/knx -b usb:1:6:1:0:0
 1324 pts/0    S+     0:00 grep --color=auto knxd

Next I installed Openhab2 and the KNX binding via Paper UI.
adress to open OPENHAB: 192.168.1.10:8080

I made a sitemap:

sitemap default label="My first sitemap"
{
    Switch item=TestItem label="Woonkamer"

}

And a file called home.items in the items folder. This switch is an dimer+switch combi. If I use groupssocketlisten and I turn the light on I get:

pi@raspberrypi:~ $ knxtool groupsocketlisten ip:localhost 
Write from 1.1.7 to 7/0/0: 01

If I turn the light on and press this switch longer I get:

pi@raspberrypi:~ $ knxtool groupsocketlisten ip:localhost 
Write from 1.1.7 to 7/0/0: 01
Write from 1.1.7 to 7/1/0: 09

So based on this made an item called TestItem:

Switch TestItem "Switch 1" <Switch> { knx="<7/0/0" }

I can turn my light on and of with groupswrite:

knxtool groupswrite ip:localhost 7/0/0 1

I configured my knx.cfg

# KNX gateway IP address  (optional, if serialPort or connection type 'ROUTER' is specified)
ip=224.0.23.12

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.128

# 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=ROUTER

# 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=192.168.1.10


Lastly:

# Command line parameters for knxd. TPUART Backend
# Serial device Raspberry
#KNXD_OPTIONS="--eibaddr=1.1.128 --client-addrs=1.1.129:1 -d -D -T -R -S -i --listen-local=/tmp/knx -b tpuarts:/dev/ttyAMA0"
# Serial device PC
# KNXD_OPTIONS="--eibaddr=1.1.128 --client-addrs=1.1.129:1 -d -D -T -R -S -i --listen-local=/tmp/knx -b tpuarts:/dev/ttyS0"
# Tunnel Backend
# KNXD_OPTIONS="--eibaddr=1.1.128 --client-addrs=1.1.129:1 -d -D -T -R -S -i --listen-local=/tmp/knx -b ipt:192.168.56.1"
# USB Backend
KNXD_OPTIONS="--eibaddr=1.1.128 --client-addrs=1.1.129:1 -d -D -T -R -S -i --listen-local=/tmp/knx -b usb:1:6:1:0:0"

I’m sorry for the long post. @Dim, @george.erhan: if you guys need extra information, can you please tell me which line of code I have to type in the terminal? I’m new to this so “logical stuff” is difficult to me :smiley:.

Like you guys said, I think I’m close. Thanks in advance.

1 Like

Hi,

I think I connected openHab2 to KNX:

08:35:35.627 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'home.items'
08:35:40.165 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'home.sitemap'
08:35:40.607 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'astro.things'
08:35:43.193 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at /start
08:35:43.640 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
08:35:43.706 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
08:35:43.776 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
08:35:44.495 [INFO ] [nx.internal.connection.KNXConnection] - Established connection to KNX bus on 224.0.23.12:3671 in mode ROUTER.

However, still my switch is not working…
could it be an error in my.items file?

Switch TestItem "Switch 1" {knx="1.001:7/0/0"}

grtz
Yarn

GOT IT!!!

ip=224.0.23.12
ignorelocalevents=true
type=TUNNEL ## THIS DID THE TRICK!!!
port=3671
localIp=192.168.1.10

Thanks guys! Never was so happy to see a light switching on!

1 Like

:fireworks: :fireworks: :fireworks:

By the way: this is a strange setup… Tunnel mode with ip=224.0.23.12 … I have never seen this before :slight_smile: (and it’s not really a correct config set :stuck_out_tongue:)

Can you post the output of the following command in your OH2 console (ssh openhab@localhost -p 8101 with password: habopen)

config:list "(service.pid=org.openhab.knx)"
Pid:            org.openhab.knx
BundleLocation: mvn:org.openhab.binding/org.openhab.binding.knx/1.9.0
Properties:
   busaddr = 1.1.128
   ignorelocalevents = true
   ip = 224.0.23.12
   localIp = 192.168.1.10
   port = 3671
   service.pid = org.openhab.knx
   type = TUNNEL

I don’t get it… the (multicast) ip=224.0.23.12 is usually used when you have a type=ROUTER mode…
For TUNNEL, you should normally set the unicast IP Address of the gateway (in your case, the localhost running the knxd)

Since it works… keep it like that :slight_smile: It seems that you are tunneling using the multicast… that’s new for me

You could try to set ip=127.0.0.1 to see if it will work (everything else, the same)

@george.erhan, @watou, @lewie, @kgoderis : Have you seen this before? :sunglasses:

When I use this configuration I cannot use groupsocketlisten or vbusmonitor in knx tools. Also ETS doesn’t recognize my device anymore.

Hi,
Reflow the thread “Clover4x4”

I have installed knxd on my Raspian in RP3.
When it starts.

>    pi@raspberrypi:~ $ findknxusb
    Possible addresses for KNX USB devices:
    device: 1:6:1:0:0 (ABB STOTZ-KONTAKT GmbH:KNX-USB Interface (MDRC))
    pi@raspberrypi:~ $ ps ax|grep knxd
     1241 pts/0    S+     0:00 grep --color=auto knxd
    pi@raspberrypi:~ $ sudo systemctl status networking.service
    ● networking.service - Raise network interfaces
       Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: e
       Active: active (exited) since Mon 2017-11-27 00:17:05 CET; 12h ago
         Docs: man:interfaces(5)
      Process: 295 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUC
      Process: 285 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "
     Main PID: 295 (code=exited, status=0/SUCCESS)
       CGroup: /system.slice/networking.service

    nov 27 00:17:02 raspberrypi systemd[1]: Starting Raise network interfaces...
    nov 27 00:17:02 raspberrypi sh[285]: ifquery: couldn't open interfaces file "/etc/ne
    nov 27 00:17:02 raspberrypi ifup[295]: ifup: couldn't open interfaces file "/etc/net
    nov 27 00:17:05 raspberrypi systemd[1]: Started Raise network interfaces.
    pi@raspberrypi:~ $ knxtool vbusmonitor1 ip:localhost
    Open failed: Connection refused

Not work, then restart “knxd.service”

pi@raspberrypi:~ $ sudo systemctl restart knxd.service

I work knxd well sending telegrams with “knxtool groupswrite ip:localhost 4/0/1 1”

> pi@raspberrypi:~ $ ps ax|grep knxd
 1319 ?        Ssl    0:00 /usr/local/bin/knxd -p /run/knxd/knxd.pid --eibaddr=1.1.128 --client-addrs=1.1.129:16 -d -D -T -R -S -i --listen-local=/tmp/knx -b usb:
 1341 pts/0    S+     0:00 grep --color=auto knxd
pi@raspberrypi:~ $ knxtool vbusmonitor1 ip:localhost
LPDU: BC 11 82 20 01 E1 00 81 91 :L_Data low from 1.1.130 to 4/0/1 hops: 06 T_DATA_XXX_REQ A_GroupValue_Write (small) 01

In OpenHAB2 The config is the same of user “Clover4x4”. Connect a BUS KNX OK but not work he telegrams sent from openhab2.
They are sent correctly but not received by the USB gateway.

> `
> 2017-11-27 12:37:05.488 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
> 2017-11-27 12:37:06.294 [INFO ] [nx.internal.connection.KNXConnection] - Established connection to KNX bus on 224.0.23.12:3671 in mod            e TUNNEL.
> 2017-11-27 12:37:16.477 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Stopped HABmin servlet
> 2017-11-27 12:37:16.566 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic UI
> 2017-11-27 12:37:19.166 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
> 2017-11-27 12:37:19.758 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
> 
> ==> /var/log/openhab2/events.log <==
> 2017-11-27 12:40:19.426 [ItemCommandEvent          ] - Item 'knx_Vent1' received command ON
> 2017-11-27 12:40:19.548 [ItemStateChangedEvent     ] - knx_Vent1 changed from NULL to ON
> 2017-11-27 12:40:21.170 [ItemCommandEvent          ] - Item 'knx_Vent1' received command OFF
> 2017-11-27 12:40:21.184 [ItemStateChangedEvent     ] - knx_Vent1 changed from ON to OFF
> 2017-11-27 12:40:21.847 [ItemCommandEvent          ] - Item 'knx_Vent2' received command ON
> 2017-11-27 12:40:21.875 [ItemStateChangedEvent     ] - knx_Vent2 changed from NULL to ON
> 2017-11-27 12:40:22.462 [ItemCommandEvent          ] - Item 'knx_Vent2' received command OFF
> 2017-11-27 12:40:22.477 [ItemStateChangedEvent     ] - knx_Vent2 changed from ON to OFF
> `

I think something must have in the routing.

I have tried all the options of the messages above and it does not work.

My IP data: /etc/systemd/network/eth0.network

[Match]
# You can also use wildcards. Maybe you want enable dhcp
# an all eth* NICs
Name=eth0
[Network]
#DHCP=v4
# static IP
# 192.168.1.250 netmask 255.255.255.0
Address=192.168.1.250/24
Gateway=192.168.1.10
DNS=80.58.61.254 8.8.8.8
# Route for Multicast Address EIB/KNX
[Route]
Destination=224.0.23.12/32

 >pi@raspberrypi:~ $ ifconfig
> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>         inet 192.168.1.250  netmask 255.255.255.0  broadcast 192.168.1.255
>         inet6 fe80::ba27:ebff:feb5:bfd7  prefixlen 64  scopeid 0x20<link>
>         ether b8:27:eb:b5:bf:d7  txqueuelen 1000  (Ethernet)
>         RX packets 18635  bytes 2159944 (2.0 MiB)
>         RX errors 0  dropped 2  overruns 0  frame 0
>         TX packets 1263  bytes 183220 (178.9 KiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
pi@raspberrypi:~ $ dmesg|grep eth
[    1.954250] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:b5:bf:d7
[    4.913742] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    4.914258] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    6.501103] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    6.504633] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
> pi@raspberrypi:~ $ route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> default         192.168.1.10    0.0.0.0         UG    0      0        0 eth0
> 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
> 224.0.23.12     0.0.0.0         255.255.255.255 UH    0      0        0 eth0

More configuration information:

> lsusb -v
> 
> Bus 001 Device 006: ID 147b:5120
> Device Descriptor:
>   bLength                18
>   bDescriptorType         1
>   bcdUSB               1.01
>   bDeviceClass            0 (Defined at Interface level)
>   bDeviceSubClass         0
>   bDeviceProtocol         0
>   bMaxPacketSize0         8
>   idVendor           0x147b
>   idProduct          0x5120
>   bcdDevice            1.03
>   iManufacturer           1 ABB STOTZ-KONTAKT GmbH
>   iProduct                2 KNX-USB Interface (MDRC)
>   iSerial                 0
>   bNumConfigurations      1
> 
> pi@raspberrypi:~ $ sudo systemctl status knxd.service
> ● knxd.service - KNX Daemon
>    Loaded: loaded (/lib/systemd/system/knxd.service; enabled; vendor preset: enabled
>    Active: active (running) since Mon 2017-11-27 12:35:07 CET; 13min ago
>  Main PID: 1432 (knxd)
>    CGroup: /system.slice/knxd.service
>            └─1432 /usr/local/bin/knxd -p /run/knxd/knxd.pid --eibaddr=1.1.128 --clie
> 
> nov 27 12:35:07 raspberrypi systemd[1]: Started KNX Daemon.
> pi@raspberrypi:~ $ journalctl -xu knxd.service
> -- Logs begin at Thu 2016-11-03 18:16:42 CET, end at Mon 2017-11-27 12:48:51 CET. --
> nov 27 00:17:05 raspberrypi systemd[1]: Started KNX Daemon.
> -- Subject: Unit knxd.service has finished start-up
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> --
> -- Unit knxd.service has finished starting up.
> --
> -- The start-up result is done.
> nov 27 00:17:05 raspberrypi systemd[1]: knxd.service: Main process exited, code=kill
> nov 27 00:17:05 raspberrypi systemd[1]: knxd.service: Unit entered failed state.
> nov 27 00:17:05 raspberrypi systemd[1]: knxd.service: Failed with result 'signal'.
> nov 27 12:26:11 raspberrypi systemd[1]: Started KNX Daemon.
> -- Subject: Unit knxd.service has finished start-up

knx.cfg y knxd

> openhab> config:list "(service.pid=org.openhab.knx)"
> ----------------------------------------------------------------
> Pid:            org.openhab.knx
> BundleLocation: file:/usr/share/openhab2/addons/org.openhab.binding.knx-1.9.0-201611251544.jar
> Properties:
>    busaddr = 1.1.128
>    ignorelocalevents = true
>    ip = 224.0.23.12
>    localIp = 192.168.1.250
>    port = 3671
>    service.pid = org.openhab.knx
>    timeout = 100000
>    type = TUNNEL

KNXD_OPTIONS="–eibaddr=1.1.128 --client-addrs=1.1.129:16 -d -D -T -R -S -i --listen-local=/tmp/knx -b usb:"

Thank you very much in advance and I feel the text so long.
What is the problem?
I think something must have in the routing.

these 2 config parameters don’t go together
If you want to using routing (multicast IP 224.0.23.12), you need to specify type = ROUTER in your /etc/openhab2/services/knx.cfg file

If you want to use TUNNEL, you need to specify the unicast IP Address of your gateway (the host running knxd… it could be the localhost of course).

so: switch to type = ROUTER and try again :slight_smile:

Ps: It’s better to start a new thread. This one is already marked as Solved and may not get too much attention.

1 Like

Thanks Dim,
Not work with ROUTER.

Close thread. I start New thread.