Danfoss Ally integration openHAB doesn't work

So far I am using Eurotronic Spirit TRV. I was very disappointed about that devices loosing connection every time and not being reachable. A stable PID control for that devices can not achieved. But nevertheless the integration in openHAB via the deCONZ Binding works like a charm.

So I decided to replace them by Danfoss Ally devices. The integration in deCONZ works very good. After connection to my Zigbee network the devices has been visible in the GUI. After integration of the DDF file it has been also visible to Phoscon Web App.

But within openHAB the thing state is unknown and most of the channels known from Eurotronic are missing. Also the Setpoint of the temperature shows always NULL. The mode state, typically shows Automatic, Heat or OFF shows NULL.

I tried to find the mistake. First I have extended the DDF file by the config/mode state as mentioned in some github posts, nothing changed. Then I installed a Home Assistant instance to verify the functionality of the devices. Within HA everything works fine as shown below. Is there anything I can test so far?

System:
Danfoss Ally, eTRV0103
Raspberry Pi 4, 2 GB, deCONZ 2.20.1 Release
Raspberry Pi 4, 4 GB, openHAB 3.4.2 stable

Devices Diagnostics from HA:

"77": {
    "config": {
      "battery": 43,
      "displayflipped": false,
      "externalsensortemp": -8000,
      "externalwindowopen": false,
      "heatsetpoint": 2100,
      "locked": false,
      "mode": "heat",
      "mountingmode": false,
      "offset": 0,
      "on": true,
      "reachable": true,
      "schedule": {},
      "schedule_on": false
    },
    "ep": 1,
    "etag": "xxxxxxxxxx",
    "lastannounced": null,
    "lastseen": "2023-03-15T21:25Z",
    "manufacturername": "Danfoss",
    "modelid": "eTRV0103",
    "name": "Thermostat Flur",
    "state": {
      "errorcode": "0",
      "lastupdated": "2023-03-15T21:38:01.028",
      "mountingmodeactive": false,
      "on": true,
      "temperature": 2138,
      "valve": 4,
      "windowopen": "Closed"
    },
    "swversion": "00.20.0008 00.20",
    "type": "ZHAThermostat",
    "uniqueid": "xxxx"
  },
  "78": {
    "config": {
      "battery": 43,
      "on": true,
      "reachable": true
    },
    "ep": 1,
    "etag": "1f55692xxxxxx",
    "lastannounced": null,
    "lastseen": "2023-03-15T21:25Z",
    "manufacturername": "Danfoss",
    "modelid": "eTRV0103",
    "name": "Thermostat Flur",
    "state": {
      "lastset": "2023-03-14T05:30:17Z",
      "lastupdated": "2023-03-15T21:12:06.227",
      "localtime": "2023-03-15T21:12:05",
      "utc": "2023-03-15T21:12:05Z"
    },
    "swversion": "00.20.0008 00.20",
    "type": "ZHATime",
    "uniqueid": "xxxx"
  }

Moved to deCONZ > general support.

I guess openHAB issues are more suited to be discussed on their places? Deconz exposes everything what is expected.

Thanks for the reply. I know what you mean.

But who is responsible for the interface to any home automation system? The interface has two endings. At the moment I am not sure where the bug is located? Is it on the deCONZ side, is it on the openHAB side, or somewhere between…

In this case, openhab.