impossible to get info with DPT 13.10 DPT 235.1

[jluc2808]

Description of problem:

• [ x] using Home-Assistant knx integration

Version information: XKNX Version: 2.12.2 KNX-Frontend Version: 2024.1.20.105944 Connected to bus: Oui

KNX installation:

• using: Hager domovea V2 TJA470.

my configuration.yaml ` sensor:

comptage général 3

- name: "comptage général 3 puissance"
  state_address: "24/4/240"
  type: power
- name: "comptage général 3 energie"
  state_address: "24/4/241"
  type: active_energy
  sync_state: 1`

the power is OK and return a value the active_energy have always status : unknown (24/4/241)

DPT of 24/4/241 is DPT13.10 DPT 235.1

[farmio]

Hi 👋!

DPT of 24/4/241 is DPT13.10 DPT 235.1

Those are 2 different types. If it is DPT 13.010 that is fine and you can use active_energy. If it is DPT 235.001 that is just not supported (yet?) in HA. It was recently added to xknx but not yet released and it is unclear if / how these compound DPT structures can be used in sensors. See https://www.home-assistant.io/integrations/knx/#value-types for currently supported DPTs.

[jluc2808]

i don't know what to say because in the domovea / KNX display it is noted like i wrote DPT13.10 DPT 235.1 so i understand that it is confusing, but i don't have any idea of how to understand this value

[jluc2808]

[farmio]

🤷 sorry I don't know Domovea. Maybe have a look at the ETS project where the GA is defined... or the manual.

[jluc2808]

i have the explanation from hager support (already in that post : https://github.com/openhab/openhab-addons/issues/15159) the TE331 from hager is coded with a group address for that objet which is 6 bytes

• 4 for DPT 13.010 corresponding to Wh
• 1 for DPT 235.01 corresponding to Tarification
• 1 for 235.01 to control now the only value available in HA is a 4 bytes telegram (so the 6 bytes is unreadable)

is there a solution to trap the 6 bytes to split in 4 bytes and let apart the 2 bytes not used ? or is there an evolution which will accept telegram with 6 bytes ?

[farmio]

This will be possible eg. via a trigger based template sensor when the next version (to be released yet) of xknx is used in HA.

Maybe there is a way to do it currently too - using raw payloads somehow.