Some knx are not assigned to things/items (Received telegram for unknown group address)

  • Platform information:
    • Hardware: Pi3
    • OS: debian 9.6
    • Java Runtime Environment: Oracle java version “1.8.0_65”
    • openHAB version: openhab2/testing 2.4.0~M5-1
      • 2.4.0.M5 KNX Binding
  • Issue of the topic: some knx are not assigned to things/items

Some values are not assigned to the things/items configured to the group adresses. The excerpt from my configuration below shows two examples. Many other KNX devices are working just finde. I can’t find the problem.

In the TRACE log the KNX2 binding reports “Received telegram for unknown group address”, here 3/1/0. A few lines later it mentions the thing which is configured to the same group address. The received value is not written to the thing/item configure for this group address.

Any ideas?

Items configuration related to the issue
things:

Bridge knx:ip:bridge [
    ipAddress="xxx",
    portNumber=3671,
    type="TUNNEL",
    readingPause=50,
    responseTimeout=10,
    readRetriesLimit=3,
    autoReconnectPeriod=3,
    localSourceAddr="0.0.0"
] {

Thing device we79 "KNX" @ "router" [
    address="1.7.12",
    fetch=true,
    pingInterval=300,
    readInterval=3600
] {
        Type number: Z_H_Betriebsart        "Heizung Betriebsart"       [ ga="5.010:<0/0/1" ]
        Type number: WZ_V_Temperatur_Ist    "Temperatur Wohnzimmer IST" [ ga="9.001:<3/1/0" ]
}
}

items:

Number Z_H_Betriebsart          "Heizung Betriebsart [MAP(hvac.mapping):%s]"    <settings>      (H)     { channel="knx:device:bridge:we79:Z_H_Betriebsart"}
Number WZ_V_Temperatur          "Temperatur Wohnzimmer [%.1f °C]"       <temperature>   (T, WZ)         { channel="knx:device:bridge:we79:WZ_V_Temperatur_Ist" }

logs

2018-11-15 20:24:36.248 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.20:3671: indication from 1.7.31
2018-11-15 20:24:36.251 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from '1.7.31' to '3/1/0'
2018-11-15 20:24:36.255 [DEBUG] [.internal.handler.DeviceThingHandler] - Thing 'knx:device:bridge:we79' received a Group Write telegram from '1.7.31' for destination '3/1/0'
2018-11-15 20:24:36.253 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 3/1/0
2018-11-15 20:24:36.262 [TRACE] [.internal.handler.DeviceThingHandler] - Thing 'knx:device:bridge:we79' processes a Group Write telegram for destination '3/1/0' for channel 'knx:device:bridge:we79:WZ_V_Temperatur_Ist'
2018-11-15 20:24:36.265 [TRACE] [g.knx.internal.dpt.KNXCoreTypeMapper] - toType datapoint DPT = 9.001

where is the we79 coming from?

based on your configs, the Thing UID should be: knx:device:bridge:router

Maybe you used we79 in a previous configuration attempt?

edit: Ok, I see your edited config now…checking

Sorry, that was renamed incompletely for the post only. The names of KNX device and items match. Fixed it above.
When looking at the Paper UI the path from Configuration/Things/KNX/Channels to the related item is also clickable (blue circle with white filled dot).

have you tried to set the IA (Individual Address aka Physical Address) to the one transmitting the KNX message? (1.7.31) to your we79 Thing to see if this problem goes away?

What is device with IA 1.7.12 and what is device with IA 1.7.31 ?

1.7.12 is the front-end with the temperature sensor
1.7.31 is the actor that controls the heating and receives temperature
Both are configured for reading and the message was triggered by issuing a read request from ets. Both responded.

Just to make sure this isn’t the problem, here’s a log from a write request, changing the heatings hvac mode

