Even though I couldn’t find any reference in the technical specifications of the GIRA 1030 00 model that you have, it seems that it supports only 1 concurrent tunneling connection.
In theory, this single tunneling connection is used up by the Gira Homeserver and that’s why you were getting that response from the Router in the OH Logs (could not accept new connection (maximum reached)).
The other terminals that connect to the GIRA Homeserver do not affect this parameter since the only device communicating with the GIRA KNX/IP Router is the Homeserver.
You could retry (just for testing purposes) to temporarily shut down the Homeserver and see if OpenHab will establish a tunnel to the Router.
Now, in ROUTER mode, this limitation does not apply and you should be able to connect to it.
Did your logs show this message: “Established connection to KNX bus on 224.0.23.12:3671 in mode ROUTER.” ?
Your items config looks good (the 2 switches with their GAs) and I the only reason that I can identify for this situation is that the GIRA KNX/IP Router should be set as a Line Coupler (PA of type: x.y.0) and not as a Data Interface.
In my case (with the 216700 model) in order to get the ROUTER mode to work, I had to change the PA from 1.1.200 (configured as a Line Repeater/Data Interface) to 1.1.0 (configured as a Line Coupler).
Can you modify the PA of the Router and try ROUTER mode again?
By the way: Which version of OH and KNX Binding are you using?
Have tried switching off the Homeserver to see if I’m limited to 1 connection. It was still giving the same ‘max connections’ error. I’m going to try a few more options as you suggest over the next day or so.
Thanks for your help – am sure I’ll find out what it is shortly – I’ll report back!
Now, when you mentioned about the router settings, i thought I’d check to see if there were parameters set…I had a suspicion that there must be a setting to say where to receive telegrams from in IP - see pic…
Must have some setting in here to restrict the IPs it receives comands from?
It makes sense, probably some security setting so you can’t just send comands from any device on the IP network. I see that the new Gira Router has an encryption option too - lucky i don’t have that
I don’t think that you can control this aspect from the ETS parameters of the device (to accept/receive communications from a specific remote IP Address (e.g. the Homeserver) only).
By the way: The IP Routing multicast in your screenshot is correct. No need to change that.
Multicast IP Address 224.0.23.12 is registered for use by the KNXnet/IP protocol and can be used by many devices concurrently.
To simplify: This acts like a broadcast channel. An IP device can broadcast to this address and all listening to it will receive the message. It is connection-less (no point to point link is established), contrary to the tunnel configuration where a permanent connection is established and uses the individually assigned IP Address (in this case: 192.168.1.12) and UDP port 3167.
In my experience, the best way for OpenHab to connect to a KNX system via a Router is to use multicasting (ROUTER type in the knx.cfg). There are some additional considerations to be made when using the KNX/IP device as a router: You need to configure the Filter Table of the Router device within ETS to allow routing of KNX Telegrams from the KNX Bus to the IP network (and from IP to Bus).
This can be done either with:
a) A Dummy application in ETS that has the required Group Addresses linked to it (prefered)
or
b) Allow mass routing of telegrams from Bus->IP and from IP->Bus (not really recommended :))
or
c) Manual editing of the Filter Table of the KNX Router (really, really not recommended :))
I would try to get Routing working… it is the best way and it will work in parallel with your existing setup (with the Homeserver).
I have only 1 concern… I am not 100% sure if the Router will respond in parallel to both unicast (Tunneling) as well as multicast (Routing) IP communications… From what I know (from my GIRA 216700): This works fine.
BR,
Dim
Ps: IP Config tabs are all looking good! IP Config 1 shows you the multicast address and allows you to change the individual device IP Address assignment and since you have set it to manual (correctly), it enables IP Config 2 tab (where you set the static IP of the GIRA KNX Device) and IP Config 3 tab (where you set the default gateway)
Important note: If you want to use multicasting to communicate to the GIRA 103000 KNX/IP Router, you will need to change it’s Physical Address (PA) in the KNX Line from 1.0.255 to 1.0.0.
The PA of x.y.z type (1.0.255) sets the device in a Line Repeater mode and will not allow proper routing of KNX Telegrams. It works fine for tunneling.
The PA of x.y.0 type or x.0.0 (1.0.0) sets the device in Line Coupler / Area Coupler mode (the correct setting for a routing environment). Tunneling also works fine here.
The IP Address can remain the same (192.168.1.12) and this PA change should not affect the communications with the GIRA Homeserver (which is most likely using unicast (tunnel) to connect to the Router… can you check that please from the configs of the Homeserver and let me know?))
HomeServer should continue to work even after the PA change. Check the HomeServer configuration in advance to see how it is set to connect to the GIRA Router. It should be based on tunnel config (with the IP 192.168.1.12 of the Router).
If anything goes wrong, revert back to the original PA (1.0.255).
Since the IP will not change, the HomeServer will be able to connect to the Router without problems and establish a tunnel.
Remember to configure the Filter Table also on the KNX Router. Add a dummy application in your ETS Project that represents OpenHab and link the Group Addresses that you want to allow to be routed between the 2 “worlds” (KNX Bus and IP). Put this dummy App in a new Line (e.g. 1.1) and give it a PA in that new line (e.g. 1.1.200). Then, link the GAs to the dummy app and the ETS will automatically calculate the Filter Table for the Router. Reprogram the Router afterwards using ETS.
When I try to change the PA in ETS4 of the IP Router is says 'Set Address of Device ‘0.0.255 FC01 router’ to ‘0’ failed. The usage of IP routers requires a IP backbone line.
Do I need to create a new line with just the IP router on it now? Currently it is on the same line as all the other KNX devices.
The Router should remain in the existing position in the ETS Project (within the existing Line).
The error that you are getting is because your Backbone Area has “TP” set as the Backbone Medium (this is the default in ETS Projects).
To change that to IP, go to the Topology Workplace Panel in ETS and select Topology from the left side, then Properties->Settings->Backbone Medium->IP.
Here is my setup (with the extra line holding the dummy application for configuring the filter table in the router):
? Changing the Backbone Media moved your devices from Line 1 ? That’s strange…
Keep Line Medium to TP. In this way, you shouldn’t affect your existing devices. All the old devices (and the Router) should stay where they are (in the existing Line)
Change Backbone Media to IP to allow you to reconfigure the PA of the Router
Also: Use the Undo function if something goes obviously wrong. Don’t try to move more stuff around since this could create a mess
The Link between the 2 “worlds” (TP and IP) is the Router.
It is positioned in the TP Line since it is primarily a TP device and can see all KNX Telegrams from other TP devices in its line.
The Backbone should be set to IP to allow the Router to communicate the Telegrams “upwards” towards the IP “world”
Well… I don’t have a GIRA HomeServer, but from what I know, it is a regular IP host/device (similar to a Raspberry Pi or a PC running OpenHab)
It has it’s own IP Address and connects over IP to the GIRA KNX/IP Router.
The HomeServer does not directly “talk” TP since it doesn’t have an interface for KNX Bus.
In theory, the HomeServer establishes a Tunnel connection over IP to the Router and can receive/transmit Telegrams from/to the KNX Bus via the Router.
In parallel, we will configure the GIRA KNX/IP 103000 Router to properly use Multicasting so that OpenHab 2 can also communicate with the Router (using the 2nd method: routing) so that we can also access KNX Telegrams over IP.
)