Support for Hörmann garage doors

Slawomir_Ksiazek · January 22, 2020, 5:55pm

Hi Thomas,
New version of binding from today seems that is more stable, i need to couple of days to verify situation
and to do more tests, anyway I will wait new functions, especially status of gate, would you please share roadmap of development ?
Thank you for your contribution here
Slawek

thomas_letsch_de · January 23, 2020, 7:12am

Hi Slawomir,

ohh, there won’t be any timeline, roadmap, deadline etc. I have that in my work, but this is my free time project

The status of the gate is already usable in OH, the gate item is of type Rollershutter. You can see how much open it is and you can send OPEN / CLOSE and STOP commands to it.

Getting this done was most important for me and at the moment everything I need. So there are no further plans other then making the binding more and more stable.

Regards,
Thomas

Slawomir_Ksiazek · January 23, 2020, 4:53pm

Hi Thomas

Many thanks for everything you do here in scope of this binding for Hormann garage doors, I’m really appreciate
Slawek

copystring · January 24, 2020, 7:47pm

@thomas_letsch_de
Reinstalled openhab and installed your addon again. It works just fine now.
Now I am trying to get this to be controlled/viewed via mqtt.

thomas_letsch_de · February 11, 2020, 8:32am

Just a note of warning:
My long term tests showed that using the current version of the BiSecure Addon will get your openhab instance stuck.
There seems to be a problem with threads not getting removed and in my case renders the OH instance unusable after a few days

I will drop a note when a fix is available

thomas_letsch_de · February 13, 2020, 9:16am

The new version looks good so far. I encourage every tester to download the actual version and use it instead of the old one

cinadr · February 22, 2020, 3:42pm

Hi Thomas,

I’ve downloaded your newest binding and testing it for a while. It works with my two gate setup quite well.
I noticed that quick open - close sequence of my garage door isn’t noticed by the binding. Is there a polling interval that could be set for quicker refresh?

Thanks,
Cina.

P.S.: I thank you very much for your effort.

Bize · February 22, 2020, 9:32pm

Hello!

Same for me, by chance I just found the HmIP-MOD-HO module for Hörmann garage door drives. It would fit to my garage door drive according to the description.

Is there anyone here with experience in integration this to OH2 ?

Thanks!

Mhgglmmr · February 22, 2020, 10:06pm

Maybe this tutorial helps

thomas_letsch_de · March 2, 2020, 2:54pm

Hi Cina,

the polling interval is currently fixed to 30 sec, but if a command (UP / DOWN) is applied it changes to 4 sec until the door is in its final position again.

My tests showed that a status query normally (99%) takes less than 1 sec so we could easily lower the interval and make it configurable.

It could take some time to get a new version out, but I’ll keep that in the queue.

Regards,
Thomas

cinadr · March 2, 2020, 3:18pm

Hi Thomas,

Is the 4sec is true when the gates are opened by external way (e.g. by remote) ? It would be useful also.
I think the 4sec polling should last for 3-5 minutes after the final position reached and will last if the gate stopped in middle until closed/opened fully?

Edit: Please add some options in the gateway config:
Polling timings

Idle: [30 sec - default] {Polling interval of the gateway while a gate is fully closed or opened}
Active: [4 sec - default] {Polling interval of the gateway while a gate is closing or opening}
Opened timeout: [300 sec - default] {Return to idle polling after this time if gate is fully opened}
Closed timeout: [30 sec - default] {Return to idle polling after this time if gate is fully closed}
Active while unclosed [true - default] {Keep the active polling interval if the gate is not moving but not fully closed or opened}

These are just practical ideas. The gate/door much likely to get closed after an opening event so the quicker polling should be turned on for a longer period of a time - but after closing the gate it is more unlikely to be opened again in a short time period so we can turn off quick polling sooner. This may vary on different usage scenarios so the user should be able to decide the optimal settings here.

Thank you again for your hard work. Any support for you is possible somewhere (patreon or else)?

Best regs,
Zsolt.

cinadr · March 4, 2020, 8:14pm

Hi Thomas!

