This page last changed on Apr 24, 2014 by alexeyand.

Tried setup OR to control KNX installation. Having OSX 10.9 and K-BUS Gateway http://shop.knxstoreonline.com/gb/gateways-and-interfaces/3-bnip-00001-gateway-ipknx.html
First added gateway IP address to config.properties file - have no result
Then i installed eibd - works fine:

$ eibd -d -D -S -T -i ipt:192.168.1.15

$ groupsocketlisten ip:127.0.0.1
Write from 0.0.0 to 1/0/0: 00
Write from 1.1.13 to 1/0/2: 00
Write from 0.0.0 to 1/0/0: 01
Write from 1.1.13 to 1/0/2: 80
Write from 0.0.0 to 1/0/0: 00

But OR controller can't detect eibd correctly:
sh-3.2# tail -F knx-debug.log
DEBUG 2014-04-24 17:31:04,105 (KNX): Creating KNX bus with org.openremote.controller.protocol.port.DatagramSocketPort
INFO 2014-04-24 17:31:04,106 (KNX): Found a KNX IP interface at /0.0.0.0:3671
INFO 2014-04-24 17:31:04,106 (KNX): Connection created for KNX IP interface at /0.0.0.0:3671
DEBUG 2014-04-24 17:31:04,106 (KNX): Creating KNX bus with org.openremote.controller.protocol.port.DatagramSocketPort
INFO 2014-04-24 17:31:04,107 (KNX): Failed to get network interface for address '/25.81.44.131'. Skipping...
DEBUG 2014-04-24 17:31:04,107 (KNX): Creating KNX bus with org.openremote.controller.protocol.port.DatagramSocketPort
WARN 2014-04-24 17:31:04,108 (KNX): Could not connect
org.openremote.controller.protocol.knx.ConnectionException: Connect failed
at org.openremote.controller.protocol.knx.KNXIpConnectionManager$KNXConnectionImpl.connect(KNXIpConnectionManager.java:703)
at org.openremote.controller.protocol.knx.KNXIpConnectionManager.getConnection(KNXIpConnectionManager.java:223)
at org.openremote.controller.protocol.knx.KNXIpConnectionManager$ConnectionTask.run(KNXIpConnectionManager.java:989)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: java.io.IOException: No route to host
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.DatagramSocket.send(DatagramSocket.java:625)
at org.openremote.controller.protocol.port.DatagramSocketPort.send(DatagramSocketPort.java:64)
at org.openremote.controller.protocol.knx.ip.IpProcessor.send(IpProcessor.java:195)
at org.openremote.controller.protocol.knx.ip.IpProcessor.send(IpProcessor.java:188)
at org.openremote.controller.protocol.knx.ip.IpProcessor.service(IpProcessor.java:175)
at org.openremote.controller.protocol.knx.ip.IpTunnelClient.connect(IpTunnelClient.java:112)
at org.openremote.controller.protocol.knx.KNXIpConnectionManager$KNXConnectionImpl.connect(KNXIpConnectionManager.java:697)
... 4 more

Here is a routing table:

sh-3.2# netstat -r
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.55.1 UGSc 39 0 en2
default link#4 UCSI 1 0 en0
25 link#9 UC 2 0 ham0
25.255.255.255 ff:ff:ff:ff:ff:ff UHLWbI 0 7 ham0
127 localhost UCS 0 0 lo0
localhost localhost UH 6 163220 lo0
169.254 link#4 UCS 0 0 en0
192.168.1 link#4 UCS 5 0 en0
knx.local 10:0:0:0:0:1 UHLWIi 2 234 en0 715
192.168.1.23 localhost UHS 0 746 lo0
192.168.1.100 link#4 UHLWIi 2 385 en0
192.168.1.177 link#4 UHRLWIi 11 3272 en0
192.168.1.209 link#4 UHLWIi 1 6 en0
192.168.1.255 ff:ff:ff:ff:ff:ff UHLWbI 0 7 en0
192.168.55 link#6 UCS 2 0 en2
192.168.55.1 e0:46:9a:62:64:76 UHLWIir 40 550 en2 619
192.168.55.100 localhost UHS 1 176 lo0
192.168.55.255 ff:ff:ff:ff:ff:ff UHLWbI 0 7 en2
224.0.23.12 1:0:5e:0:17:c UHmLS 0 0 en0
224.0.23.12 1:0:5e:0:17:c UHmLWI 0 185 en0

