Problem with ip connection through loxone to knx

[Tom Cassimon]

Hi,

recently (after an update of loxone and ETS software) i'm unable to program KNX devices through the loxone KNX interface. The KNX interface itself appears to be working, the loxone miniserver receives messages from the bus and acts upon it. In loxone config i can monitor the KNX bus to see messages appearing. Even in the ETS software I can monitor the KNX bus. But when I test the connection or try to download programming in a KNX component I get following error in the logging of the ETS software:

2016-06-09 13:30:21,873 [1] INFO  Falcon.Bus - opening connector KnxIpTunneling with params Tunneling, IPAddress=192.168.113.11, IPPort=3671, UseNat=False in mode LinkLayer

2016-06-09 13:30:21,874 [1] INFO  Falcon.ConnectionManager - Connection Con-ID: KnxIpTunneling, Tunneling, IPAddress=192.168.113.11, IPPort=3671, UseNat=False (Ch=0) not found; creating new

2016-06-09 13:30:21,875 [1] INFO  Falcon.TunnelingBusConnector - Connect tunneling bus connector to Tunneling, IPAddress=192.168.113.11, IPPort=3671, UseNat=False, type Tunneling, useNat False, mode LinkLayer

2016-06-09 13:30:21,877 [1] INFO  Falcon.TunnelingBusConnector - opening firewall for 192.168.113.110:64595

2016-06-09 13:30:31,877 [1] INFO  Falcon.KnxIp.DeviceManagementBusConnector - Connect tunneling bus connector to Tunneling, IPAddress=192.168.113.11, IPPort=3671, UseNat=False, type DeviceManagement, useNat False, mode LinkLayer

2016-06-09 13:30:31,907 [7] FATAL Falcon.MessageFrameReceiver - error in processing telegram frame $06, $10, $02, $04, $00, $42, $36, $01, $02, $00, $11, $fa, $00, $00, $50, $4f, $94, $10, $13, $68, $00, $00, $00, $00, $50, $4f, $94, $10, $13, $68, $6c, $78, $6c, $31, $33, $36, $38, $00, $00, $00, $00, $00, $00, $00, $00, $00, $00, $00, $00, $00, $00, $00, $00, $00, $00, $00, $00, $00, $00, $00, $08, $02, $02, $01, $03, $01: System.IO.EndOfStreamException: Trying to read 1 bytes but there are only 0 bytes available

   at ag0.c(Int32 A_0)

   at ag0.r()

   at ag0.t[a]()

   at af2.fp(ag0 A_0)

   at acf..ctor(ag0 A_0)

   at af2..ctor(ag0 A_0)

   at acf.dy(ag0 A_0)

   at afb.fp(ag0 A_0)

   at ab6..ctor(ag0 A_0, IPEndPoint A_1)

   at afb..ctor(ag0 A_0, IPEndPoint A_1)

   at afl..ctor(ag0 A_0, IPEndPoint A_1)

   at af5.a(Byte[] A_0, IPEndPoint A_1, Boolean A_2, Byte[] A_3)

   at af8.o(IAsyncResult A_0)

2016-06-09 13:30:34,906 [1] ERROR Falcon.TunnelingBusConnector - failed to receive response for DescriptionRequest: controlEndpoint=192.168.113.110:64594 on client 192.168.113.110:64594

2016-06-09 13:30:34,907 [1] INFO  Falcon.KnxIp.DeviceManagementBusConnector - Disconnect DeviceManagementBusConnector bus connector from Tunneling, IPAddress=192.168.113.11, IPPort=3671, UseNat=False

2016-06-09 13:30:34,908 [1] INFO  Falcon.Bus - disconnecting interface Connector KnxIpTunneling, OpenParams=Tunneling, IPAddress=192.168.113.11, IPPort=3671, UseNat=False, ChnId# 26

2016-06-09 13:30:34,909 [1] INFO  Falcon.ConnectionManager - Release connector 'Tunneling, IPAddress=192.168.113.11, IPPort=3671, UseNat=False'.

2016-06-09 13:30:34,910 [1] INFO  Falcon.ConnectionManager - ...Finally released connector 'Tunneling, IPAddress=192.168.113.11, IPPort=3671, UseNat=False'.

2016-06-09 13:30:34,910 [1] INFO  Falcon.TunnelingBusConnector - Disconnect TunnelingBusConnector bus connector from Tunneling, IPAddress=192.168.113.11, IPPort=3671, UseNat=False

I've disable firewall en antivirus software just to be sure (read somewhere there could be missing firewall rules, that prevent you from making a connection), but I'm still unable to program any KNX device. I suspect an update of the loxone miniserver is causing the issue, i've already opened a ticket with them, but up until now no response from them.

Thanks in advance for your reply.

Regards,

Tom

[Duncan]

as far as i know, 7.4 versions of loxone wont talk to ets 5.5 - you need to use the 7.5betas of loxone, or roll back to ets 5

[tzajaczk]

The problem is well known @ Loxone...
Here is the new version with the bug correction :

https://drive.google.com/open?id=0Bz9Z-b63UjHMendvQjhmNjBsZnc

[Pawel Wojcik]

Is there any way to connect to ETS through LOXONE Miniserver without etc licence? For home use.

[Duncan]

as far as i know, the test / free version of ets will still use loxone as an ip/knx gateway to program devices - it just has a smaller limit of devices per knx project.

[Pawel Wojcik]

Thanks Duncan. I tried to use ets3 and there’s not possible. 

Have you seen any good instruction how to do it? The one on Loxone website is for older version of ets. 

W dniu wt., 26.12.2017 o 11:39 PM Duncan <joanne...@gmail.com> napisał(a):

as far as i know, the test / free version of ets will still use loxone as an ip/knx gateway to program devices - it just has a smaller limit of devices per knx project.

--
You received this message because you are subscribed to a topic in the Google Groups "Loxone English" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/loxone-english/Gzc8oFA58fM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to loxone-englis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/loxone-english/69b13841-1806-4da0-9e18-d296d1ecfdf9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Pozdrawiam
Paweł

[Duncan]

check this thread first:

https://groups.google.com/forum/#!searchin/loxone-english/ets|sort:date/loxone-english/eqpgQtScIF4/TT_7O-iMBwAJ

have you tried with the latest v5 of ets?
does ets find your miniserver as a gateway?
go in to ets, bus, there should be the miniserver under discovered interfaces, but add another manual entry for your miniserver ip address and tick the NAT box, then test that connection