Keba binding (suddenly) does not work

Hi there,

my Keba binding stopped working properly and I am somewhat lost what the reason is:
I am running OH3.4.0 on docker with the built in Keba binding. My Box is a P30 x-series that used to work with the binding. The log says the following:

17:26:41.452 [DEBUG] [eba.internal.handler.KeContactHandler] - Running pollingRunnable to connect Keba wallbox
17:26:41.832 [DEBUG] [eba.internal.handler.KeContactHandler] - isKebaReachable() returns true
17:26:41.876 [DEBUG] [internal.handler.KeContactTransceiver] - Sending ‘report 1’ on the channel ‘/192.168.17.1:59559’->‘/192.168.17.27:7090’
17:26:44.833 [DEBUG] [eba.internal.handler.KeContactHandler] - Missing response from Keba station for ‘report 1’
17:26:47.917 [DEBUG] [internal.handler.KeContactTransceiver] - Sending ‘report 2’ on the channel ‘/192.168.17.1:59559’->‘/192.168.17.27:7090’
17:26:50.835 [DEBUG] [eba.internal.handler.KeContactHandler] - Missing response from Keba station for ‘report 2’
17:26:53.924 [DEBUG] [internal.handler.KeContactTransceiver] - Sending ‘report 3’ on the channel ‘/192.168.17.1:59559’->‘/192.168.17.27:7090’
17:26:56.836 [DEBUG] [eba.internal.handler.KeContactHandler] - Missing response from Keba station for ‘report 3’
17:27:11.836 [DEBUG] [eba.internal.handler.KeContactHandler] - Running pollingRunnable to connect Keba wallbox
17:27:12.033 [DEBUG] [eba.internal.handler.KeContactHandler] - isKebaReachable() returns true
17:27:12.033 [TRACE] [internal.handler.KeContactTransceiver] - OH-thingHandler-3 waiting on handerLock java.util.concurrent.locks.ReentrantLock@f745119[Locked by thread OH-thingHandler-3]
17:27:12.043 [DEBUG] [internal.handler.KeContactTransceiver] - Sending ‘report 1’ on the channel ‘/192.168.17.1:59559’->‘/192.168.17.27:7090’
17:27:15.034 [DEBUG] [eba.internal.handler.KeContactHandler] - Missing response from Keba station for ‘report 1’
17:27:18.035 [TRACE] [internal.handler.KeContactTransceiver] - OH-thingHandler-3 waiting on handerLock java.util.concurrent.locks.ReentrantLock@f745119[Locked by thread OH-thingHandler-3]
17:27:18.083 [DEBUG] [internal.handler.KeContactTransceiver] - Sending ‘report 2’ on the channel ‘/192.168.17.1:59559’->‘/192.168.17.27:7090’
17:27:21.036 [DEBUG] [eba.internal.handler.KeContactHandler] - Missing response from Keba station for ‘report 2’
17:27:24.037 [TRACE] [internal.handler.KeContactTransceiver] - OH-thingHandler-3 waiting on handerLock java.util.concurrent.locks.ReentrantLock@f745119[Locked by thread OH-thingHandler-3]
17:27:24.090 [DEBUG] [internal.handler.KeContactTransceiver] - Sending ‘report 3’ on the channel ‘/192.168.17.1:59559’->‘/192.168.17.27:7090’
17:27:27.037 [DEBUG] [eba.internal.handler.KeContactHandler] - Missing response from Keba station for ‘report 3’
17:27:42.038 [DEBUG] [eba.internal.handler.KeContactHandler] - Running pollingRunnable to connect Keba wallbox

I did not change the configuration of the box which runs the latest firmware (1.14.1). Also the mobile Keba-App does connect to the box and shows data. OH, Box and mobile are connected to the same network.

Scanning for the UDP port to be online with entering the following on the OH host

sudo nmap -sU -Pn -p 7090 192.168.17.27

shows

PORT STATE SERVICE
7090/udp open|filtered unknown
MAC Address: 84:71:27:0D:C9:65 (Silicon Laboratories)
Nmap done: 1 IP address (1 host up) scanned in 1.37 seconds

I already rebootet the box and the OH host (Ubuntu).
I can not exactly say what has changed since the last time it worked. I did upgrade to OH3.4 (from OH3.4.M6) and upgraded the host for OH to Ubuntu 22.04 (from 20.04).
In general my box is quite slow. Initial idea is to increase the timeout but I haven’t found a setting that would allow for this.

Thanks for any idea how I can investigate further or give the extended timeout a try.

Solution: this turned out to be a firewall issue after upgrading to Ubuntu 22.04.

Would it be possible that you describe a bit more in detail what the exact firewall issue was?

I face the same issue with the same log messages since a OpenHAB upgrade.

My issues had nothing to do with OH. Instead, I discovered a messed firewall setup in firewalld and iptables. The iptables setup was a leftover from previous installations and interfered with firewalld in a way that settings did not work.