OH 4.2 SatelModule ETHM-1 exception occurred during writing a message: Broken pipe

Add-ons Bindings
,
1

I was doing my first steps with OH3 and satel module. I was able to connect to ETHM-1 Plus module and communication was working fine. After update to OH4.2 SatelModule binding is not longer working.

2024-07-20 00:40:30.290 [TRACE] [.satel.internal.protocol.SatelModule] - Checking communication thread: true, false
2024-07-20 00:40:30.292 [TRACE] [.satel.internal.protocol.SatelModule] - Command enqueued: Message: command = 7E, payload = 
2024-07-20 00:40:30.292 [DEBUG] [.satel.internal.protocol.SatelModule] - Communication thread started
2024-07-20 00:40:30.294 [INFO ] [.satel.internal.protocol.Ethm1Module] - Connecting to ETHM-1 module at XXXXX
2024-07-20 00:40:30.309 [INFO ] [.satel.internal.protocol.Ethm1Module] - ETHM-1 module connected successfully
2024-07-20 00:40:30.311 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7E, payload = 
2024-07-20 00:40:30.314 [TRACE] [satel.internal.protocol.SatelMessage] - Calculated checksum = D860
2024-07-20 00:40:30.316 [ERROR] [.satel.internal.protocol.SatelModule] - Unexpected exception occurred during writing a message
java.net.SocketException: Broken pipe
	at sun.nio.ch.NioSocketImpl.implWrite(NioSocketImpl.java:425) ~[?:?]
	at sun.nio.ch.NioSocketImpl.write(NioSocketImpl.java:445) ~[?:?]
	at sun.nio.ch.NioSocketImpl$2.write(NioSocketImpl.java:831) ~[?:?]
	at java.net.Socket$SocketOutputStream.write(Socket.java:1035) ~[?:?]
	at java.net.Socket$SocketOutputStream.write(Socket.java:1031) ~[?:?]
	at org.openhab.binding.satel.internal.protocol.SatelModule.writeMessage(SatelModule.java:338) [bundleFile:?]
	at org.openhab.binding.satel.internal.protocol.SatelModule.communicationLoop(SatelModule.java:401) [bundleFile:?]
	at org.openhab.binding.satel.internal.protocol.SatelModule$CommunicationWatchdog$2.run(SatelModule.java:520) [bundleFile:?]
	at java.lang.Thread.run(Thread.java:840) [?:?]
2024-07-20 00:40:30.319 [INFO ] [.satel.internal.protocol.Ethm1Module] - Closing connection to ETHM-1 module
2024-07-20 00:40:30.321 [DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = false, reason = null
2024-07-20 00:40:30.323 [TRACE] [satel.internal.event.EventDispatcher] - Distributing to org.openhab.binding.satel.internal.protocol.Ethm1Module@6b0b5a8f
2024-07-20 00:40:30.325 [TRACE] [satel.internal.event.EventDispatcher] - Distributing to org.openhab.binding.satel.internal.handler.Ethm1BridgeHandler@14b27b6d
2024-07-20 00:40:30.328 [DEBUG] [.satel.internal.protocol.SatelModule] - Communication thread stopped
2024-07-20 00:40:30.951 [DEBUG] [.internal.handler.SatelBridgeHandler] - Disposing bridge handler.
2024-07-20 00:40:30.952 [DEBUG] [.internal.handler.SatelBridgeHandler] - Satel module closed.

I already tried:

  1. remove all things and items, remove binding and install it again
  2. clear cache with sudo openhab-cli clean-cache
  3. reboot
  4. search for solution: all I found about similar issue was that, if I have two binding installed I should remove one. I’m not sure how to check if I have two bindings, in UI I can only see one.
  5. disable/enable bridge
  6. creating new bridge
  7. installed openhabian from scratch (new OS)

nothing helped.

If any of you guys can give me some tip about how to solve this, I will be grateful.

2

Hello Dariusz.
If you’re 100% sure, that there is no other OH instanance running and the binding configuration is OK, the issue may be also caused by ETHM-1 module. It happened to me some time ago, that the module was not accepting any connection at all. I power-cycled the module and it started working again.

3

Turns out, I had some old openhabian instance working on NAS that I completely forgot about. Once I disable it, all issues are gone.

But thank you @druciak for reply!