Problems with KNX binding with ABB router

Add-ons Bindings
1

Hi,

After some evenings searching and browsing the internet i can’t do much else then to post this topic.

I have a KNX installation and use the ABB IPR/S 3.1.1 IP-Router

I have configured the router in the openhab paper UI

image
image1150×761 44.2 KB

192.168.1.132 is the ip address of the ABB IP-Router
192.138.1.131 is the ubuntu box where i run openhab (in docker)

The

I also configured a KNX device with the next properties
address = blank
*fetch = ON (i can see device parameters like manufacturername, serial number, …) *
interval (poll status device) = 600
interval (between attempts read group status on bus) = 0

both things (KNX/IP Gateway and KNX Device) appear online

I configured a channel (switch) with the next properties
address = ga=“0/0/1<0/0/1”

I linked a an item “Switch” that is visible in the control panel

when I switch the switch in the control panel nothing happens.
In the logfile I see the next statements, i can’t seem to see an error.

Who can help me? I would be very thankfull.

2020-10-26 21:40:48.802 [hingStatusInfoChangedEvent] - ‘knx:ip:2fe6cbfa’ changed from OFFLINE (COMMUNICATION_ERROR): server request to ONLINE
2020-10-26 21:40:48.804 [hingStatusInfoChangedEvent] - ‘knx:device:7dba7656’ changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2020-10-31 14:47:59.073 [hingStatusInfoChangedEvent] - ‘knx:ip:2fe6cbfa’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): server request
2020-10-31 14:47:59.089 [hingStatusInfoChangedEvent] - ‘knx:device:7dba7656’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2020-10-31 14:48:59.099 [hingStatusInfoChangedEvent] - ‘knx:ip:2fe6cbfa’ changed from OFFLINE (COMMUNICATION_ERROR): server request to ONLINE
2020-10-31 14:48:59.101 [hingStatusInfoChangedEvent] - ‘knx:device:7dba7656’ changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2020-11-07 16:48:26.340 [hingStatusInfoChangedEvent] - ‘knx:device:7dba7656’ changed from ONLINE to UNINITIALIZED
2020-11-07 16:48:26.350 [hingStatusInfoChangedEvent] - ‘knx:device:7dba7656’ changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2020-11-07 16:48:26.351 [hingStatusInfoChangedEvent] - ‘knx:ip:2fe6cbfa’ changed from ONLINE to UNINITIALIZED
2020-11-07 16:48:26.364 [hingStatusInfoChangedEvent] - ‘knx:ip:2fe6cbfa’ changed from UNINITIALIZED to OFFLINE
2020-11-07 16:48:26.366 [hingStatusInfoChangedEvent] - ‘knx:ip:2fe6cbfa’ changed from OFFLINE to UNINITIALIZED (HANDLER_MISSING_ERROR)
2020-11-07 16:48:26.530 [temChannelLinkRemovedEvent] - Link ‘Test_LichtTechnischeRuimte => knx:device:79963810:1’ has been removed.
2020-11-07 16:48:26.533 [temChannelLinkRemovedEvent] - Link ‘Uitgangen20A_LichtTechnischeRuimte => knx:device:e95b974d:1’ has been removed.
2020-11-07 16:48:26.542 [temChannelLinkRemovedEvent] - Link ‘Test_LichtTechnischeRuimte => knx:device:7dba7656:1’ has been removed.
2020-11-07 16:48:26.543 [temChannelLinkRemovedEvent] - Link ‘KNXDevice_test => knx:device:794b8156:1’ has been removed.
2020-11-07 16:48:26.543 [temChannelLinkRemovedEvent] - Link ‘Test_ => knx:device:e15e338d:1’ has been removed.
2020-11-07 16:48:43.579 [hingStatusInfoChangedEvent] - ‘knx:device:7dba7656’ changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2020-11-07 16:48:43.589 [hingStatusInfoChangedEvent] - ‘knx:ip:2fe6cbfa’ changed from UNINITIALIZED to INITIALIZING
2020-11-07 16:48:43.602 [hingStatusInfoChangedEvent] - ‘knx:ip:2fe6cbfa’ changed from INITIALIZING to UNKNOWN
2020-11-07 16:48:43.619 [hingStatusInfoChangedEvent] - ‘knx:device:7dba7656’ changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2020-11-07 16:48:43.628 [hingStatusInfoChangedEvent] - ‘knx:device:7dba7656’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2020-11-07 16:49:43.652 [hingStatusInfoChangedEvent] - ‘knx:ip:2fe6cbfa’ changed from UNKNOWN to ONLINE
2020-11-07 16:49:43.652 [hingStatusInfoChangedEvent] - ‘knx:device:7dba7656’ changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2020-11-07 16:50:17.830 [ome.event.ItemCommandEvent] - Item ‘Test_LichtTechnischeRuimte’ received command ON
2020-11-07 16:50:17.830 [nt.ItemStatePredictedEvent] - Test_LichtTechnischeRuimte predicted to become ON
2020-11-07 16:50:17.834 [vent.ItemStateChangedEvent] - Test_LichtTechnischeRuimte changed from NULL to ON
2020-11-07 16:56:44.540 [ome.event.ItemCommandEvent] - Item ‘Test_LichtTechnischeRuimte’ received command OFF
2020-11-07 16:56:44.540 [nt.ItemStatePredictedEvent] - Test_LichtTechnischeRuimte predicted to become OFF
2020-11-07 16:56:44.543 [vent.ItemStateChangedEvent] - Test_LichtTechnischeRuimte changed from ON to OFF
2020-11-07 16:57:46.157 [ome.event.ItemCommandEvent] - Item ‘Test_LichtTechnischeRuimte’ received command ON