I found that the binding in 2.5.3-SNAPSHOT (and with 2.5.2 RELEASE as well) is behaving strangely. I’ve got high CPU usage which is slowly getting higher and higher. I switched to DEBUG bisecur binding and I found that it fires a lot of exceptions: (I’ve cleaned the cache and tmp folders already and it is repeating)

2020-03-04 21:02:50.115 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.115 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.

Here is the DEBUG log of the problem starting:

2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received Exception Timeout waiting for PackageReceived (after waiting 3000 ms) (which probably comes from a timeout while reading). This happens after a while (about 2min), the GW just stops responding => retrying…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reconnecting
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Connecting…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received Exception Timeout waiting for PackageReceived (after waiting 3000 ms) (which probably comes from a timeout while reading). This happens after a while (about 2min), the GW just stops responding => retrying…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Connected
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reconnecting
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Connecting…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Sending package command: Command(code=16 (10), name=‘LOGIN’), tag: 20, token: 00000000, payload: 076F70656E6861626861626F70656E, isResponse=false, checksum=-23
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilEmptyQueue
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilEmptyQueue finished
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilMessageProcessed
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Connected
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Sending package command: Command(code=16 (10), name=‘LOGIN’), tag: 21, token: 00000000, payload: 076F70656E6861626861626F70656E, isResponse=false, checksum=-23
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilEmptyQueue
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilEmptyQueue finished
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilMessageProcessed
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-04 21:02:50.097 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received exception while waiting for bytes: java.io.IOException: Stream closed.

I’ve managed to get TRACE logs from console. I’ve found that 6-8 threads of the bisdk is running concurrently consuming almost equal CPU time. Here are the <threads --list> output for the relevan threads:

Id Name State CPU time Usr time
3609 Thread-2060 RUNNABLE 26525156 26472828
3670 Thread-2092 RUNNABLE 26332671 26279390
3935 Thread-2258 RUNNABLE 25480812 25431718
3914 Thread-2244 RUNNABLE 25382531 25329718
5485 Thread-3115 RUNNABLE 20380906 20335234
5476 Thread-3109 RUNNABLE 20355078 20301703
5621 Thread-3176 RUNNABLE 20006796 19959968
6759 Thread-3662 RUNNABLE 17414765 17371937
9013 Thread-4644 RUNNABLE 12432515 12399375
12186 Thread-5865 RUNNABLE 6239859 6224281
13064 Thread-6210 RUNNABLE 4739156 4727375
13288 Thread-6298 RUNNABLE 4412906 4401000
13538 Thread-6409 RUNNABLE 4009312 4000156
14558 Thread-6824 RUNNABLE 2614281 2607937
16538 Thread-7588 RUNNABLE 206125 205640

And this is the thread info for some of them. Each listed above had the same stack trace but wiht different thread IDs:

openhab> threads 3609
Thread 3609 Thread-2060 RUNNABLE
Stacktrace:
java.lang.Throwable.fillInStackTrace line: -2
java.lang.Throwable.fillInStackTrace line: 784
java.lang.Throwable. line: 266
java.lang.Exception. line: 66
java.io.IOException. line: 58
java.net.AbstractPlainSocketImpl.available line: 470
java.net.SocketInputStream.available line: 259
java.io.FilterInputStream.available line: 168
org.bisdk.sdk.Receiver.readBytes line: 51
org.bisdk.sdk.Receiver.readAnswer line: 38
org.bisdk.sdk.Receiver.run line: 101
java.lang.Thread.run line: 748

openhab> threads 3670
Thread 3670 Thread-2092 RUNNABLE
Stacktrace:
java.lang.Throwable.fillInStackTrace line: -2
java.lang.Throwable.fillInStackTrace line: 784
java.lang.Throwable. line: 266
java.lang.Exception. line: 66
java.io.IOException. line: 58
java.net.AbstractPlainSocketImpl.available line: 470
java.net.SocketInputStream.available line: 259
java.io.FilterInputStream.available line: 168
org.bisdk.sdk.Receiver.readBytes line: 51
org.bisdk.sdk.Receiver.readAnswer line: 38
org.bisdk.sdk.Receiver.run line: 101
java.lang.Thread.run line: 748

and each are the same from the above list.

