Connection lost and not restored by Lutron binding

Add-ons Bindings
1

Hello
I am using the Lutron OH2 Binding with OpenHab 2.5.4
The problem I am experiencing is that OH sometimes loses connection to the Lutron Gulliver processor for whatever reason (which is hard to investigate as this is happening very seldom and upredictably), and is it not restored.

In the portion of OH log below I can see that OH has been started at 16:22 and the Lutron binding has worked fine. Then, at 16:36 the connection is lost suddenly:

2020-12-15 16:22:13.547 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'lutron:dimmer:01F57DEB:267' to inbox.
2020-12-15 16:22:13.551 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'lutron:dimmer:01F57DEB:266' to inbox.
2020-12-15 16:22:13.555 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'lutron:pico:01F57DEB:371' to inbox.
2020-12-15 16:22:13.559 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'lutron:switch:01F57DEB:372' to inbox.
2020-12-15 16:22:13.562 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'lutron:switch:01F57DEB:95' to inbox.
2020-12-15 16:22:13.566 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'lutron:switch:01F57DEB:138' to inbox.
2020-12-15 16:22:13.570 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'lutron:switch:01F57DEB:137' to inbox.
2020-12-15 16:22:13.575 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'lutron:timeclock:01F57DEB:1' to inbox.
2020-12-15 16:22:13.579 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'lutron:timeclock:01F57DEB:2' to inbox.
2020-12-15 16:22:13.583 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'lutron:timeclock:01F57DEB:3' to inbox.
2020-12-15 16:22:13.587 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'lutron:timeclock:01F57DEB:0' to inbox.
2020-12-15 16:22:13.591 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'lutron:greenmode:01F57DEB:6' to inbox.
2020-12-15 16:36:36.987 [WARN ] [ron.internal.handler.IPBridgeHandler] - Communication error, will try to reconnect. Error: Could not write to stream
2020-12-15 16:36:37.025 [WARN ] [ron.internal.handler.IPBridgeHandler] - Error disconnecting: Socket closed

This has happened few times in one month.
I may accept that the telnet connection may break, but why it is not eventually re-established? The Lutron things remain offline forever until eventually I restart the OH altogether.

I have looked into the binding source code and I can see that, when an exception is thrown on OH sending data to the Lutron processor, it is caught and then a reconnect() is called.
But it does not succeed.

I would like to know

  • what is the best way to investigate and find why the connection is not re-established;
  • if there is a way (any way) to ensure that the connection is eventually re-established.

I have seen that there is a similar issue in another post but the thread has drifted out of topic and is quite old, so I am starting a new thread here.

Thank you for any suggestion!

Alberto

2

It should reconnect unless there is something that is prevent it from doing so. By default ipbridge will try to reconnect every 5 minutes, unless you have changed the value of the reconnect parameter. Try enabling DEBUG or TRACE logging for the the binding (org.openhab.binding.lutron) and it will give you more info about what is going on.