KNX - cant turn switch on or off

Setup, Configuration and Use Beginners
, ,
8

Hi,

If you managed to use the router connection type, then that’s the way you should go, tunelling is a little more resourceful, you will have denial of connection if too many clients are connected (depending on the gateway)!
Of course, the ets configuration should be a must in terms of routing!

Best regards,

George Erhan

9

Hi Dries,

yes i do have the ETS KNX software. i’m going to try it.

One more question. Is my items file and sitemap file correct? or did i make a mistake there?

thanks for all the reply’s

10

They are correct.
It seems to me that if we fix the IP to KNX Bus connection, everything will work

Remember to fix your /etc/openhab2/services/knx.cfg file as @george.erhan said.
Leaving busaddr= unset might? be the root cause of your problem.
Either comment it out using # or set it to something free in your KNX address space.

Post also please the output of the following console command:

config:list "(service.pid=org.openhab.knx)"
1 Like
11

Hi,

So i assigned the individual addres of the gira.
Also when i make a change to knx.cfg do i need to restart the pi? restart something?

Here is the log after setting commenting out the busaddres.

2017-05-30 20:21:13.700 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2017-05-30 20:21:14.220 [INFO ] [nx.internal.connection.KNXConnection] - Established connection to KNX bus on 224.0.23.12:3671 in mode ROUTER.
2017-05-30 20:21:24.814 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item ‘licht_test’ from KNX bus: timeout waiting for group read response: timeout
2017-05-30 20:21:24.816 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address ‘0/0/18’ = '2’
2017-05-30 20:21:34.870 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item ‘licht_test’ from KNX bus: timeout waiting for group read response: timeout
2017-05-30 20:21:34.871 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address ‘0/0/18’ = '1’
2017-05-30 20:21:44.925 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item ‘licht_test’ from KNX bus: timeout waiting for group read response: timeout
2017-05-30 20:21:44.927 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address ‘0/0/18’ = '0’
2017-05-30 20:21:54.980 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item ‘licht_test’ from KNX bus: timeout waiting for group read response: timeout
2017-05-30 20:21:54.982 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Give up, could not read address ‘0/0/18’ after ‘3’ retries.
2017-05-30 20:23:19.243 [WARN ] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: received unknown frame, service type 0x20b - ignored
2017-05-30 20:23:19.244 [WARN ] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: received unknown frame, service type 0x20b - ignored
2017-05-30 20:23:22.582 [WARN ] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: received unknown frame, service type 0x20b - ignored
2017-05-30 20:23:22.583 [WARN ] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: received unknown frame, service type 0x20b - ignored
2017-05-30 20:23:26.604 [WARN ] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: received unknown frame, service type 0x20b - ignored
2017-05-30 20:23:26.607 [WARN ] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: received unknown frame, service type 0x20b - ignored
2017-05-30 20:23:30.848 [WARN ] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: received unknown frame, service type 0x20b - ignored
2017-05-30 20:23:30.851 [WARN ] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: received unknown frame, service type 0x20b - ignored
2017-05-30 20:24:44.681 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'switch.items’
2017-05-30 20:30:58.170 [INFO ] [nx.internal.connection.KNXConnection] - Closing KNX connection
2017-05-30 20:30:58.248 [INFO ] [panel.internal.HABPanelDashboardTile] - Stopped HABPanel
2017-05-30 20:30:58.304 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Stopped HABmin servlet
2017-05-30 20:30:58.362 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Stopped Paper UI
2017-05-30 20:30:58.391 [INFO ] [assic.internal.servlet.WebAppServlet] - Stopped Classic UI
2017-05-30 20:30:58.513 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic UI
2017-05-30 20:30:58.641 [INFO ] [.dashboard.internal.DashboardService] - Stopped dashboard
2017-05-30 20:31:31.798 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'switch.items’
2017-05-30 20:31:34.895 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'demo.rules’
2017-05-30 20:31:36.647 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'demo.sitemap’
2017-05-30 20:31:36.801 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'demotest.sitemap’
2017-05-30 20:31:38.673 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at /start
2017-05-30 20:31:40.631 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
2017-05-30 20:31:40.844 [INFO ] [assic.internal.servlet.WebAppServlet] - Started Classic UI at /classicui/app
2017-05-30 20:31:41.266 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2017-05-30 20:31:41.559 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
2017-05-30 20:31:41.663 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2017-05-30 20:31:42.125 [INFO ] [nx.internal.connection.KNXConnection] - Established connection to KNX bus on 224.0.23.12:3671 in mode ROUTER.
2017-05-30 20:32:17.177 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: Boolean (main type 1) loaded
2017-05-30 20:32:17.179 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: Boolean controlled (main type 2) loaded
2017-05-30 20:32:17.179 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 3 Bit controlled (main type 3) loaded
2017-05-30 20:32:17.180 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 8 Bit unsigned value (main type 5) loaded
2017-05-30 20:32:17.181 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 8 Bit signed value (main type 6) loaded
2017-05-30 20:32:17.181 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 2 octet unsigned value (main type 7) loaded
2017-05-30 20:32:17.182 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 2 octet float value (main type 9) loaded
2017-05-30 20:32:17.183 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: Time (main type 10) loaded
2017-05-30 20:32:17.183 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: Date (main type 11) loaded
2017-05-30 20:32:17.184 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 4 octet unsigned value (main type 12) loaded
2017-05-30 20:32:17.185 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 4 octet signed value (main type 13) loaded
2017-05-30 20:32:17.186 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 4 octet float value (main type 14) loaded
2017-05-30 20:32:17.186 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: String (main type 16) loaded
2017-05-30 20:32:17.187 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: Scene number (main type 17) loaded
2017-05-30 20:32:17.188 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: Scene control (main type 18) loaded
2017-05-30 20:32:17.195 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: Date with time (main type 19) loaded
2017-05-30 20:32:17.195 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: UTF-8 string (main type 28) loaded
2017-05-30 20:32:17.196 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: 64 Bit signed value (main type 29) loaded
2017-05-30 20:32:17.197 [DEBUG] [tuwien.auto.calimero ] - DPTXlator: RGB color value (main type 232) loaded
2017-05-30 20:32:17.198 [INFO ] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send message to 0/0/4, wait for confirmation
2017-05-30 20:32:17.199 [INFO ] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send message to 0/0/4, wait for confirmation
2017-05-30 20:32:17.200 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: cEMI L-Data.ind from 5.3.4 to 0/0/4, low priority hop count 6 tpdu 00 80
2017-05-30 20:32:17.200 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: add to multicast loopback frame buffer: L-Data.ind from 5.3.4 to 0/0/4, low priority hop count 6 tpdu 00 80
2017-05-30 20:32:17.206 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: cEMI L-Data.ind from 5.3.4 to 0/0/4, low priority hop count 6 tpdu 00 80
2017-05-30 20:32:17.207 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: add to multicast loopback frame buffer: L-Data.ind from 5.3.4 to 0/0/4, low priority hop count 6 tpdu 00 80
2017-05-30 20:32:17.208 [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 53 04 00 04 01 00 80
2017-05-30 20:32:17.208 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Wrote value ‘OFF’ to datapoint 'command DP 0/0/4 licht_test, DPT main 0 id 1.001, low priority’
2017-05-30 20:32:17.209 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send to 0/0/4 succeeded
2017-05-30 20:32:17.213 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Wrote value ‘OFF’ to datapoint 'command DP 0/0/4 licht_test, DPT main 0 id 1.001, low priority’
2017-05-30 20:32:17.213 [DEBUG] [tuwien.auto.calimero ] - process 224.0.23.12:3671: group write to 0/0/4 succeeded
2017-05-30 20:32:17.214 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: discard multicast loopback cEMI frame: L-Data.ind from 5.3.4 to 0/0/4, low priority hop count 6 tpdu 00 80
2017-05-30 20:32:17.215 [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 53 04 00 04 01 00 80
2017-05-30 20:32:17.216 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: discard multicast loopback cEMI frame: L-Data.ind from 5.3.4 to 0/0/4, low priority hop count 6 tpdu 00 80
2017-05-30 20:32:17.217 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send to 0/0/4 succeeded
2017-05-30 20:32:17.218 [DEBUG] [tuwien.auto.calimero ] - process 224.0.23.12:3671: group write to 0/0/4 succeeded
2017-05-30 20:32:17.495 [INFO ] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send message to 0/0/4, wait for confirmation
2017-05-30 20:32:17.495 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Wrote value ‘ON’ to datapoint 'command DP 0/0/4 licht_test, DPT main 0 id 1.001, low priority’
2017-05-30 20:32:17.496 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: cEMI L-Data.ind from 5.3.4 to 0/0/4, low priority hop count 6 tpdu 00 81
2017-05-30 20:32:17.496 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: add to multicast loopback frame buffer: L-Data.ind from 5.3.4 to 0/0/4, low priority hop count 6 tpdu 00 81
2017-05-30 20:32:17.497 [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 53 04 00 04 01 00 81
2017-05-30 20:32:17.497 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Wrote value ‘ON’ to datapoint 'command DP 0/0/4 licht_test, DPT main 0 id 1.001, low priority’
2017-05-30 20:32:17.498 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send to 0/0/4 succeeded

Do you see something that can help.

Thanks for the help

12

In /etc/openhab2/services/knx.cfg you should set an unused bus address that will be used by the Binding.
Don’t use the actual bus address of the GIRA gateway since this may cause a conflict.

So, in case of type=ROUTER, you should have:

ip=224.0.23.12
busaddr=2.2.2
ignorelocalevents=true
type=ROUTER
port=3671
localIp=192.168.0.112

No need to restart something. OH2 will re-read the knx.cfg file and apply the changes immediately.
There is an issue with the config options and you should do the following to be on the safe side:

  1. Stop OH2 service (systemctl stop openhab2)
  2. Remove file /var/lib/openhab2/config/org/openhab/knx.config
  3. Fix your /etc/openhab2/services/knx.cfg and start OH2 service
2017-05-30 20:21:54.980 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'licht_test' from KNX bus: timeout waiting for group read response: timeout
2017-05-30 20:21:54.982 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Give up, could not read address '0/0/18' after '3' retries.

The KNX Binding is sending the message but it is failing to get a reply from the GIRA X1 Gateway…

How is the X1 configured? Is it set as a Line Repeater (PA type of x.y.z) or as a Line Coupler (PA type of x.y.0) ?
If I am not wrong, your GIRA X1 bus address is currently 5.3.4 and this should be changed to another one of Line Coupler type (x.y.0)

This is another problem and we will solve it but I don’t think that it is a blocking issue.

So: Try to change the knx.cfg (delete knx.config first) and check the logs again to see if the situation improves.

13

(sidenote… don’t spend too much time on this :slight_smile:) Actually… I don’t like this at all…

The official KNX Specification (v2.1) defines KNXnet/IP Service Type Identifiers for KNXnet/IP protocol version 1.0 (Core) in the range of 0200 to 020F hex.
So this identifier (0x20b) belongs to the KNXnet/IP Core action.
But… the KNX Standard (volume 3 (System Specifications), part 8 (KNXnet/IP), chapter 1) has only 10 Service names used until now (up to 0x20a)… 020B until 020F are unused.

KNX_IP_Core.jpg719×666 397 KB

So… it seems to me that GIRA has implemented another Service Type Identifier (outside the KNX standard) for their X1 product (0x20b)…

They have done it before also with Service Type Identifier 0x538 to me… :slight_smile:

Boris is treating this here: https://github.com/calimero-project/calimero-core/blob/master/src/tuwien/auto/calimero/knxnetip/KNXnetIPRouting.java

	// newer Gira servers have a "reliable communication" option, which uses the
	// following unsupported service type; not part of the knx spec
	private static final int GiraUnsupportedSvcType = 0x538;

Simple version: The calimero library which is used by the KNX Binding has all the KNX Standard service types implemented. The GIRA X1 is broadcasting some UDP datagrams with an unknown (by calimero) service type identifier. In theory, this warning can be ignored since it shouldn’t block the regular (standard) communications.

You could try to disable “Reliable Communications” in your GIRA X1 using ETS to see if this message disappears.
From my experience, they use these “extended” service types to establish communications between their Gateways and their other solutions (software, etc)

…The good news from all of this is: openHAB2 is receiving multicast messages from the GIRA X1 gateway on your network. If we fix the configs, it will work :slight_smile:

14

Hi Dim,

with an unused basaddres, you mean just a number that i dont use?
what does the knx.config do ??

how do i know if it is an Line Repeater or Line Coupler? Can i look it in ets5 or does it involve the wiring?

What i will do is delete the lknx.config
check if it is inproved.

I will check the config.

One more question.
So i should slide the slider to on and the lightbulb/ maxinbox switch (0/0/4) should change to on?

thanks

15

Yes. Some new address that does not exist currently in your KNX topology. This bus address will be used by the KNX Binding.

The knx.config is generated and stored automatically by internal openHAB2 processes after reading your knx.cfg.

Yes. When the communications problem will be fixed, you will be able to flick the switch in your sitemap and then the light will react (to ON or OFF)

16

i did stop the openhab2 service deletet the knx.config and restarted openhab2.
I did change the busaddr to 2.2.2
this is the log file.
2017-05-31 19:15:00.844 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Wrote value ‘OFF’ to datapoint 'command DP 0/0/4 licht_test, DPT main 0 id 1.001, low priority’
2017-05-31 19:15:00.844 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: cEMI L-Data.ind from 2.2.2 to 0/0/4, low priority hop count 6 tpdu 00 80
2017-05-31 19:15:00.849 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: add to multicast loopback frame buffer: L-Data.ind from 2.2.2 to 0/0/4, low priority hop count 6 tpdu 00 80
2017-05-31 19:15:00.851 [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 22 02 00 04 01 00 80
2017-05-31 19:15:00.852 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send to 0/0/4 succeeded
2017-05-31 19:15:00.853 [DEBUG] [tuwien.auto.calimero ] - process 224.0.23.12:3671: group write to 0/0/4 succeeded
2017-05-31 19:15:00.855 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: discard multicast loopback cEMI frame: L-Data.ind from 2.2.2 to 0/0/4, low priority hop count 6 tpdu 00 80
2017-05-31 19:15:00.857 [INFO ] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send message to 0/0/4, wait for confirmation
2017-05-31 19:15:00.857 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Wrote value ‘OFF’ to datapoint 'command DP 0/0/4 licht_test, DPT main 0 id 1.001, low priority’
2017-05-31 19:15:00.858 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: cEMI L-Data.ind from 2.2.2 to 0/0/4, low priority hop count 6 tpdu 00 80
2017-05-31 19:15:00.860 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: add to multicast loopback frame buffer: L-Data.ind from 2.2.2 to 0/0/4, low priority hop count 6 tpdu 00 80
2017-05-31 19:15:00.863 [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 22 02 00 04 01 00 80
2017-05-31 19:15:00.865 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send to 0/0/4 succeeded
2017-05-31 19:15:00.867 [DEBUG] [tuwien.auto.calimero ] - process 224.0.23.12:3671: group write to 0/0/4 succeeded
2017-05-31 19:15:00.869 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: discard multicast loopback cEMI frame: L-Data.ind from 2.2.2 to 0/0/4, low priority hop count 6 tpdu 00 80
2017-05-31 19:15:01.598 [INFO ] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send message to 0/0/4, wait for confirmation
2017-05-31 19:15:01.599 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Wrote value ‘ON’ to datapoint 'command DP 0/0/4 licht_test, DPT main 0 id 1.001, low priority’
2017-05-31 19:15:01.599 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: cEMI L-Data.ind from 2.2.2 to 0/0/4, low priority hop count 6 tpdu 00 81
2017-05-31 19:15:01.603 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: add to multicast loopback frame buffer: L-Data.ind from 2.2.2 to 0/0/4, low priority hop count 6 tpdu 00 81
2017-05-31 19:15:01.604 [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 22 02 00 04 01 00 81
2017-05-31 19:15:01.605 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send to 0/0/4 succeeded
2017-05-31 19:15:01.606 [DEBUG] [tuwien.auto.calimero ] - process 224.0.23.12:3671: group write to 0/0/4 succeeded
2017-05-31 19:15:01.607 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: discard multicast loopback cEMI frame: L-Data.ind from 2.2.2 to 0/0/4, low priority hop count 6 tpdu 00 81
2017-05-31 19:15:01.614 [INFO ] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send message to 0/0/4, wait for confirmation
2017-05-31 19:15:01.615 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Wrote value ‘ON’ to datapoint 'command DP 0/0/4 licht_test, DPT main 0 id 1.001, low priority’
2017-05-31 19:15:01.618 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: cEMI L-Data.ind from 2.2.2 to 0/0/4, low priority hop count 6 tpdu 00 81
2017-05-31 19:15:01.621 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: add to multicast loopback frame buffer: L-Data.ind from 2.2.2 to 0/0/4, low priority hop count 6 tpdu 00 81
2017-05-31 19:15:01.624 [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 22 02 00 04 01 00 81
2017-05-31 19:15:01.626 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send to 0/0/4 succeeded
2017-05-31 19:15:01.629 [DEBUG] [tuwien.auto.calimero ] - process 224.0.23.12:3671: group write to 0/0/4 succeeded
2017-05-31 19:15:01.632 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: discard multicast loopback cEMI frame: L-Data.ind from 2.2.2 to 0/0/4, low priority hop count 6 tpdu 00 81

17

logs look clean
does it work? :slight_smile:

18

Hi Dim,

No it’s still not working :confused:
What can be wrong??

19

2 things:
a) The X1 device should be configured as a Line Coupler (x.y.0 address)
b) You need a dummy application configured in ETS in order to allow the routing of telegrams via the filter table

If you need help with (a) and/or (b) let me know

20

Hi Dim,

Sorry but i need help with a and b.
I dont know anything about line coupler

What is it ?

21

Check this out:

There is a lot of info in that thread related to this topic.

22

Hi Dim,

Pysical adress is the same as individual adress?
if yes i changed it too 1.0.4. I couldn’t set it to 1.0.0.

I’m still reading the other thread about a dummy application

23

Yes. PA = IA (they are used as synonyms in KNX literature)

To change it to x.y.0 you will need to change your Backbone Line medium from TP to IP.
There is some info about this in the thread above.

24

HI,
thanks for all the help.

So i changed some settings and got it working. Then something happend and i wasn’t able to open the webinterface of openhab.

So after 2days of figuring it out, i decided to start over.

So after setting evrything back up.
I was able to turn the light on and off.

My configuration.

-----------------------services\knx.cfg----------------------------------

KNX gateway IP address

(optional, if serialPort or connection type ‘ROUTER’ is specified)

ip=192.168.0.112

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=

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=192.168.0.132

-------------------items\encora.items----------------------------------
Switch lamp_vier “lamp 4” {knx=“0/0/4+0/0/14”}

Switch Dimmer_LEEN “dimmer lamp” {knx=“0/0/1”}

Dimmer Dimmer_een “Dimmer [%s]” {knx=“0/0/1, 0/1/0, 0/0/11”}

-----------------------sitemap\encora.sitemap---------------------
sitemap encora label=“lampVier”
{
Frame
{
Switch item=lamp_vier icon=“light” mappings=[OFF=“uit”, ON=“aan”]
Switch item=Dimmer_LEEN icon=“light” mappings=[OFF=“uit”, ON=“aan”]
}
Frame
{
Switch item=Dimmer_een label"lamp2 [%d %%]" mappings[INCREASE=“hoger”, DECREASE=“lager”]
Slider item=Dimmer_een label=“lamp [%d %%]”
}

The issues i have.
Issue 1: When i togle the switch it is sometimes slow.
Toggle on takes sometimes up to 5sec to turn on or off.
Also when the light is on and i refresh the page it doesnt show the correct state.
Issue 2: The dimmer works so on/off works and decrease and increase works.
But i can’t enter an 8 bit value trough the slider.
Am i doing something wrong?

I want to thank everyone for helping me.

Greetings

25

Hi,

The dimmer does work now. But it is slow in response.

greetings,

26

It sounds to me that something is not optimized in your KNX installation side…
Since OH2 can connect with mode=TUNNEL and can control the endpoints, you may be experiencing delays due to some kind of KNX Bus issues. I can’t pin point the issue but it’s worth to try to analyze the telegram traffic using Bus Monitor with ETS.

27

Hello,
Thank you for the support,

please can you help with configuration?

I have a Gira 2167, configured in ETS with the address 1.1.0
these are the info:

Device Info of Device 1.1.0

General

Item Value Resource name Unformatted value
Mask Version 091A 2330
Serial Number 0008:128104A5 DeviceSerialNumber 0008128104A5
Programming Mode Off ProgrammingMode false
Max. APDU Length 220 MaxApduLength 220

IP

Item Value Resource name Unformatted value
Name KNX/IP router KNX/IP router
MAC Address 00-0A-B3-27-5C-07 000AB3275C07
IP Address 192.168.1.103 C0A80167
Subnet Mask 255.255.255.0 FFFFFF00
Default Gateway 192.168.1.1 C0A80101
Additional Addresses 1.1.15 1.1.16 1.1.17 1.1.18 4367 4368 4369 4370
Routing Multicast Address 224.0.23.12 E000170C

Line Coupler

Item Value Resource name Unformatted value
Main > Sub Configuration Indiv. adressed: transmit always

Indiv. adressed repeat on error: repeat
Broadcasts: normal
Broadcast repeat on error: repeat
Group IACK: only if passed
Indiv. addressed IACK: normal|MainLcConfig|117|
|Sub > Main Configuration|Indiv. adressed: transmit always
Indiv. adressed repeat on error: repeat
Broadcasts: normal
Broadcast repeat on error: repeat
Group IACK: only if passed
Indiv. addressed IACK: normal|SubLcConfig|117|
|Main > Sub Group Configuration|Group addresses <= 0x6FFF (13/7/255): pass always
Group addresses >= 0x7000 (14/0/0): pass always
On transmission error: repeat|MainLcGrpConfig|21|
|Sub > Main Group Configuration|Group addresses <= 0x6FFF (13/7/255): pass always
Group addresses >= 0x7000 (14/0/0): pass always
On transmission error: repeat|SubLcGrpConfig|21|
|Filter Table Load State|Loaded|GroupFilterTableLoadStatus|1|
|Coupler Service Control|Inconsistency check: disabled
Heartbeat: disabled
SNA update: disabled
SNA read: enabled
Subline status: disabled|CouplServControl|8|
|Max. Routing APDU Length|220|MaxRoutingApduLength|220|

The application is on address 1.1.105
these are the info:

Device Info of Device 1.1.105

General

Item Value Resource name Unformatted value
Mask Version 07B0 1968
Individual Address 1.1.105 IndividualAddress 4457
Device Manufacturer GIRA Giersiepen DeviceManufacturerId 8
Order Number $00000000000000000000 DeviceOrderId 00000000000000000000
Serial Number 0008:128104A6 DeviceSerialNumber 0008128104A6
Firmware Version [0] 0.1 FirmwareVersion 1
Bus Voltage 30,0V (±0.5V) DeviceBusVoltage 30
Programming Mode Off ProgrammingMode false

Application Program

Item Value Resource name Unformatted value
Application program GIRA Giersiepen Applicazioni router V3.5 V3.5 ApplicationId 0008901A35
Load State Loaded ApplicationLoadStatus 1
Run State Running ApplicationRunStatus 1

Application Program 2

Item Value Resource name Unformatted value
Application program 0 0000 V0.0 PeiprogId 0000000000
Load State Loaded PeiprogLoadStatus 1
Run State Running PeiprogRunStatus 1

Group Communication

Item Value Resource name Unformatted value
Address Table Load State Loaded GroupAddressTableLoadStatus 1
Association Table Load State Loaded GroupAssociationTableLoadStatus 1
Group Object Table Load State Loaded GroupObjectTableLoadStatus 1

these are the ETS devices

1.1.0 Quadro Principale KNX/IP router V3.5 X X X X X GIRA Giersiepen 2167 00 KNX/IP router
1.1.1 Quadro Principale Camino/Caldai… Switch actuator,4 fold,universal X - X X X Video-Star 1A10xxA01R Switch actuator, 4 fold, universal
1.1.2 Quadro Principale Schalten, Treppenlicht 4f X X X X X MDT technologies AKS-0410.01 AKS-0410.01 Schaltaktor 4-fach, 4TE, 1…
1.1.3 Quadro Principale Switch actuator,4 fold,universal X X X X X Video-Star 1A10xxA01R Switch actuator, 4 fold, universal
1.1.4 Quadro Principale Switch actuator,4 fold,universal X X X X X Video-Star 1A10xxA01R Switch actuator, 4 fold, universal
1.1.5 Quadro Principale Dimmer 4 fold X X X X X Video-Star 1A04XXB03D KA/D 04.xx.1 4 fold dimmer
1.1.6 Quadro Principale Dimmer 4 fold X X X X X Video-Star 1A04XXB03D KA/D 04.xx.1 4 fold dimmer
1.1.7 Quadro Principale Dimmer 4 fold X X X X X Video-Star 1A04XXB03D KA/D 04.xx.1 4 fold dimmer
1.1.8 Quadro Principale Dimmer 4 fold X X X X X Video-Star 1A04XXB03D KA/D 04.xx.1 4 fold dimmer
1.1.9 Quadro Principale Dimmer 4 fold X X X X X Video-Star 1A04XXB03D KA/D 04.xx.1 4 fold dimmer
1.1.10 Quadro Principale Universal Interfaces, 4 fold X X - X X Video-Star 1M10xxC01K Universal Interfaces, 4 fold
1.1.11 Quadro Principale Logik, Zeitglied, Temperaturvergleich X - X X X MDT technologies SCN-LOG1.01 SCN-LOG1.01 Logikmodul, 2TE
1.1.12 Quadro Principale Riscaldamento Switch PWM 2067/0.1 X - - - X Schneider Electric Industries SAS MTN645129 Heizungsaktor REG-K/6x230/0,05A
1.1.13 Quadro Principale Tapparelle Jalousie, Rollade 8f 10 A X X X X X MDT technologies JAL-0810.01 JAL-0810.01 Jalousieaktor 8-fach, 8TE, …
1.1.14 Quadro Principale Tende Jalousie, Rollade 8f 10 A X X X X X MDT technologies JAL-0810.01 JAL-0810.01 Jalousieaktor 8-fach, 8TE, …
1.1.105 Quadro Principale Applicazioni router V3.5 X X X X X GIRA Giersiepen 2167 00 KNX/IP router
1.1.250 Quadro Principale iKnix ETS KNiX Port Gateway X X X X X iKNiX KNiX Port Gateway KNiX Port Gateway

PAPERUI Things configuration:

Configuration Parameters

Configure parameters for the thing.

IP Connection Type

Router

The ip connection type for connecting to the KNX bus. Could be either TUNNEL or ROUTER

                      ()

Network Address

Network address of the KNX/IP gateway

Port

Port number of the KNX/IP gateway

Local Network Address

Network address of the local host to be used to set up the connection to the KNX/IP gateway

Local Device Address

The Physical Address (Individual Address) in x.y.z notation for identification of this KNX/IP gateway within the KNX bus

Use NAT

Set to “true” when having network address translation between this server and the gateway

Reading Pause

Time in milliseconds of how long should be paused between two read requests to the bus during initialization

Response Timeout

Seconds to wait for a response from the KNX bus

Read Retries Limit

Limits the read retries while initialization from the KNX bus

Auto Reconnect Period

Seconds between connection retries when KNX link has been lost, 0 means never retr

I connect the interface in ROUTER mode, it says ONLINE, and in the LOG i can see this:
2019-01-18 16:30:38.835 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.107’ to ‘2/2/2’ with value ‘[1]’

2019-01-18 16:30:39.558 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:08beb4b1 is disconnecting from the KNX bus

2019-01-18 16:30:39.614 [DEBUG] [nx.internal.client.AbstractKNXClient] - The KNX network link was detached from the process communicator

==> /var/log/openhab2/events.log <==

2019-01-18 16:30:39.668 [hingStatusInfoChangedEvent] - ‘knx:ip:08beb4b1’ changed from ONLINE to OFFLINE

2019-01-18 16:30:39.704 [me.event.ThingUpdatedEvent] - Thing ‘knx:ip:08beb4b1’ has been updated.

2019-01-18 16:30:39.713 [hingStatusInfoChangedEvent] - ‘knx:ip:08beb4b1’ changed from OFFLINE to OFFLINE (CONFIGURATION_ERROR): The ‘ipAddress’ of the gateway must be configured in ‘TUNNEL’ mode

==> /var/log/openhab2/openhab.log <==

2019-01-18 16:30:48.847 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:08beb4b1 is disconnecting from the KNX bus

==> /var/log/openhab2/events.log <==

2019-01-18 16:30:48.836 [me.event.ThingUpdatedEvent] - Thing ‘knx:ip:08beb4b1’ has been updated.

==> /var/log/openhab2/openhab.log <==

2019-01-18 16:30:48.868 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:08beb4b1 is connecting to the KNX bus

2019-01-18 16:30:48.871 [DEBUG] [binding.knx.internal.client.IPClient] - Establishing connection to KNX bus on 224.0.23.12:3671 in mode ROUTER.

==> /var/log/openhab2/events.log <==

2019-01-18 16:30:48.877 [hingStatusInfoChangedEvent] - ‘knx:ip:08beb4b1’ changed from OFFLINE (CONFIGURATION_ERROR): The ‘ipAddress’ of the gateway must be configured in ‘TUNNEL’ mode to UNKNOWN

2019-01-18 16:30:48.912 [hingStatusInfoChangedEvent] - ‘knx:ip:08beb4b1’ changed from UNKNOWN to ONLINE

==> /var/log/openhab2/openhab.log <==

2019-01-18 16:30:49.744 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.108’ to ‘2/0/5’ with value ‘[12, 41]’

2019-01-18 16:30:49.763 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.108’ to ‘2/2/3’ with value ‘[0]’

2019-01-18 16:30:51.586 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.109’ to ‘2/0/6’ with value ‘[7, -38]’

2019-01-18 16:30:51.606 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.109’ to ‘2/2/4’ with value ‘[0]’

2019-01-18 16:30:53.282 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.115’ to ‘3/1/7’ with value ‘[1]’

2019-01-18 16:30:56.586 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.47’ to ‘3/1/6’ with value ‘[1]’

So i assume that the connection is weel done, i read the knx bus broadcast telegram

BUT…
i can’t turn switch on or off…

ITEMS:
[16:38:37] openhabian@openHABianPi:/etc/openhab2/items$ cat knx.items
Switch BComSpecchio “Luce Specchio” [ “Lighting” ] { knx=“0/0/23+0/1/23” }
Switch BPadSpecchio “Luce Specchio Padronale” [ “Lighting” ] { knx=“0/0/30+0/1/30” }
Switch PadTestaSx “Testaletto sx” [ “Lighting” ] { knx=“0/0/25+0/1/25” }
Switch PadTestaDx “Testaletto dx” [ “Lighting” ] { knx=“0/0/26+0/1/26” }

SERVICES:
[16:40:54] openhabian@openHABianPi:/etc/openhab2/services$ cat knx.cfg
type=ROUTER
[16:41:00] openhabian@openHABianPi:/etc/openhab2/services$

Please, can you HELP?