[SIlverCrest Wifi Binding] Aldi Plugs stay Offline

Hi,
I have a problem with the Silvercrest Wifi Binding using ALDI Plugs.

My setup has been running for quite a while using two Plugs. In the beginning I used an bash script via exec to turn them on/off, but with the recent update of the SilverCrest Binding, the ALDI Plugs were discovered (yay). The great thing about this is, that openHAB gets informed by the Plugs if they are turned on or off.

I recently got another Wifi Plug and added it via the paper UI. The first thing I noticed was that the Plug was not discovered automatically. So I added it manually (using MAC address, IP address and correct type).
As of that moment, all three Wifi Plugs now show “Offline” in OpenHAB. I can switch them on/off as always, but the status is not being pulled from the Plugs (it now works the same way as it did with my exec-command).

I tried removing and reinstalling the devices, the binding and openHAB.
To make sure that I was not causing problems with my configuration, I used an empty configuration in openHAB, just installed the binding and adding the Plugs.

I turned on DEBUG logging for the SilverCrest Binding and it shows the following:

==> /var/log/openhab2/openhab.log <==

2018-02-08 15:54:57.262 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Begin of Socket keep alive thread routine. Current configuration update interval: 60 seconds.

2018-02-08 15:54:57.268 [DEBUG] [handler.SilvercrestWifiSocketHandler] - It has been passed 1518101697 seconds since the last update on socket with mac address 009569A640D0.

2018-02-08 15:54:57.273 [DEBUG] [handler.SilvercrestWifiSocketHandler] - No updates have been received for a long time, search the mac address 009569A640D0 in network...

2018-02-08 15:54:57.278 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Will query for device with mac address 009569A640D0 in network with broadcast address /192.168.100.255

2018-02-08 15:54:57.283 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Sent packet to address: /192.168.100.255 and port 8530

2018-02-08 15:54:57.283 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - Received packet from: 192.168.100.2. Will process the packet...

2018-02-08 15:54:57.289 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - The message received is not one response. Probably the message received is one broadcast message looking for the socket.

2018-02-08 15:54:57.294 [DEBUG] [handler.SilvercrestWifiSocketHandler] - No updates have been received for a long long time will put the thing with mac address 009569A640D0 OFFLINE.

2018-02-08 15:54:57.299 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Send command for mac addr: 009569A640D0 with type: GPIO_STATUS with hostaddress: 192.168.100.252

2018-02-08 15:54:57.304 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Sent packet to address: /192.168.100.252 and port 8530

2018-02-08 15:54:57.316 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - Received packet from: 192.168.100.252. Will process the packet...

2018-02-08 15:54:57.320 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - The message received is not one response. Probably the message received is one broadcast message looking for the socket.

2018-02-08 15:54:57.323 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - Received packet from: 192.168.100.252. Will process the packet...

2018-02-08 15:54:57.327 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - The message received is not one response. Probably the message received is one broadcast message looking for the socket.

2018-02-08 15:54:57.333 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Begin of Socket keep alive thread routine. Current configuration update interval: 60 seconds.

2018-02-08 15:54:57.338 [DEBUG] [handler.SilvercrestWifiSocketHandler] - It has been passed 1518101697 seconds since the last update on socket with mac address 009569A6907C.

2018-02-08 15:54:57.341 [DEBUG] [handler.SilvercrestWifiSocketHandler] - No updates have been received for a long time, search the mac address 009569A6907C in network...

2018-02-08 15:54:57.347 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Will query for device with mac address 009569A6907C in network with broadcast address /192.168.100.255

2018-02-08 15:54:57.350 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Sent packet to address: /192.168.100.255 and port 8530

2018-02-08 15:54:57.350 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - Received packet from: 192.168.100.2. Will process the packet...

2018-02-08 15:54:57.353 [DEBUG] [handler.SilvercrestWifiSocketHandler] - No updates have been received for a long long time will put the thing with mac address 009569A6907C OFFLINE.

