Connection closed by remote device

Hi everyone,

I have had the same issue while using LSS100100/LSS100200 Wiser for KNX and SpaceLYnk.

the issue was caused by home assistant using the KNX IP tunnel function wile i was trying to commission the device.

If you are having similar issue make sure to not have any other device tunneling to the IP interface while you try to commission.

Hi Petr,

Thank you very much for sharing this solution. I’ve tried almost everything and spent many hours on it. As soon as I disconnected my Home Assistant connection, it uploaded the new configuration without any issues. Funny that this isn’t a problem with all components.

Just to mention that I'm using latest ETS version 6.0.6 

Hi Ioannis, try to use the "Use reduced bus communication rate" setting from the project details. Let us know if it worked. //Vassilios

Good morning,

The same thing happened to me yesterday with a Homelynk LSS100100 from Schneider Electric. I programmed 4 devices with no problem, then went back to my desk to make some changes and came back to program the rest of the devices.

I got the same error of this thread: 'Connection closed by remote device'. The loading bar was not starting to turn green. I tried to use "Use reduced bus communication rate", the bar was almost half loaded, and the same error came out again.

In the end I tried with an MTN6502-0105 IP interface, and I was able to program the equipment.

Have you been able to solve the problem in these two months? It's a very annoying problem, and I was lucky to have an additional interface available.

ETS version: 6.1.0 (build 5686)

Kind regards

Hello

We have the same problem ('Connection closed by remote device) with the current ETS 6.1.0 (Build 5686) and the IP router MDT SCN-IP100.03. It doesn't work with "Slow tunneling connection" or without.

What is the solution?

Kind regards

I have the same issue with ETS 6.1.0 (Build 5686)..

Serge

I have the same Issue ETS 6.1.0 (Build 5686)

Kr

Did you find a solution to the issue ? 
I am having the same problems with a MTN670802 on ETS 6.1.0 (Build 5686)

I have same issue with ETS 6.10 and IP interfece SCN-IP000.03
Not only that when I download all with assignment of individual address, during download it stuck at around 60%-70% and appear this msg "Connection closed after too many TTL and Device does not respond"

Any one know how to solve this?

Same here: Download failed - connection closed by the remote device.

Using ETS 6.1.0 and my Wiser for KNX as IP interface. Have the issue with all my four MTN6710-0004 dimming devises.

Already followed these instructions: https://www.se.com/be/fr/faqs/FAQ000245979/ 

but nothing seems to work

@Vasilios Lourdas the "Use reduced bus communication rate" setting worked in my case, thank you!

I am also facing the same challenge.  All solutions outlined above didn't work for me. I am using ETS6.1.1. I cannot update any device on my ongoing project 

Same problem here.  I am using the latest ETS 6.1.1 (Build 6264). Reduced bus communication rate does not help.  What could be causing the problem? Anyone a solution?

Same problem here with Schneider Electric LSS100100 as IP interface and using ETS 6.1.1 (build 6264). I can program some devices in my installation, but e.g. all my Schneider Electric WDE002933 push-button switches fail with error "Connection closed by remote device". Option "Use reduced bus communication rate" does not help.

I'm facing the same issue on a Schneider MTN6725-004 DALI-Gateway Basic REG-K, while trying to download the application. Tryed to use reduced bus communication rate, too but it didn't work. Switching light's on/off via DCA is working fine. Any solution?

Facing the same issue with zennio USB interface !!

Same problem with the ISE Smart Connect

Removing the Gira line repeater and upgrading the power supply to 1280 mA resolved the " Connection closed by remote device" problem.

Is there any update on this? This is a real problem that seems to affect multiple installations as reported in this thread and also in other forum threads if you do a search. I just checked it again with my house using the latest ETS6 and the problem is still there.

A more powerful power supply (1280 mA) resolved the issue in my case

in my case i just changed the individual address to new address then full download. this happened to me multiple times with MDT devices, once with Timer switch, and once with analogue actuator.

Just an update how I was able resolve this. Did a lot of googling and experimenting, and finally found out that when I switch the connection type from "IP tunneling" to "Ethernet" (with the multicast address configured in LSS100100, is this the same as IP routing?) it finally started working. I noticed that communication from ETS6 worked well with all other devices in IP tunneling mode except for the Schneider Electric WDE002933 push buttons.

Hi Seppo, 

Can you maybe share a bit more detail on how you set this up, both in your LSS100100 and in ETS. 

Thanks. 

Here are some screenshots how my ETS6 and LSS100100 are configured. Still I do not know what is the real root cause, but I am happy that it works for now.

Hi, 

Thanks for sharing. However, it does not solve my problem. Apparently there is a difference when using the LSS100100. :(

Hi, 

Are there any new solutions you can share? I still cannot update 4 of my devices. They give the same error as described in the main post. It worked fine previously, but not anymore. I have updated everything. I have tried using LSS100100 and via the IP interface, but I get the same error. I have not yet tried using USB interface. 

For me a restart of the whole system worked. In other words cutting the power supply

Thank you for your response. Unfortunately, I have already tried that several times. In addition, I have also completely deleted the component, created it anew, changed the address, etc. I have done multiple reinstallations and updated eConfigure Lite, which I use as the tool. All other components update just fine, but these four MTN6710-0004 components time out. I see that some of you have upgraded to a new/larger power supply. I have not tested that, but I don’t understand why it would suddenly be necessary. It’s very frustrating when almost everything has been tested

Hi Hans,

in my case I had unfortunately not set the settings on the KNX line couplers for the main and secondary lines correctly. After I set everything there to pass-through/forwarding everything worked normally again. I hope that solves your problem.