Right now I’m testing if this occurs only with both doors active. I’ve disabled one of the doors things in Paper UI. This is stable right now after 8 hours or so. Is there a race condition? I peeped into the souce on the github but I have no ide where is Receiver.run is called from. It looks like the IO exception is thrown back but the code continues waiting for data to be received…

Any idea on that?

Thank you,
Zsolt.

cinadr · March 21, 2020, 8:58am

Hi Thomas!

I’m sorry to inform you about the above situation, that I still has problems with the binding. Only one gate active I have the same errors filling the log files (almost 10 GB of repeated loglines). Can you help me with that? Is there anything more needed to test or explore?

Thanks,
Zsolt.

thomas_letsch_de · March 21, 2020, 10:17am

Hi Zsolt,

I have been quite busy with other things (upgrading my instances to 2.5.x and fighting with problems of bindings after that).

I have investigated the errors in detail and I think I can improve the handling of the IO Exception. There is a new version of the binding underway (with new link since I switched sources to 2.5.3-SNAPSHOT):

Regards,
Thomas

cinadr · March 28, 2020, 1:48pm

Hi Thomas,

I’m really sorry to bother you again. The binding was ok for the last week about CPU usage so the former bug was corrected. Now I have operational issues. I could operate the gates from openhab for several days without issues. Today I wanted to open them but no response. I looked at the logs and I found these a lot repeated:

2020-03-28 13:14:46.762 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Connecting…
2020-03-28 13:14:46.762 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Connecting…
2020-03-28 13:15:13.706 [WARN ] [egateway.internal.BiSdkLoggerAdapter] - Message to be sent, but not authenticated! Ignoring message…
2020-03-28 13:15:13.706 [WARN ] [egateway.internal.BiSdkLoggerAdapter] - Message to be sent, but not authenticated! Ignoring message…
2020-03-28 13:15:13.706 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Waiting for answer with tag 56
2020-03-28 13:15:13.706 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Waiting for answer with tag 55
2020-03-28 13:15:13.706 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilPackageReceived
2020-03-28 13:15:13.706 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilPackageReceived
2020-03-28 13:15:16.753 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received Exception Timeout waiting for PackageReceived (after waiting 3000 ms) (which probably comes from a timeout while reading). This happens after a while (about 2min), the GW just stops responding => retrying…
2020-03-28 13:15:16.753 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received Exception Timeout waiting for PackageReceived (after waiting 3000 ms) (which probably comes from a timeout while reading). This happens after a while (about 2min), the GW just stops responding => retrying…
2020-03-28 13:15:16.753 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reconnecting
2020-03-28 13:15:16.753 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reconnecting

I tried to disable then enable the binding but it says:

Status: UNINITIALIZED - HANDLER_INITIALIZING_ERROR connect timed out

The logs behind:

2020-03-28 13:16:42.124 [DEBUG] [overy.BiSecureDeviceDiscoveryService] - BiSecureDeviceDiscoveryService org.openhab.binding.bisecuregateway.internal.handler.BiSecureGatewayHandler@14e2d8a0
2020-03-28 13:16:42.124 [DEBUG] [ernal.handler.BiSecureGatewayHandler] - Start initializing!
2020-03-28 13:16:42.124 [INFO ] [egateway.internal.BiSdkLoggerAdapter] - Connecting to /192.168.1.3:4000
2020-03-28 13:16:42.140 [DEBUG] [nternal.handler.BiSecureGroupHandler] - Running initializing thread
2020-03-28 13:16:42.140 [WARN ] [ernal.handler.BiSecureGatewayHandler] - GetGroups called, but bridge not ONLINE => ignoring
2020-03-28 13:16:42.140 [DEBUG] [nternal.handler.BiSecureGroupHandler] - Group 0 not found in gateway!
2020-03-28 13:16:42.140 [DEBUG] [nternal.handler.BiSecureGroupHandler] - Running initializing thread
2020-03-28 13:16:42.140 [WARN ] [ernal.handler.BiSecureGatewayHandler] - GetGroups called, but bridge not ONLINE => ignoring
2020-03-28 13:16:42.140 [DEBUG] [nternal.handler.BiSecureGroupHandler] - Group 1 not found in gateway!
2020-03-28 13:16:56.344 [WARN ] [ernal.handler.BiSecureGatewayHandler] - childHandlerDisposed not implemented!
2020-03-28 13:16:59.094 [WARN ] [ernal.handler.BiSecureGatewayHandler] - childHandlerDisposed not implemented!
2020-03-28 13:17:07.641 [DEBUG] [overy.BiSecureDeviceDiscoveryService] - BiSecureDeviceDiscoveryService org.openhab.binding.bisecuregateway.internal.handler.BiSecureGatewayHandler@5d4a1641

