search

eclipse-archived / smarthome

Eclipse SmartHome™ project
https://www.eclipse.org/smarthome/
Eclipse Public License 2.0
865 stars 782 forks source link

[homematic] new parameter "bindAddress" broken #6762

Closed oliverrahner closed 5 years ago

oliverrahner commented 5 years ago

For me, the newly introduced parameter "bindAddress" (#6547, #6716) does not work. Even worse, the "old" behaviour where gatewayAddress was also used as the address to bind to doesn't work anymore.

My setup is openHABian running on latest snapshot. I have two interfaces: Wifi on 192.168.178.41, Ethernet on 192.168.178.8.

This is the log:

10:15:23.918 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'homematic:bridge:2af8774a' changed from UNINITIALIZED (DISABLED) to INITIALIZING
10:15:23.920 [DEBUG] [ematic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.36,callbackHost=192.168.178.8,bindAddress=192.168.178.8,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,groupPort=9292,timeout=15,discoveryTimeToLive=-

Looks ok, but the result is:

# netstat -tulpen | grep 9125
tcp6       0      0 192.168.178.41:9125     :::*                    LISTEN      1000       2470746    11633/java

Any additional logs I could provide to solve this? I know I can always disable Wifi and everything should work, but I wouldn't find these race conditions then ;)

oliverrahner commented 5 years ago

After some weeks and several updates I tried reproducing this issue. It seems fixed now!

openHAB 2.5.0 Build #1507