Astro Binding has problems with trigger

Hi,

since three days I have a strange behaviour of the Astro Binding. It worked for 2 weeks after a complete fresh install of Openhabian with OH 2.1. I am using te Astro Binding to control rollershutters, closing them 10 minutes before CivilDusk triggers “end”. Again, this worked flawless with OH2 and again 2 weeks with OH2.1.
Now today I had the following errors in the log

[Code]
==> /var/log/openhab2/openhab.log <==
2017-07-10 21:54:32.767 [ERROR] [lfe.hap.impl.http.impl.BinaryHandler] - Exception in binary handler
java.io.IOException: Connection timed out
at sun.nio.ch.FileDispatcherImpl.read0(Native Method)[:1.8.0_121]
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)[:1.8.0_121]
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)[:1.8.0_121]
at sun.nio.ch.IOUtil.read(IOUtil.java:192)[:1.8.0_121]
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)[:1.8.0_121]
at io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:447)[214:org.openhab.io.homekit:2.1.0]
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:880)[214:org.openhab.io.homekit:2.1.0]
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:242)[214:org.openhab.io.homekit:2.1.0]
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119)[214:org.openhab.io.homekit:2.1.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)[214:org.openhab.io.homekit:2.1.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)[214:org.openhab.io.homekit:2.1.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)[214:org.openhab.io.homekit:2.1.0]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)[214:org.openhab.io.homekit:2.1.0]
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)[214:org.openhab.io.homekit:2.1.0]
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)[214:org.openhab.io.homekit:2.1.0]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
2017-07-10 21:54:32.774 [ERROR] [.hap.impl.http.impl.AccessoryHandler] - Exception caught in web handler
java.io.IOException: Connection timed out
at sun.nio.ch.FileDispatcherImpl.read0(Native Method)[:1.8.0_121]
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)[:1.8.0_121]
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)[:1.8.0_121]
at sun.nio.ch.IOUtil.read(IOUtil.java:192)[:1.8.0_121]
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)[:1.8.0_121]
at io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:447)[214:org.openhab.io.homekit:2.1.0]
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:880)[214:org.openhab.io.homekit:2.1.0]
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:242)[214:org.openhab.io.homekit:2.1.0]
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119)[214:org.openhab.io.homekit:2.1.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)[214:org.openhab.io.homekit:2.1.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)[214:org.openhab.io.homekit:2.1.0]
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)[214:org.openhab.io.homekit:2.1.0]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)[214:org.openhab.io.homekit:2.1.0]
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)[214:org.openhab.io.homekit:2.1.0]
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)[214:org.openhab.io.homekit:2.1.0]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
==> /var/log/openhab2/events.log <==
2017-07-10 21:54:54.274 [ItemStateChangedEvent ] - Currenttime changed from 2017-07-10T21:53:54.241+0200 to 2017-07-10T21:54:54.241+0200
2017-07-10

[Code]

It seems, for whatever reason the trigger of the Binding causes a crash. Any ideas ?

Thanks a lot
Cu
Frank

Hi. I probably have the same issue, at least same behavior. Did you find a solution for the problem?

It has been stated in annother post that the astro binding in 2.1 is buggy. So either upgrade to unstable 2.2 or wait for stable 2.2 or just copy the astrobinding.jar file from the 2.2 unstable to your system

Ok… Thanks for the information, then I know what has to be done… I guess this bug is fixed in 2.2?