2018-02-08 15:54:57.355 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - The message received is not one response. Probably the message received is one broadcast message looking for the socket.

2018-02-08 15:54:57.358 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Send command for mac addr: 009569A6907C with type: GPIO_STATUS with hostaddress: 192.168.100.251

2018-02-08 15:54:57.362 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Sent packet to address: /192.168.100.251 and port 8530

2018-02-08 15:54:57.416 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Begin of Socket keep alive thread routine. Current configuration update interval: 60 seconds.

2018-02-08 15:54:57.418 [DEBUG] [handler.SilvercrestWifiSocketHandler] - It has been passed 1518101697 seconds since the last update on socket with mac address 009569A636F8.

2018-02-08 15:54:57.420 [DEBUG] [handler.SilvercrestWifiSocketHandler] - No updates have been received for a long time, search the mac address 009569A636F8 in network...

2018-02-08 15:54:57.422 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Will query for device with mac address 009569A636F8 in network with broadcast address /192.168.100.255

2018-02-08 15:54:57.425 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - Received packet from: 192.168.100.2. Will process the packet...

2018-02-08 15:54:57.425 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Sent packet to address: /192.168.100.255 and port 8530

2018-02-08 15:54:57.426 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - The message received is not one response. Probably the message received is one broadcast message looking for the socket.

2018-02-08 15:54:57.426 [DEBUG] [handler.SilvercrestWifiSocketHandler] - No updates have been received for a long long time will put the thing with mac address 009569A636F8 OFFLINE.

2018-02-08 15:54:57.429 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Send command for mac addr: 009569A636F8 with type: GPIO_STATUS with hostaddress: 192.168.100.253

2018-02-08 15:54:57.434 [DEBUG] [handler.SilvercrestWifiSocketHandler] - Sent packet to address: /192.168.100.253 and port 8530

2018-02-08 15:54:57.526 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - Received packet from: 192.168.100.253. Will process the packet...

2018-02-08 15:54:57.529 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - The message received is not one response. Probably the message received is one broadcast message looking for the socket.

2018-02-08 15:54:57.532 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - Received packet from: 192.168.100.253. Will process the packet...

2018-02-08 15:54:57.535 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - The message received is not one response. Probably the message received is one broadcast message looking for the socket.

My environment:
openHAB 2.2 (latest) on raspbian running on raspberry pi
IP addresses:
192.168.100.2 rasbperry
192.168.100.251 WiFiPlug-1
192.168.100.251 WiFiPlug-2
192.168.100.251 WiFiPlug-3

The part showing that the binding has not recieved an update in 1518101697 seconds is making me think that there is a time problem somewhere, but the raspberry pi gets the time from an NTP and I could not find any NTP setting on the Aldi Plugs…

Does anyone have an idea how I could continue troubleshooting this?

I’ve installed a fresh openHAB on a spare raspberry pi and the issue is the same. I have only added the silvercrest binding, and enabled debug logging. This shows up in the logs:

2018-02-09 18:40:53.315 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - Received packet from: 192.168.100.251. Will process the packet...
2018-02-09 18:40:53.318 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - The message received is not one response. Probably the message received is one broadcast message looking for the socket.
2018-02-09 18:41:24.361 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - Received packet from: 192.168.100.2. Will process the packet...
2018-02-09 18:41:24.365 [DEBUG] [restWifiSocketUpdateReceiverRunnable] - The message received is not one response. Probably the message received is one broadcast message looking for the socket.

<etc>

The message is triggered everytime my “normal” openHAB (192.168.100.2) checks for an update or the plugs send the update (when I press the button on the plug, the message appears immediately with the plug’s IP address).
It seems like the data cannot be read from the UDP packets sent by the plugs. The Android app works fine for all three so it is unlikely that the problem is with the plugs. I also checked that the firmware has not changed from when I bought them.

Not sure where to look next.

I’ve created an issue on github where I will continue:
https://github.com/openhab/openhab2-addons/issues/3229