Still on OH 1.8.3 now wanting to move to OH3 - mainly struggling on KNX now

Hi there,

had been a long time that i have been active in the forum - as you can see i have a well running 1.8.3 OH instance still running with some bindings in. Now thinking to move to a more current version on OH3.x. I got my Wemo, Daikin, … weather and Astro bindings to run seamlessly - but on KNX - i am really struggling.

Unfortunately the main binding in use for me is KNX - which i have to move and migrate. I have approx 250 KNX items in my house running (lights, dimmers, heating control, temperature, …). Have to say - the KNX is managed by my Electrician - and i don’t have a KNX programming app available to change something. I have received an address list from my Electrician to identify and control the items.

I have them currently setup only with 1 address in OH and it works very well. Now trying to move to OH3 - i see the requirement of e.g. Switch to have 2 addresses instead.

My current setup is in the knx.items under 1.8.x:

Switch Light_EG_Kitchen_Ceiling1 "Lampe Schrank" {knx=" 1/3/5 "}

I am struggling to transfer this into a OH3 connection - i see the code listed in there:

UID: knx:device:d74925c5a6
label: Lampe Schrank
thingTypeUID: knx:device
  pingInterval: 600
  address: 1.3.5
  readInterval: 0
  fetch: false
bridgeUID: knx:ip:d6780b9ab1
location: Dachgeschoss
  - id: Schalter
    channelTypeUID: knx:switch-control
    label: Schalter
    description: ""
      ga: 1.3.5

I see the gateway being online. On the above item i only get the following in the logfile.

10:42:29.253 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'knx:device:d74925c5a6' changed from OFFLINE to UNKNOWN
10:42:33.368 [WARN ] [     ] - negative confirmation of 1.3.5: 2e 00 b1 60 ff ff 13 05 00 80
10:42:33.453 [WARN ] [     ] - negative confirmation of 1.3.5: 2e 00 bd 60 ff ff 13 05 01 43 00
10:42:36.537 [WARN ] [     ] - negative confirmation of 1.3.5: 2e 00 bd 60 ff ff 13 05 01 43 00
10:42:39.613 [WARN ] [     ] - negative confirmation of 1.3.5: 2e 00 bd 60 ff ff 13 05 01 43 00
10:42:42.699 [WARN ] [     ] - negative confirmation of 1.3.5: 2e 00 bd 60 ff ff 13 05 01 43 00
10:42:45.774 [WARN ] [     ] - negative confirmation of 1.3.5: 2e 00 b1 60 ff ff 13 05 00 81
10:42:45.776 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'knx:device:d74925c5a6' changed from UNKNOWN to OFFLINE

First: if you don‘t know exactly what you are doing, you most probably don‘t need the physical address. Remove it, it is known to cause issues in some setups.

Second: Group-addresses are usually written in 1/2/3, not 1.2.3 notation. If so remember correctly that was also the case with the OH1 binding. In your example above you used 1.2.3 in the channel configuration, change that.

Hi Jan,

thx - i know what i want to achieve - switch the light on :slight_smile: therefore i would require the address.

The definition says that the address has to be entered with a “.” instead of a “/” - other says Invalid address.


You proved me right :slight_smile: You know what you want to achieve, but you don’t know what this setting is for. It’s only used in some rare special cases and not needed in 99%+ (if you ask me: it should never have been implemented). And it’s not needed in your case. IF you would need it, then the dot-notation would be correct, but probably with anopther value. So: remove it, just leave the field blank.

My second comment (regarding the slash) was about the channel configuration (the lower part). There the slash is correct and the dot is wrong. So it needs to be 1/3/5 in the ga field (not sure if that needs to be in quotes, but the UI will set them automatically), just like the setting in OH1.

Maybe it wuld be helpful to see your whole configuration string for this switch in OH1.



Maybe this “little” post I made in another thread will make things clearer for you, e.g. what are the adresses, how to use them where and how to do it in main UI.
It gives you the basics only.


1 Like

cool thanks all for your help. i got it working now.


1 Like