Need help with openhab2, KNX & exor ebis panel

openhab2
knx
Tags: #<Tag:0x00007fe066218bf0> #<Tag:0x00007fe066218a88>

(zameer) #1

Hello Gurus,

This is just my first week with home automation/Openhab, need your inputs.
I have an ABB home automation setup with an Exor Ebis 507 panel to control the lights, etc.
Now, the automation panel (Exor ebis 507) has a PLCM02 plug-in module installed which connects to KNX using TP interface.
I was able to get the Alexa to OpenHab2 interface working, but having some trouble setting up the OpenHab2 to KNX interface.
I’ve connected the automation panel to my WiFi network, but I’m unable to connect OpenHab to KNX via TUNNEL option where it uses the automation panel as a Gateway to KNX.
It tries to connect via port 6720 & 3671, but both fail. The IP I mention in knx.cfg is of the automation panel as that is the only interface I have to connect to KNX.

Could you suggest how I could connect OpenHab to KNX in my setup?
I was able to connect OpenHab to KNX bus via a ROUTER option where it connects to KNX bus via the default IP:PORT 224.0.23.12:3671. But I don’t think the KNX commands actually reach the KNX bus as I don’t see any confirmation message in the logs.
OpenHab Log snippets:
"
2018-02-14 10:09:21.912 [INFO ] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: using network interface wlan1
2018-02-14 10:09:21.914 [INFO ] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: multicast loopback mode enabled
2018-02-14 10:09:21.920 [INFO ] [nx.internal.connection.KNXConnection] - Established connection to KNX bus on 224.0.23.12:3671 in mode ROUTER.
2018-02-14 10:10:08.948 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: Boolean (main type 1) loaded
2018-02-14 10:10:08.948 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: Boolean controlled (main type 2) loaded
2018-02-14 10:10:08.949 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 3 Bit controlled (main type 3) loaded
2018-02-14 10:10:08.949 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 8 Bit unsigned value (main type 5) loaded
2018-02-14 10:10:08.950 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 8 Bit signed value (main type 6) loaded
2018-02-14 10:10:08.950 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 2 octet unsigned value (main type 7) loaded
2018-02-14 10:10:08.952 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 2 octet float value (main type 9) loaded
2018-02-14 10:10:08.953 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: Time (main type 10) loaded
2018-02-14 10:10:08.954 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: Date (main type 11) loaded
2018-02-14 10:10:08.954 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 4 octet unsigned value (main type 12) loaded
2018-02-14 10:10:08.955 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 4 octet signed value (main type 13) loaded
2018-02-14 10:10:08.955 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 4 octet float value (main type 14) loaded
2018-02-14 10:10:08.956 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: String (main type 16) loaded
2018-02-14 10:10:08.957 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: Scene number (main type 17) loaded
2018-02-14 10:10:08.957 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: Scene control (main type 18) loaded
2018-02-14 10:10:08.957 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: Date with time (main type 19) loaded
2018-02-14 10:10:08.958 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: UTF-8 string (main type 28) loaded
2018-02-14 10:10:08.958 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 64 Bit signed value (main type 29) loaded
2018-02-14 10:10:08.959 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: RGB color value (main type 232) loaded
2018-02-14 10:10:08.960 [INFO ] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send message to 2/1/5, wait for confirmation
2018-02-14 10:10:08.960 [INFO ] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send message to 2/1/5, wait for confirmation
2018-02-14 10:10:08.960 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: cEMI L-Data.ind from 15.15.249 to 2/1/5, low priority hop count 6 tpdu 00 81
2018-02-14 10:10:08.961 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: cEMI L-Data.ind from 15.15.249 to 2/1/5, low priority hop count 6 tpdu 00 81
2018-02-14 10:10:08.961 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: add to multicast loopback frame buffer: L-Data.ind from 15.15.249 to 2/1/5, low priority hop count 6 tpdu 00 81
2018-02-14 10:10:08.961 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: add to multicast loopback frame buffer: L-Data.ind from 15.15.249 to 2/1/5, low priority hop count 6 tpdu 00 81
2018-02-14 10:10:08.971 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: sending cEMI frame seq 0, non-blocking, attempt 1 (channel 0) 06 10 05 30 00 11 29 00 bc e0 ff f9 11 05 01 00 81
2018-02-14 10:10:08.972 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send to 2/1/5 succeeded
2018-02-14 10:10:08.973 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: sending cEMI frame seq 0, non-blocking, attempt 1 (channel 0) 06 10 05 30 00 11 29 00 bc e0 ff f9 11 05 01 00 81
2018-02-14 10:10:08.975 [DEBUG] [tuwien.auto.calimero ] - process 224.0.23.12:3671: group write to 2/1/5 succeeded
2018-02-14 10:10:08.975 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: discard multicast loopback cEMI frame: L-Data.ind from 15.15.249 to 2/1/5, low priority hop count 6 tpdu 00 81
2018-02-14 10:10:08.976 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send to 2/1/5 succeeded
2018-02-14 10:10:08.976 [DEBUG] [tuwien.auto.calimero ] - process 224.0.23.12:3671: group write to 2/1/5 succeeded
2018-02-14 10:10:08.976 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: discard multicast loopback cEMI frame: L-Data.ind from 15.15.249 to 2/1/5, low priority hop count 6 tpdu 00 81
"
Here OpenHab is trying to send ’ 2/1/5’ to the KNX bus.

Another thing I’ve noticed is that the automation panel has a OPC-UA server that I’ve enabled.
Is there a way to get access to the KNX bus using the OPC-UA server ?

Appreciate your inputs.


(Rich Koshak) #2

I can’t help with the KNX but it will be easier for those who can if you How to use code fences


(Udo Hartmann) #3

You will need a knx interface with KNXnet/IP protocol.

As eBis507 does not provide KNXnet/IP to ethernet, there is no way to use this device as an interface.