While it works with the Android app.

This might be relevant as well:

2020-03-25 01:06:47.676 [WARN ] [egateway.internal.BiSdkLoggerAdapter] - Message to be sent, but not authenticated! Ignoring message…
2020-03-25 01:06:47.676 [WARN ] [egateway.internal.BiSdkLoggerAdapter] - Message to be sent, but not authenticated! Ignoring message…
2020-03-25 01:06:47.676 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Waiting for answer with tag 57
2020-03-25 01:06:47.676 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Waiting for answer with tag 56
2020-03-25 01:06:47.676 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilPackageReceived
2020-03-25 01:06:47.676 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilPackageReceived
2020-03-25 01:06:50.692 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received Exception Timeout waiting for PackageReceived (after waiting 3000 ms) (which probably comes from a timeout while reading). This happens after a while (about 2min), the GW just stops responding => retrying…
2020-03-25 01:06:50.692 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received Exception Timeout waiting for PackageReceived (after waiting 3000 ms) (which probably comes from a timeout while reading). This happens after a while (about 2min), the GW just stops responding => retrying…
2020-03-25 01:06:50.692 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reconnecting
2020-03-25 01:06:50.692 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reconnecting
2020-03-25 01:06:50.692 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Connecting…
2020-03-25 01:06:50.692 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Connecting…
2020-03-25 01:06:50.723 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Stopping receiver thread, we received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-25 01:06:51.707 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Connected
2020-03-25 01:06:51.707 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Sending package command: Command(code=16 (10), name=‘LOGIN’), tag: 58, token: 00000000, payload: 076F70656E6861626861626F70656E, isResponse=false, checksum=-23
2020-03-25 01:06:51.707 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilEmptyQueue
2020-03-25 01:06:51.707 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilEmptyQueue finished
2020-03-25 01:06:51.707 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilMessageProcessed
2020-03-25 01:06:51.707 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reading from socket…
2020-03-25 01:06:51.770 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Sending transport container 0000000000055410EC4FEEB900183A0000000010076F70656E6861626861626F70656E230C
2020-03-25 01:06:51.770 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Sending done
2020-03-25 01:06:51.832 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilMessageProcessed finished
2020-03-25 01:06:56.709 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Stopping receiver thread, we received exception while waiting for bytes: java.io.IOException: Stream closed.
2020-03-25 01:07:17.665 [WARN ] [egateway.internal.BiSdkLoggerAdapter] - Message to be sent, but not authenticated! Ignoring message…
2020-03-25 01:07:17.665 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Waiting for answer with tag 59
2020-03-25 01:07:17.665 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilPackageReceived
2020-03-25 01:07:17.665 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilPackageReceived finished
2020-03-25 01:07:17.665 [INFO ] [egateway.internal.BiSdkLoggerAdapter] - Received Exception Stream closed. => retrying…
2020-03-25 01:07:17.696 [WARN ] [egateway.internal.BiSdkLoggerAdapter] - Message to be sent, but not authenticated! Ignoring message…
2020-03-25 01:07:17.696 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Waiting for answer with tag 60
2020-03-25 01:07:17.696 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilPackageReceived
2020-03-25 01:07:18.180 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Waiting for answer with tag 59
2020-03-25 01:07:18.180 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilPackageReceived
2020-03-25 01:07:20.759 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received Exception Timeout waiting for PackageReceived (after waiting 3000 ms) (which probably comes from a timeout while reading). This happens after a while (about 2min), the GW just stops responding => retrying…
2020-03-25 01:07:20.759 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reconnecting
2020-03-25 01:07:20.759 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Connecting…
2020-03-25 01:07:21.181 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received Exception Timeout waiting for PackageReceived (after waiting 3000 ms) (which probably comes from a timeout while reading). This happens after a while (about 2min), the GW just stops responding => retrying…
2020-03-25 01:07:21.181 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reconnecting
2020-03-25 01:07:21.181 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Connecting…
2020-03-25 01:07:47.669 [WARN ] [egateway.internal.BiSdkLoggerAdapter] - Message to be sent, but not authenticated! Ignoring message…
2020-03-25 01:07:47.669 [WARN ] [egateway.internal.BiSdkLoggerAdapter] - Message to be sent, but not authenticated! Ignoring message…
2020-03-25 01:07:47.669 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Waiting for answer with tag 62
2020-03-25 01:07:47.669 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Waiting for answer with tag 61
2020-03-25 01:07:47.669 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilPackageReceived
2020-03-25 01:07:47.669 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - waitUntilPackageReceived
2020-03-25 01:07:50.731 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received Exception Timeout waiting for PackageReceived (after waiting 3000 ms) (which probably comes from a timeout while reading). This happens after a while (about 2min), the GW just stops responding => retrying…
2020-03-25 01:07:50.731 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Received Exception Timeout waiting for PackageReceived (after waiting 3000 ms) (which probably comes from a timeout while reading). This happens after a while (about 2min), the GW just stops responding => retrying…
2020-03-25 01:07:50.731 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reconnecting
2020-03-25 01:07:50.731 [DEBUG] [egateway.internal.BiSdkLoggerAdapter] - Reconnecting

