When I try to use a dedicated tunnel of the MDT SCN-IP100.03 IP e.g. 1.0.2 by exporting the connection information from ETS into the wizard Home Assistant is establishing the connection always with the next tunnel connection, i.e. 1.0.3. When I try to set up 1.0.3 it takes 1.0.4* and so on…
There is also a message showing:
KNX Interface Verbindungstyp wurde nicht verfügbar
20:39:32 - Vor 11 Minuten
Because I have some KNX devices sending Data Secure messages I cannot reveive these messages due to the tunnel shift.
Because I read other issues related MDT SCN_IP100.03, I upgraded the firmware to 4.0.7 and use knxproj V3.0 but with no success.
Hi unfortunately this is a known issue with the MDT Routers and interfaces. A workaround is to associate the data secure addresses to all interface tunnels and use any but the last tunnel to export the interface parameters. That works in my situation. It will still use the next tunnel but since the address is whitelisted in the secure devices they will accept the telegrams.
@richardpolzer Thanks a lot for your hint. You made my day.
But it’s still crazy!
For me the last tunnel (#4) which is provided by MDT Router didn’t work because then Home Assistant didn’t get the not available tunnel #5.
Instead I have to use tunnel #3 and copied the group adress associations to all other tunnels as you recommended.
This really doesn’t make any sense.
But it works now.
For all others these are the steps that I selected in the HA wizard:
Stumbled over the same issue yesterday. I have just assigned all my GAs to the next Tunneling Channel, as it seems to always choose the next one. Shouldn’t this be enough, or why assign it to all channels?
Is the filter table of your mdt router also empty when looking at it in ETS?
The main reason I started to look around was for these error messages in my log file (I have everything on one line, just using the router for IP connection to the outer world).
Could not sync group address ‘1/2/3’ (Entity name - Feature)
Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: ‘1/2/3’
Tunnells are topological located at sub-Line. Filter tables only apply for communication with different lines (for a router that’s IP). So in case of a single-Line installation you don’t need to worry about filter tables (and don’t really need a router).
Technically it should work assigning the GAs just the exported and the next tunnel. However based on availability and usage of the tunnels the Router might decide to pick another tunnel than one of the two we are talking about. This is non standard behavior and should be addressed by MDT. If that is the case and we do get a different IA then it’s best to have the GAs assigned to all of the tunnels to be sure.
The assignment will only whitelist the IAs of the tunnels within the Devices that use that GA securely. Kinda like if you revive an encrypted request from IA 1.1.65 then process it. If it’s not whitelisted it will be ignored. That’s also the reason why you need to reprogram all secure devices using that GA once you make the assignment.
I think it’s an off-by-1 error in the MDT application since I’ve never heard about it using another tunnel than +1. So if you only export a single tunnel endpoint from ETS as keyring file, you’ll get the next tunnel with MDT. Since you can only connect with that exported user_id (IP secure tunnelling), you won’t get another tunnel. If it is occupied, the connection should fail.
That’s the same observation I also made during extensive testing.
I still get the same error in HA log with
* Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 1/1/11
* Could not sync group address '1/1/11' (Unknown - State)
It is always the same (not secure) GA. Has anyone an idea what could be the reason for this, if it’s not the filter table as described in the integrations documentation?