2

To add, I also added the suggestion of @Udo_Hartmann to add the DPT wich not seems to help.

3

I have seen that i have made an error in the log LEVEL.
I see much more logging now.

I think this could be the problem
[DEBUG] [.internal.handler.DeviceThingHandler] - None of the configured GAs on channel ‘knx:device:7dba7656:1’ could handle the command ‘ON’ of type ‘OnOffType’

I see the next post on that:
https://community.openhab.org/t/knx2-solved-none-of-the-configured-gas-on-channel-could-handle-the-command/46196

Could the problem be that I am only using the same GA for reading the status?
1.001:ga=“0/0/1<0/0/1”

On 0/0/1 I already linked the status of the KNX actuator channel so 0/0/1 should always have the correct state?
Or am I missing something?

4

The GA is not correct.

If configuring the Channel with Paper UI, please instead of

1.001:ga="0/0/1<0/0/1"

use simply

<0/0/1

If using a *.things file, please use

[ ga="<0/0/1" ]

as the last part of Type definition.

However, I have to point out, that you will need two different GA for a switch channel to work properly, the first is to send a command to the switch actuator, the second is to get the status of the switch actuator.
Although this is not mandatory in knx, it’s strongly recommended to do so. This would result in the following GA definition:

[ga="0/0/1+<0/0/2"]

or in Paper UI

0/0/1+<0/0/2

please note the + between first and second GA.

Please use code fences when posting configurations or logging.

5

It works!

Thank you for your assistance @Udo_Hartmann

Can we further discuss (I like to understand everything) the reason why a separate GA for the feedback is necessary?
I’m sure it is the case but I don’t understand why.

Everything seems to work now, also when I switch the light manually, the status in openhab and in the gui is immediately updated.

In ETS I added the status of the actuator channel to 0/0/1 and that does the trick.

I don’t want to be difficult but I just want to understand why everybody is using 2 GA’s.
What functionality do I miss when only using one?

greetings,
Ruben

6

The point is a unidirectional communication. Please be aware that an actuator in knx may react on other GAs, for example a central off GA, or a scene GA.