OH1: KNX and HUE are interfering with each other and cause problems

Setup, Configuration and Use Installation
,
1
  • Platform information: Win10 64bit / 32GB RAM / intel Z270 / M2e SSD
    • Java Runtime Environment: 1.8.0_152
    • openHAB version: 1.8.3
    • Hue Binding version: 1.11.0
    • KNX Binding version: 1.11.0

Dear all

since I see from time to time problems with my Hue bulbs (switching on/off without any commands) I was looking for the root cause. In my log file I see a lot of entries which seems to be caused by an interferring problem between Hue and KNX binding.

2017-11-25 18:44:11.955 [INFO ] [b.k.i.connection.KNXConnection] - Established connection to KNX bus on 192.168.0.2:3671 in mode TUNNEL.
2017-11-25 18:44:11.976 [INFO ] [b.k.i.connection.KNXConnection] - Connected to KNX
2017-11-25 18:46:07.482 [WARN ] [.h.internal.hardware.HueBridge] - Failed to connect to Hue bridge: HTTP request timed out.
2017-11-25 18:46:07.482 [WARN ] [inding.hue.internal.HueBinding] - Hue settings were null, maybe misconfigured bridge IP.
2017-11-25 18:46:10.928 [WARN ] [b.k.i.connection.KNXConnection] - KNX link has been lost (reason: server request on object tunneling link link (closed) 192.168.0.2:3671 TP1 medium, device 0.0.0, hopcount 6)
2017-11-25 18:46:10.930 [INFO ] [b.k.i.connection.KNXConnection] - KNX link will be retried in 30 seconds
2017-11-25 18:46:10.932 [ERROR] [.b.knx.internal.bus.KNXBinding] - Received detach Event.
2017-11-25 18:46:17.494 [WARN ] [.h.internal.hardware.HueBridge] - Failed to connect to Hue bridge: HTTP request timed out.
2017-11-25 18:46:17.494 [WARN ] [inding.hue.internal.HueBinding] - Hue settings were null, maybe misconfigured bridge IP.
2017-11-25 18:46:40.934 [INFO ] [b.k.i.connection.KNXConnection] - Trying to (re-)connect to KNX...
2017-11-25 18:46:40.939 [INFO ] [b.k.i.connection.KNXConnection] - Established connection to KNX bus on 192.168.0.2:3671 in mode TUNNEL.
2017-11-25 18:46:40.960 [INFO ] [b.k.i.connection.KNXConnection] - Connected to KNX
2017-11-25 18:48:34.926 [WARN ] [b.k.i.connection.KNXConnection] - KNX link has been lost (reason: server request on object tunneling link link (closed) 192.168.0.2:3671 TP1 medium, device 0.0.0, hopcount 6)
2017-11-25 18:48:34.928 [INFO ] [b.k.i.connection.KNXConnection] - KNX link will be retried in 30 seconds
2017-11-25 18:48:34.931 [ERROR] [.b.knx.internal.bus.KNXBinding] - Received detach Event.
2017-11-25 18:48:43.220 [WARN ] [.h.internal.hardware.HueBridge] - Failed to connect to Hue bridge: HTTP request timed out.
2017-11-25 18:48:43.220 [WARN ] [inding.hue.internal.HueBinding] - Hue settings were null, maybe misconfigured bridge IP.
2017-11-25 18:48:58.222 [WARN ] [.h.internal.hardware.HueBridge] - Failed to connect to Hue bridge: HTTP request timed out.
2017-11-25 18:48:58.222 [WARN ] [inding.hue.internal.HueBinding] - Hue settings were null, maybe misconfigured bridge IP.
2017-11-25 18:49:04.930 [INFO ] [b.k.i.connection.KNXConnection] - Trying to (re-)connect to KNX...
2017-11-25 18:49:08.234 [WARN ] [.h.internal.hardware.HueBridge] - Failed to connect to Hue bridge: HTTP request timed out.
2017-11-25 18:49:08.234 [WARN ] [inding.hue.internal.HueBinding] - Hue settings were null, maybe misconfigured bridge IP.
2017-11-25 18:49:14.931 [ERROR] [b.k.i.connection.KNXConnection] - Error connecting to KNX bus: timeout connecting to control endpoint /192.168.0.2:3671
2017-11-25 18:49:14.931 [ERROR] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.0.2:3671: establishing connection failed, timeout connecting to control endpoint /192.168.0.2:3671
2017-11-25 18:49:14.931 [INFO ] [b.k.i.connection.KNXConnection] - KNX link will be retried in 30 seconds
2017-11-25 18:49:34.930 [INFO ] [b.k.i.connection.KNXConnection] - Trying to (re-)connect to KNX...
2017-11-25 18:49:34.933 [INFO ] [b.k.i.connection.KNXConnection] - Established connection to KNX bus on 192.168.0.2:3671 in mode TUNNEL.
2017-11-25 18:49:34.953 [INFO ] [b.k.i.connection.KNXConnection] - Connected to KNX
2017-11-25 18:51:30.856 [WARN ] [b.k.i.connection.KNXConnection] - KNX link has been lost (reason: server request on object tunneling link link (closed) 192.168.0.2:3671 TP1 medium, device 0.0.0, hopcount 6)
2017-11-25 18:51:30.856 [INFO ] [b.k.i.connection.KNXConnection] - KNX link will be retried in 30 seconds
2017-11-25 18:51:30.858 [ERROR] [.b.knx.internal.bus.KNXBinding] - Received detach Event.
2017-11-25 18:51:33.915 [WARN ] [.h.internal.hardware.HueBridge] - Failed to connect to Hue bridge: HTTP request timed out.
2017-11-25 18:51:33.915 [WARN ] [inding.hue.internal.HueBinding] - Hue settings were null, maybe misconfigured bridge IP.
2017-11-25 18:51:48.917 [WARN ] [.h.internal.hardware.HueBridge] - Failed to connect to Hue bridge: HTTP request timed out.
2017-11-25 18:51:48.917 [WARN ] [inding.hue.internal.HueBinding] - Hue settings were null, maybe misconfigured bridge IP.
2017-11-25 18:51:58.929 [WARN ] [.h.internal.hardware.HueBridge] - Failed to connect to Hue bridge: HTTP request timed out.
2017-11-25 18:51:58.929 [WARN ] [inding.hue.internal.HueBinding] - Hue settings were null, maybe misconfigured bridge IP.
2017-11-25 18:52:00.858 [INFO ] [b.k.i.connection.KNXConnection] - Trying to (re-)connect to KNX...

