OH 3.4 KNX commands not send to bus but status is retrieved

,
1

Hi all,

I’ve just migrating my installtion to KNX. To connect from my openHAB 3.4 to the KNX Bus I’m using the MDT SCN-IP000.03 interface. The setup of the binding works as expected and the bridge is online:

UID: knx:ip:da8004d231
label: KNX/IP Gateway
thingTypeUID: knx:ip
configuration:
  useNAT: false
  readRetriesLimit: 3
  ipAddress: 192.168.178.136
  autoReconnectPeriod: 60
  localIp: 192.168.178.159
  type: TUNNEL
  localSourceAddr: 0.0.0
  readingPause: 50
  portNumber: 3671
  responseTimeout: 10

Based on the bridge I’ve added a new KNX device which connects to my MDT AKK-0816.03 actor. The device is shown as online:

UID: knx:device:da8004d231:10b9f484c8
label: KNX 8-fach Relais
thingTypeUID: knx:device
configuration:
  pingInterval: 600
  address: 1.1.3
  readInterval: 0
  fetch: true
bridgeUID: knx:ip:da8004d231

Now I’ve added a channel to control and read the status of one of the relais:

channels:
  - id: knx_actor8_c_patio_lights
    channelTypeUID: knx:switch
    label: KNX Terrassenlicht
    description: ""
    configuration:
      ga: 1.001:0/0/1+<0/0/2

The status could be retrieved, but I cannot control the relais from openHAB. I have already monitor the KNX Bus via ETS and could see, that the message is not sent to the Bus from openHAB. The ETS configuration looks as follows:

image
image1224×140 13.9 KB

image

Has anymore any hint for. what I’m doing wrong?

2

Hi,

I don’t see any mistake in the config…

In the meantime, while you wait for your fellow German, our local knx expert to @Udo_Hartmann to see his opinion :slight_smile:

You can try this app

It helped me while setting this up.

give the app the IP of your knx ip interface, then you type the address 0/0/1 and send a command.

Only after you make sure this is good and works (meaning your ip interface controls the light), lets look at the openhab again…

3

Thanks a lot for your advice. I’ve used a different App from the same developer as you suggested and it worked. I can control the relais and I’m retrieving the status feedback. The KNX IP Interface was discovered automativally by the App und I’ve added a switch and set the GA for switching and status. All works as expected. Switching to maunell mode in the App and inserting the correct IP of the gateway, it’s works as well.

Therefore I assume the issue is on openHAB side. In the ETS I can see the traffic:

image
image1299×200 13.6 KB

The 1.1.4 is the physical address of the IP tunnel.

image
image462×642 11.4 KB

4

is that terace light a regular switch, not a dimmer? can you try omit 1.001, just configure it as

ga: 0/0/1+<0/0/2

also try minimal config of the ip bridge, define only

 ipAddress: 192.168.178.136

omit everything else

5

Setting only IP and type to TUNNEL gives following error:

image

The relais should just close the power cycle to lights up the patio. I know the 1.009 prefix is not required, but it is not wrong either. Currently the all components lay on my desk, because I’m in the configuration / learning phase. Is not productive yet.

6

I’ve setup a OH5.1 instance to see if it maybe works in 5.1. It turns out it works on 5.1. Since my OH3.4 instance contains 272 items and the migration attempt a few weeks ago was unsuccessful, I’m wondering if anyone has a patch or something similar that fixes the KNX issue in version OH3.4?

7

your version is very old, can you at least try to upgrade to OH 4.x for now?

8

I can only encourage you to upgrade. Also hesitated a long time using OH 3.4. Then i used the 2-step strategy described by @rlkoshak moving to 4.3 first and then to 5.x. It has been easier than i thought before. Good luck.

9

Thanks all for the support. I will use the migration to configure the system from scratch. Removing unused Rules or test items will clean up my system.

I will close the topic now.

10

Just to add some stupid words :wink: :

I’'m using knx since openHAB 1.0, and while there was a time in early openHAB2 days, where knx was a bit tricky, this is not true since ~ openHAB2.3. I’ve run openHAB3.4 successfully with my knx system.

I don’t see any obvious errors in the configuration either.
The only little thing to improve would be to set fetch to false. The fetch mechanism isn’t useful and can cause problems when using older knx hardware. You will only get some additional info about the device itself, if fetch works correctly.

But as already stated, openHAB 3.4 is outdated and it’s a good idea to setup openHAB5.1 instead.

11

Thanks for your reply. I have tried it with and without fetch. The hardware is brand-new. The setup with openHAB 5 with the exact same configuration is working. Maybe there’s an issue with ETS6 and openHAB 3.4.

12

Jepp, that’s possible, there are some special features that came with ETS6 and I’m still using ETS5…