[SOLVED] Satel binding "Broken pipe (Write failed)"

I installed Satel binding 2.3, but my log says this (looping):

2018-09-23 22:27:43.062 [INFO ] [.satel.internal.protocol.Ethm1Module] - Closing connection to ETHM-1 module
2018-09-23 22:27:44.029 [INFO ] [.satel.internal.protocol.Ethm1Module] - Connecting to ETHM-1 module at
2018-09-23 22:27:44.036 [INFO ] [.satel.internal.protocol.Ethm1Module] - ETHM-1 module connected successfully
2018-09-23 22:27:44.045 [ERROR] [.satel.internal.protocol.SatelModule] - Unexpected exception occurred during writing a message
java.net.SocketException: Broken pipe (Write failed)
        at java.net.SocketOutputStream.socketWrite0(Native Method) ~[?:?]
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111) [?:?]
        at java.net.SocketOutputStream.write(SocketOutputStream.java:134) [?:?]
        at org.openhab.binding.satel.internal.protocol.SatelModule.writeMessage(SatelModule.java:311) [222:org.openhab.binding.satel:2.3.0]
        at org.openhab.binding.satel.internal.protocol.SatelModule.communicationLoop(SatelModule.java:375) [222:org.openhab.binding.satel:2.3.0]
        at org.openhab.binding.satel.internal.protocol.SatelModule.access$1(SatelModule.java:345) [222:org.openhab.binding.satel:2.3.0]
        at org.openhab.binding.satel.internal.protocol.SatelModule$CommunicationWatchdog$2.run(SatelModule.java:480) [222:org.openhab.binding.satel:2.3.0]
        at java.lang.Thread.run(Thread.java:748) [?:?]
2018-09-23 22:27:44.052 [INFO ] [.satel.internal.protocol.Ethm1Module] - Closing connection to ETHM-1 module

I’ve not idea about the origin of problem…

The problem was of satel binding 1.x active on my OH. Now I removed it and I work with 2.3 binding module only

What are you running OH on RPI, Linux Box, Windows?

Also, how did you install OH e.g. openhabian image, manual install …etc

On RPI, manual installation, but now the error is gone.

FYI, sometime when making changes to your system its best to clear the cache and tmp files. This will help prevent errors like above.

I cleaned the cache, but I thought the two bindings could coexist

Sorry for late answer.

They can coexist, but the problem is with ethm-1 module which accepts only one concurrent tcp connection. So if 1.x binding is connected, the other one can not.
This also applies to second OH installation with either version of the binding.

1 Like