21:09:03.542 [DEBUG] [tuwien.auto.calimero                 ] - calimero.link.192.168.1.20:3671: indication from 15.15.243
21:09:03.542 [TRACE] [knx.internal.client.AbstractKNXClient] - Received a Group Write telegram from '15.15.243' to '0/0/1'
21:09:03.542 [DEBUG] [b.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
21:09:03.551 [DEBUG] [x.internal.handler.DeviceThingHandler] - Thing 'knx:device:bridge:we79' received a Group Write telegram from '15.15.243' for destination '0/0/1'
21:09:03.554 [DEBUG] [b.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 0/0/1
21:09:03.560 [TRACE] [x.internal.handler.DeviceThingHandler] - Thing 'knx:device:bridge:we79' processes a Group Write telegram for destination '0/0/1' for channel 'knx:device:bridge:we79:Z_H_Betriebsart'
21:09:03.567 [TRACE] [ng.knx.internal.dpt.KNXCoreTypeMapper] - toType datapoint DPT = 5.010
21:09:03.596 [INFO ] [smarthome.event.ItemStateChangedEvent] - Z_H_Betriebsart changed from 1.0 to 2.0

And f*** me, now it’s working… I’ve been switching the hvacs mode around, looking up TRACE logs for the last two hours because it had been unset.

The item value should’nt be a float though, but I think that’s a known bug.

No idea what happened here. Set ga to “0/01” instead of “<0/0/1” and did a restart. OpenHab2 version is still the same. Thanks for looking into it.

1 Like

I’ve just noticed that changes to a knx group address in a things file are only applied on a restart whereas changes on item files are applied immediately.

that shouldn’t happen. they should be immediate as well

I had another type of issue when I was editing the *.things file but this was closed: https://github.com/openhab/openhab2-addons/issues/3609

and in my case (if I remember well), changes to the GAs assigned to the Channels were immediate after an edit… maybe I am wrong… I will try to test this again

1 Like

you mean this one: https://github.com/openhab/openhab2-addons/issues/3779 ?

Yes, every change or successful write to a config file in $OPENHAB_CONF (e.g. /etc/openhab2/* for a apt based installation, like raspberry) should result in an immediate reload of this file.
But I can confirm that sometimes this mechanism does not work as expected.
If changing something with no success, it’s appropriate to do a openHAB restart, just to be sure.

1 Like

I read something about int being always being representated as floats when migrating to the KNX OpenHab2 branch version. Some thread about migration/update. All the single byte values I see in the logs are shown with a decimal digit. All of my map transforms stopped working with KNX version 2.
The issue you mentioned does not look like this problem.

I tried to google it without look. Should I create an issue in GitHub?

I tried the update/reload problem again. In knx.things I had:

Type number: Z_H_Betriebsart        "Heizung Betriebsart"       [ ga="5.010:<0/0/1" ]

I changed it to:

Type number: Z_H_Betriebsart        "Heizung Betriebsart"       [ ga="20.102:<0/0/1" ]

As you can see in the log, a reload was triggered, but the datatype did not update. When creating the thread I had set the datatype 20.102 (HVAC mode); while this datatype is used “Z_H_Betriebsart” does not receive updates (while 5.010 works, recommended here:https://github.com/openhab/openhab2-addons/issues/2203). That was the root of the problem why I created this thread.

23:50:08.748 [DEBUG] [tuwien.auto.calimero                 ] - KNXnet/IP Tunneling 192.168.1.20:3671: sending connection state request, attempt 1
23:50:16.350 [DEBUG] [tuwien.auto.calimero                 ] - calimero.link.192.168.1.20:3671: indication from 15.15.243
23:50:16.350 [TRACE] [knx.internal.client.AbstractKNXClient] - Received a Group Write telegram from '15.15.243' to '0/0/1'
23:50:16.350 [DEBUG] [b.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
23:50:16.360 [DEBUG] [x.internal.handler.DeviceThingHandler] - Thing 'knx:device:bridge:we79' received a Group Write telegram from '15.15.243' for destination '0/0/1'
23:50:16.364 [DEBUG] [b.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 0/0/1
23:50:16.367 [TRACE] [x.internal.handler.DeviceThingHandler] - Thing 'knx:device:bridge:we79' processes a Group Write telegram for destination '0/0/1' for channel 'knx:device:bridge:we79:Z_H_Betriebsart'
23:50:16.374 [TRACE] [ng.knx.internal.dpt.KNXCoreTypeMapper] - toType datapoint DPT = 5.010
23:50:33.072 [INFO ] [del.core.internal.ModelRepositoryImpl] - Refreshing model 'knx.things'
23:50:41.590 [TRACE] [knx.internal.client.AbstractKNXClient] - Received a Group Write telegram from '15.15.243' to '0/0/1'
23:50:41.593 [DEBUG] [tuwien.auto.calimero                 ] - calimero.link.192.168.1.20:3671: indication from 15.15.243
23:50:41.593 [DEBUG] [b.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
23:50:41.597 [DEBUG] [x.internal.handler.DeviceThingHandler] - Thing 'knx:device:bridge:we79' received a Group Write telegram from '15.15.243' for destination '0/0/1'
23:50:41.602 [DEBUG] [b.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 0/0/1
23:50:41.603 [TRACE] [x.internal.handler.DeviceThingHandler] - Thing 'knx:device:bridge:we79' processes a Group Write telegram for destination '0/0/1' for channel 'knx:device:bridge:we79:Z_H_Betriebsart'
23:50:41.608 [TRACE] [ng.knx.internal.dpt.KNXCoreTypeMapper] - toType datapoint DPT = 5.010