KNX DPT PT 235.001 active_energy + tariff

bbreton09 · December 18, 2022, 2:22pm

Hello, do you think it is possible to integrate the DPT 235.001 into the KNX plugin. This contains DPT 13.010 and 5.006+1 data validity byte. The decoding description is avaible here : Particularité du DPT 235.001 - Forum Communauté Jeedom.

Thanks

farmio · December 18, 2022, 2:48pm

Hi !
Currently we don’t support “compound” DPTs as sensors. It would need a quite big change in how the entity creation works.
You may use a knx_event trigger in a template sensor and work with the raw payload meanwhile.

jbellirigenty · June 17, 2023, 4:13pm

Hello,

Do you have any news about this feature?

Thank you

farmio · June 17, 2023, 4:24pm

Not really.

I did some drafts to see which implementation would fit better for such things… but didn’t come to any conclusion yet.

github.com/XKNX/xknx

DPTComplex

XKNX:main ← XKNX:dptcomplex

opened 06:27PM - 03 Jun 23 UTC

farmio

+70 -13

## Description  Use Dataclasses as container for complex DPT values. The first example is XYYColor. Pros: - properly typed, any type supported - lightweight (in py3.10 I think we can even set it `slotted=True`) - useable with data validation libraries (eg. pydantic) - maybe outsource dict / json serialisation to external library - decoupled internal data schema (for use in xknx Devices) from user-visible (HA events etc.) Cons: - extra conversion step needed to get from user input (dict / json) to data - extra step needed to get displayable data (eg. for group monitor) - maybe `dataclass.asdict()` or custom - extra documentation effort required Fixes # (issue) ## Type of change  - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Code quality improvements to existing code or addition of tests ## Checklist - [ ] The documentation has been adjusted accordingly - [ ] Tests have been added that prove the fix is effective or that the feature works - [ ] The changes are documented in the changelog (docs/changelog.md)

github.com/XKNX/xknx

DPTDict

XKNX:main ← XKNX:dptdict

opened 06:20PM - 03 Jun 23 UTC

farmio

+165 -118

## Description  Use TypedDict as container for complex DPT values. The first example is XYYColor. Pros: - readable - no need to convert from dicts (from user input - eg. HAs `knx.send`) to other type - can probably be used to auto-create documentation Cons: - lots of `dict.get()` needed no default values supported in TypedDict - no dot-notation supported - changing dict-schema would introduce breaking changes in the future (user input schema coupled to data schema) - no direct validation from user input - would need an extra step currently `total=False` is used - maybe it would be better to switch to `total=True` Fixes # (issue) ## Type of change  - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Code quality improvements to existing code or addition of tests ## Checklist - [ ] The documentation has been adjusted accordingly - [ ] Tests have been added that prove the fix is effective or that the feature works - [ ] The changes are documented in the changelog (docs/changelog.md)

bbreton09 · September 8, 2023, 12:14pm

HI,

I hope you find a solution. It’s sad not to be able to extract the kwh directly. In any case, thank you for the work done on xknx.

grubers · December 3, 2024, 9:39pm

Hi

I ran into the exact same issue with my Hager TE331 but I managed to implement a workaround.

Step 1: Setup event for KNX telegrams of meter

Setup an event for telegrams to the corresponding address (see KNX - Home Assistant).

Example configuration:

event:
  - address:
    - "24/4/190" # Gesamtzähler (Elektrische Energie)

Step 2: Setup template sensor based on event

- trigger:
    trigger: event
    event_type: knx_event
    event_data:
      destination: "24/4/190"
  sensor:
    - name: "Gesamtzähler Elektrische Energie"
      # Interpret first 4 (of 6) bytes as Wh and convert to kWh, if first 4 bytes are not all 0.
      # Every now and then the meter sends telegrams with only the tariff bytes (last 2) set (e.g. 0x000000000500)
      # and these telegrams must be ignored (otherwise the state is intermittently (re-)set to 0).
      state: >
        {{
          (
            ((trigger.event.data.data[0] * 256 * 256 * 256) +
            (trigger.event.data.data[1] * 256 * 256) +
            (trigger.event.data.data[2] * 256) +
            (trigger.event.data.data[3])) / 1000
          )
          if (
            trigger.event.data.data[0] != 0 or
            trigger.event.data.data[1] != 0 or
            trigger.event.data.data[2] != 0 or
            trigger.event.data.data[3] != 0
          )
          else this.state
          }}
      unit_of_measurement: "kWh"
      state_class: "total"

I hope this helps

farmio · December 3, 2024, 9:51pm

If the DPT is set correctly in ETS and you uploaded the project, you should be able to use knx.telegram trigger with built-in decoder, instead of knx_event.
It should also show up correctly in the group monitor.