ok, I’ll tread carefully!! Let me see if I can get to the next stage. Will let you know how i get on ! Thanks again.
Pete
1 Like
Oh…and I had my IP Router IP address set as ‘KNX gateway IP address’ before (192.168.1.12) instead of the multicast address of 224.0.23.12
Bit misleading in the config file as it says "KNX gateway IP address’… I’d never have got that without your help!
Think it should say ‘multicast address’ to help!
Pete
When using Router connection type, this ip setting is optional since it defaults to the correct Multicast IP (224.0.23.12)
If this setting is used, it should be configured to the Multicast IP Address allocated to KNXnet/IP.
I usually set it to avoid problems (see: KNX Binding Configuration Changes cause Exception). It’s just a pre-caution 
Is the ‘localIP’ address optional too if in ROUTER mode? I say that as I’m working on my MAC with DHCP, so i need to check I’ve not got a new IP address if i reconnect to the network!
Yup, ‘localIP’ is also optional. OpenHab will automatically detect it from your local hosts file (it’s ok to use DHCP for your OpenHab host but it’s not really recommended ).
It helps if you are running OpenHab on a host with multiple IP Interfaces/Addresses and you need to instruct OpenHab to use a specific IP for multicast communications to the KNX Router (to be on the same IP subnet).
Hi Dim
Can you give me a couple of examples of your KNX bindings in HAB 2. Can’t find much doc on how/where to setup the channel. Its changed from HAB 1.8, so need to re-do my items
Pete
Sure. Example config:
/etc/openhab2/items/my.items
Switch My_Light "My Light" {knx="1/0/1+<1/2/1"}
The knx binding info is: On/Off GA (1/0/1), then + sign for Status GA (1/2/1) and < sign for status read request on OpenHab startup.
/etc/openhab2/sitemaps/my.sitemap
Switch item=My_Light
Start small, test 1 KNX item using your Group Addresses and then start to enhance the configs. Also: Try to avoid using complex stuff at this troubleshooting stage (e.g. no rules, etc).
Since the KNX Binding in OpenHab 2 is still version 1.x, it uses the same formatting as the one used in OpenHab 1.
The locations of the files are different, but the syntax of their contents should remain the same
1 Like
ah, ok. So it’s pretty similar to 1.8 for the KNX bindings. Don’t need to worry about the channel setting stuff.
Will give this a try
Yeah… Forget things and channels for now or using Paper UI to configure your KNX stuff
You use Paper UI only to install the KNX Binding at the very beginning (you already did that)
Everything around configuration of KNX items is still being done with config files (just like OH1)
When KNX Binding version 2.x will arrive… many things will change (for the better :))
just tried 1 light. but when I used openHAB to turn it on it was flickering on and off! Will take a look when have more time, but at least I’m now communicating - which is fantastic progress
Thanks a lot!!
Pete
that problem (flickering on/off) is immediately solvable with:
ignorelocalevents=true
in you /etc/openhab2/services/knx.cfg
Restart OpenHab 2 afterwards.
sorry… forgot to mention that
You are all set, up and working ! 
(you are welcome)
1 Like
YEP - that was it!!!
Fantastic stuff 
Will let you know how i get on with others swtches/controllers…have heating and lighting all on KNX…
Harmony remote and Onkyo amp were picked up by openHAB as ‘things’ automatically too!
…think i have a busy weekend ahead!
Pete
1 Like
Hi Dim
Just as an update…have made great progress…
Got a lot of my lights switching on and off now, its very responsive - just as good as the Gira Homeserver.
I was running on my Mac, but have now ‘splashed out’ on a Raspberry Pi and got that all up and running too. What a great bit of kit that is! I’ve sat it on top of my Homeserver!
Now I’m out in the ‘IP World’ I’ve been testing out an Amazon Echo. And, hey, I’ve even got that working too. Using a HA Bridge which fools the Echo into thinking that my KNX light switches are Philips Hue - its great!
Will keep you updated on progress. Next step, temp monitoring!
Pete
Great news ! 
Have fun with the configs!
You mean… better ? 
Of course it’s better - but I can’t admit that as HomeServer cost me a fortune!!! 
Have you tried the recently updated KNX 1.9.0-SNAPSHOT binding? @lewie recently updated it and it would be good to see if it still works as intended for your installations (not that I doubt it, but it might work even better than previous).
yes, am on that. seems to be working well - thanks
Hello, I ask my question here, because it seems I have a similar problem.
Some month ago, I ask here in the forum how to connect via EibMarkt IP-Interface to KNX. I made a lot of trials with strange results. Some were working one time, but not again. I came to this:
Using KNXD:
/usr/bin/knxd --eibaddr=0.0.231 -DTRS -b ipt:192.168.133.200
connected via TUNNEL mode.
I got the hint to throw out KNXD and connect direct with OH2.
It was working then, not good, but not bad. Sometimes Lights don’t turn on or turn on to late.
Today I thought to work on that subject again and kicked KNXD out.
It was working, but after about 50 min I got errors in the log.
OH tries to reconnect, but then the log shows:
could not accept new connection (maximum reached)
And all the time, KNX is working.
So, I think, OH is (re)connecting multiple times, till all possible connections to the interface are used.
Which means, OH does not notice the connection is allready running.
I searched and found this thread…
I can not [quote=“Dim, post:6, topic:15074”]
disable the reliable communications
[/quote]
of my interface, nor can I use it as a line coupler.
On this “Interface” I can only set the IP, DHCP or not and the Gateway.
I’m finished.
Anybody who has good idea what to do?
And the log (I cleaned it to only have the KNX stuff in it):
2017-02-21 12:16:28.910 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'windowcontact.items'
2017-02-21 12:16:29.976 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'Haus.items'
2017-02-21 12:18:58.548 [INFO ] [nx.internal.connection.KNXConnection] - Established connection to KNX bus on 192.168.133.200:3671 in mode TUNNEL.
2017-02-21 13:09:02.036 [WARN ] [.binding.knx.internal.bus.KNXBinding] - Value '0.0' could not be sent to the KNX bus using datapoint 'command DP 0/5/0 HWR_Brightness, DPT main 0 id 9.001, low priority' - retrying one time: link closed, connection closed
2017-02-21 13:09:02.029 [WARN ] [nx.internal.connection.KNXConnection] - KNX link has been lost (reason: server request on object tunneling link link (closed) 192.168.133.200:3671 TP1 medium, device 5.5.5, hopcount 6)
2017-02-21 13:09:02.048 [INFO ] [nx.internal.connection.KNXConnection] - KNX link will be retried in 30 seconds
2017-02-21 13:09:02.055 [ERROR] [.binding.knx.internal.bus.KNXBinding] - Received detach Event.
2017-02-21 13:09:02.068 [INFO ] [nx.internal.connection.KNXConnection] - Established connection to KNX bus on 192.168.133.200:3671 in mode TUNNEL.
2017-02-21 13:09:23.538 [INFO ] [ternal.communicator.HomematicGateway] - No event since 344 seconds from gateway '0415441B-D197-EE66-6F44-38A47651DB06', restarting RPC server
2017-02-21 13:09:32.051 [INFO ] [nx.internal.connection.KNXConnection] - Trying to (re-)connect to KNX...
2017-02-21 13:09:32.056 [ERROR] [tuwien.auto.calimero ] - KNXnet/IP Tunneling 192.168.133.200:3671: could not accept new connection (maximum reached)
2017-02-21 13:09:32.057 [ERROR] [nx.internal.connection.KNXConnection] - Error connecting to KNX bus: error response from control endpoint /192.168.133.200:3671: could not accept new connection (maximum reached)
2017-02-21 13:09:32.057 [ERROR] [tuwien.auto.calimero ] - KNXnet/IP Tunneling 192.168.133.200:3671: establishing connection failed, error response from control endpoint /192.168.133.200:3671: could not accept new connection (maximum reached)
2017-02-21 13:09:32.058 [INFO ] [nx.internal.connection.KNXConnection] - KNX link will be retried in 30 seconds
2017-02-21 13:10:02.051 [INFO ] [nx.internal.connection.KNXConnection] - Trying to (re-)connect to KNX...
2017-02-21 13:10:02.060 [ERROR] [tuwien.auto.calimero ] - KNXnet/IP Tunneling 192.168.133.200:3671: could not accept new connection (maximum reached)
2017-02-21 13:10:02.061 [ERROR] [tuwien.auto.calimero ] - KNXnet/IP Tunneling 192.168.133.200:3671: establishing connection failed, error response from control endpoint /192.168.133.200:3671: could not accept new connection (maximum reached)
2017-02-21 13:10:02.061 [ERROR] [nx.internal.connection.KNXConnection] - Error connecting to KNX bus: error response from control endpoint /192.168.133.200:3671: could not accept new connection (maximum reached)
2017-02-21 13:10:02.064 [INFO ] [nx.internal.connection.KNXConnection] - KNX link will be retried in 30 seconds
2017-02-21 13:10:24.943 [INFO ] [ternal.communicator.HomematicGateway] - No event since 406 seconds from gateway '0415441B-D197-EE66-6F44-38A47651DB06', restarting RPC server
2017-02-21 13:10:32.051 [INFO ] [nx.internal.connection.KNXConnection] - Trying to (re-)connect to KNX...
2017-02-21 13:10:32.059 [ERROR] [tuwien.auto.calimero ] - KNXnet/IP Tunneling 192.168.133.200:3671: could not accept new connection (maximum reached)
2017-02-21 13:10:32.060 [ERROR] [nx.internal.connection.KNXConnection] - Error connecting to KNX bus: error response from control endpoint /192.168.133.200:3671: could not accept new connection (maximum reached)
2017-02-21 13:10:32.060 [ERROR] [tuwien.auto.calimero ] - KNXnet/IP Tunneling 192.168.133.200:3671: establishing connection failed, error response from control endpoint /192.168.133.200:3671: could not accept new connection (maximum reached)
2017-02-21 13:10:32.061 [INFO ] [nx.internal.connection.KNXConnection] - KNX link will be retried in 30 seconds
2017-02-21 13:11:02.051 [INFO ] [nx.internal.connection.KNXConnection] - Trying to (re-)connect to KNX...
2017-02-21 13:11:02.055 [ERROR] [tuwien.auto.calimero ] - KNXnet/IP Tunneling 192.168.133.200:3671: could not accept new connection (maximum reached)
2017-02-21 13:11:02.055 [ERROR] [nx.internal.connection.KNXConnection] - Error connecting to KNX bus: error response from control endpoint /192.168.133.200:3671: could not accept new connection (maximum reached)
2017-02-21 13:11:02.057 [INFO ] [nx.internal.connection.KNXConnection] - KNX link will be retried in 30 seconds
2017-02-21 13:11:02.057 [ERROR] [tuwien.auto.calimero ] - KNXnet/IP Tunneling 192.168.133.200:3671: establishing connection failed, error response from control endpoint /192.168.133.200:3671: could not accept new connection (maximum reached)
2017-02-21 13:11:26.201 [INFO ] [ternal.communicator.HomematicGateway] - No event since 467 seconds from gateway '0415441B-D197-EE66-6F44-38A47651DB06', restarting RPC server
2017-02-21 13:11:26.206 [WARN ] [ternal.communicator.HomematicGateway] - Die Adresse wird bereits verwendet
2017-02-21 13:11:32.051 [INFO ] [nx.internal.connection.KNXConnection] - Trying to (re-)connect to KNX...
1 Like
Hi Dimitris and anybody else willing to help,
First of all I wanna thank you for the detailed post. Finally I can use my Gira router in router mode and now I can control perfectly my fairly complex knx installation (few hundreads group addresses). Also when I change the state of a switch using OpenHab2 interface the actual light comes on immediately (before, in tunnel mode, there was a long delay).
The still have one problem:
Using Openhab2 I can fully control every KNX device (with the UI, with the Android app, with myopenhab cloud service, and even even using Amazon Echo). If I change on a light using the mobile app, the UI is update and viceversa.
But if I switch on a light using a wall switch, the light comes on but the Openhab interface is not updated!
Looking at the log file nothing happens when I use a wall switch.
This is my configuration:
-
Openhab version: 2.2.0
-
KNX binding 1.9
-
Gira router
-
KNX conf file (knx.cfg)
ip=224.0.23.12
ignorelocalevents=true
type=ROUTER -
Example of item in demo.items file
Switch Light_Living_Table “Table” (Room_Living, Lights) {autoupdate=“true”, knx=“0/2/9”} -
KNX topology set as you described in your post.
Thanks,
Alex
looks like that you have only the command Group Address defined in your items
you also need to use the status GA to be able to read the status/events from KNX