Regarding HUE:
I checked config, the pairing is done, it receives commands and reacts on it (with problems as described above).

Regarding KNX:
I tried to use ROUTER instead of TUNNEL, it is connecting but then I see a lot of other errors and KNX is not reacting anymore when it gets commands via OH.

2017-11-25 18:31:30.408 [WARN ] [.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'Heiz_EG_WZ_Status_Stellwert' from KNX bus: timeout waiting for group read response: timeout
2017-11-25 18:31:30.408 [WARN ] [.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address '1/2/14' = '2'
2017-11-25 18:31:40.460 [WARN ] [.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'Fassade2_Nachtschliessen_Status' from KNX bus: timeout waiting for group read response: timeout
2017-11-25 18:31:40.460 [WARN ] [.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address '6/1/23' = '2'
2017-11-25 18:31:50.512 [WARN ] [.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'Bus_Busverkehr_Ueberwachung_Maximaler_Busverkehr' from KNX bus: timeout waiting for group read response: timeout
2017-11-25 18:31:50.513 [WARN ] [.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address '0/0/18' = '2'
2017-11-25 18:32:00.564 [WARN ] [.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'Sicherung_F13_Strommessung' from KNX bus: timeout waiting for group read response: timeout
2017-11-25 18:32:00.564 [WARN ] [.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address '4/1/13' = '2'
2017-11-25 18:32:10.616 [WARN ] [.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'Fassade1_Sonnenauto_Hellig_Kurz_Status' from KNX bus: timeout waiting for group read response: timeout
2017-11-25 18:32:10.616 [WARN ] [.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address '6/0/48' = '2'

As a side effect I see very often a network adapter disconnect when the problems above appear.

Can you please help me to resolve this problems or at least find out what the root causes are?

Thanks & Regards
John

2

Getting a debug log would be helpful. Also, have you examined the config settings for each binding to see if you’ve defined the same address in both bindings?

You should probably verify that each binding runs properly when the other is NOT running.

3

this could be your root-cause… maybe a faulty NIC (Network Interface Card) on your Win10 host or some other network related hardware/config problem (like patch cord, switch, etc). Check the network stuff also.

4

I have strage observation:

  • OH is running on a machine in my house technic room, let’s call this machins “HOMECENTRAL”
  • I have another machine running in my office, let’s call it “JOHN”

When JOHN is not running HOMECENTRAL has no problems at all. No errors appear, neither for HUE nor for KNX.

As soon as JOHN starts the above mentioned errors appear.

Any ideas how I can find out why my office machine is bothering HOMECENTRAL?

Thanks & Regards
John

5

IP Address conflict (most likely)
are you using static IPs?

6

HOMECENTRAL = static = 192.168.0.13
JOHN = via dhcp = 192.168.0.38

Seems not to be a conflict, right?

7

what is the IP of the KNX gateway? (or the HUE bridge?)

8

HUE Bridge (Square): 192.168.0.4 (static)

KNX Gateway: 192.168.0.2 (static)