long time trying to configure it, without result. whats wrong?

This is the actual error from the OS network layer to OpenRemote:

Caused by: No route to host

That it attempts to use address 0.0.0.0 also looks suspicious. There's something not right with the network configuration.

Posted by juha at Apr 25, 2014 00:38

will try on other Mac tonight. by the way, i think "0.0.0.0" mean all local ip addresses in this case
like no problem with "0.0.0.0":
sh-3.2# groupsocketlisten ip:0.0.0.0
Write from 1.1.2 to 2/0/0: 01
Write from 1.1.12 to 2/0/0: 01
Write from 1.1.2 to 2/0/0: 00
Write from 1.1.12 to 2/0/0: 00

Posted by alexeyand at Apr 25, 2014 13:37

keep trying
launch eibd:
$ eibd -D -S -T --listen-tcp=3671 -t65535 ipt:192.168.1.15

works fine with ETS program

next launch OR and push the button assigned to some knx command:

  1. tail -F knx-debug.log
    INFO 2014-04-26 02:30:07,815 (KNX): KNX IP interface hostname set to '192.168.1.90'
    INFO 2014-04-26 02:30:07,815 (KNX): KNX IP interface port set to '3671'
    INFO 2014-04-26 02:30:07,815 (KNX): KNX PhysicalBus clazz set to 'org.openremote.controller.protocol.port.DatagramSocketPort'
    INFO 2014-04-26 02:30:07,817 (KNX): Scheduled reconnection task
    WARN 2014-04-26 02:30:07,817 (KNX): Unknown KNX property '<property name = "name" value = "sw on"/>'.
    INFO 2014-04-26 02:30:07,819 (KNX): Trying to create connection
    INFO 2014-04-26 02:30:07,819 (KNX): Removing connection
    INFO 2014-04-26 02:30:07,822 (KNX): KNX Connection manager resolving local host IP addresses...
    INFO 2014-04-26 02:30:07,830 (KNX): Found candidate NIC: name:vnic1 (vnic1)
    INFO 2014-04-26 02:30:07,831 (KNX): Added candidate IP address to set - /10.37.129.2
    INFO 2014-04-26 02:30:07,831 (KNX): Found candidate NIC: name:vnic0 (vnic0)
    INFO 2014-04-26 02:30:07,831 (KNX): Added candidate IP address to set - /10.211.55.2
    INFO 2014-04-26 02:30:07,832 (KNX): Found candidate NIC: name:ham0 (ham0)
    INFO 2014-04-26 02:30:07,832 (KNX): Skipped IPv6 address (not supported by KNX) /2620:9b:0:0:0:0:19a3:30c2
    INFO 2014-04-26 02:30:07,832 (KNX): Skipped IPv6 address (not supported by KNX) /fe80:0:0:0:7879:19ff:fea3:30c2%7
    INFO 2014-04-26 02:30:07,832 (KNX): Added candidate IP address to set - /25.163.48.194
    INFO 2014-04-26 02:30:07,832 (KNX): Found candidate NIC: name:en1 (en1)
    INFO 2014-04-26 02:30:07,832 (KNX): Skipped IPv6 address (not supported by KNX) /fe80:0:0:0:daa2:5eff:fe97:2220%5
    INFO 2014-04-26 02:30:07,832 (KNX): Added candidate IP address to set - /192.168.1.90
    INFO 2014-04-26 02:30:07,832 (KNX): Skipping loopback interface: name:lo0 (lo0)
    DEBUG 2014-04-26 02:30:07,850 (KNX): Creating KNX bus with org.openremote.controller.protocol.port.DatagramSocketPort
    INFO 2014-04-26 02:30:07,860 (KNX): Failed to get network interface for address '/10.211.55.2'. Skipping...
    DEBUG 2014-04-26 02:30:07,860 (KNX): Creating KNX bus with org.openremote.controller.protocol.port.DatagramSocketPort
    INFO 2014-04-26 02:30:07,862 (KNX): Failed to get network interface for address '/10.37.129.2'. Skipping...
    DEBUG 2014-04-26 02:30:07,863 (KNX): Creating KNX bus with org.openremote.controller.protocol.port.DatagramSocketPort
    INFO 2014-04-26 02:30:07,876 (KNX): Found a KNX IP interface at /0.0.0.0:3671
    DEBUG 2014-04-26 02:30:07,876 (KNX): Creating KNX bus with org.openremote.controller.protocol.port.DatagramSocketPort
    INFO 2014-04-26 02:30:07,889 (KNX): Failed to get network interface for address '/25.163.48.194'. Skipping...
    INFO 2014-04-26 02:30:07,986 (KNX): Created KNX Command FRAME L_Data.req 0.0.0 -> 1/0/0 Data: 0x01 for group address '1/0/0'
    INFO 2014-04-26 02:30:07,990 (KNX): No KNX connection available, did not send FRAME L_Data.req 0.0.0 -> 1/0/0 Data: 0x01
    WARN 2014-04-26 02:30:17,890 (KNX): Could not connect
    org.openremote.controller.protocol.knx.ConnectionException: KNX-IP interface not found
    at org.openremote.controller.protocol.knx.KNXIpConnectionManager.waitForConnection(KNXIpConnectionManager.java:264)
    at org.openremote.controller.protocol.knx.KNXIpConnectionManager.getConnection(KNXIpConnectionManager.java:222)
    at org.openremote.controller.protocol.knx.KNXIpConnectionManager$ConnectionTask.run(KNXIpConnectionManager.java:989)
    at java.util.TimerThread.mainLoop(Timer.java:512)
    at java.util.TimerThread.run(Timer.java:462)
    INFO 2014-04-26 02:30:17,890 (KNX): Trying to create connection
    INFO 2014-04-26 02:30:17,890 (KNX): Removing connection
    INFO 2014-04-26 02:30:17,892 (KNX): KNX-IP socket listener IOException
    java.net.SocketException: Socket closed
    at java.net.PlainDatagramSocketImpl.receive0(Native Method)
    at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:188)
    at java.net.DatagramSocket.receive(DatagramSocket.java:725)
    at org.openremote.controller.protocol.port.DatagramSocketPort.receive(DatagramSocketPort.java:78)
    at org.openremote.controller.protocol.knx.ip.IpProcessor$PhysicalBusListener.run(IpProcessor.java:82)
    WARN 2014-04-26 02:30:17,892 (KNX): KNX-IP socket listener stopped
    INFO 2014-04-26 02:30:17,892 (KNX): KNX-IP socket listener IOException
    java.net.SocketException: Socket closed

at this time see eibd output:

Layer 8(D3500E10,535ADF64) SEARCH
Layer 1(D3500F40,535ADF64) Send(068): 08 01 00 00 00 00 0E 57 36 01 02 00 00 00 00 00 00 00 00 00 00 00 E0 00 17 0C 00 00 00 00 00 00 65 69 62 64 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 02 02 01 04 01
Layer 0(D3500F40,535ADF64) Send(074): 06 10 02 02 00 4A 08 01 00 00 00 00 0E 57 36 01 02 00 00 00 00 00 00 00 00 00 00 00 E0 00 17 0C 00 00 00 00 00 00 65 69 62 64 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 02 02 01 04 01

that is, the controller tries to access eibd, but apparently does not recognize his answer. This is incompatible with the ip interface or with eibd?

OR version 2.1.0_FM_ORCJAVA-400

I think something is wrong in OR: I checked aycontrol with eibd and it works... but im really fan of OR software (quite a long time use it with arduino and vera) and would like to get it work with my knx part

thanks in advance

Posted by alexeyand at Apr 25, 2014 23:54
Document generated by Confluence on Jun 05, 2016 09:37