If you need more with this please contact me. Thank you. And I want to ask again if there is any possibility to support you somehow. Keep safe.

Zsolt.

wellem · August 20, 2020, 7:38pm

Hello,

same Problem on my side. I installed th binding and get the following Error:

UNINITIALIZED - HANDLER_INITIALIZING_ERROR Retry failed: Received Exception Timeout waiting for PackageReceived (after waiting 5000 ms)

Any news about this issue?

wellem · August 20, 2020, 9:01pm

i solved the problem myself. I have forgotten that i had changed the admin password.
After i set the correct password, the error disapeared

cinadr · October 13, 2020, 7:50am

Hi!

Is there any chance of oh3 version of this binding?

Thank you,
Zsolt.

thomas_letsch_de · October 14, 2020, 9:31am

Hi Zsolt,

I’m following the discussions on the dev forum and it actually should be easy to migrate the binding.

Since OH is not yet there, is there any need already for a OH3 version of this binding?

Regards,
Thomas

cinadr · October 14, 2020, 9:55am

Hi Thomas.

There is an OH3 milestone build which contains all the OH 2.5 bindings recompiled. You can find the post here: https://community.openhab.org/t/openhab-3-milestone-builds/106329

I thought of testing it.

Anyway I’m testing your binding in a special setup where I made a dedicated LAN connection between my Windows server and the gateway and turned off any adapter bindings on this NIC only IP4 left on. I specified a separated subnet for the server (192.168.10.1) and the gateway (192.168.10.2) – my LAN is on 192.168.1.1/24 and there is no routing between them. Openhab is installed on this server. I specified this IP (192.168.10.1) for the gateway in your binding. I don’t want to be positive too early but it seems that it is so far so good and there is no errors in the logs.

Before this I set up the gateway and the app by wire following its manual and after that I made a WLAN connection within the Bisecur App. Then I opened the web interface and changed the LAN IP to the above I mentioned (DHCP is turned off for LAN and turned on for WLAN). I think this might be a supposed solution if the binding goes online within openhab-addons. I wiresharked the connection and there were some TCP connection reset while LAN DHCP was left on (every 3 minutes) but after turning DHCP off resets went away and now I have only a few errors of: “Received Exception Receiver got signal to stop -> stopping receiving activities => retrying…”

So I’m pleased with this solution and hope it will work in OH3 as well. All these are based on the last 24 hours of testing so it needs to be observed further. I’ll report back in case of any issues…

Thank you,

Zsolt.