KNX Energy meter in Energy panel

Configuration
1

It seems knx enegy meters can’t be used in the energy panel. I have two meters of the type active_energy_kwh and they don’t show up in the drop-down.

I also tried to customize them by adding state_class with the value total_increasing or measurement but that does not work either.

Does anyone have a solution for this?

EDIT: This is what my entity currently looks like when I open it in the developer tools:

source: 1.1.10
last_knx_update: '2021-08-24 09:37:19.490025+00:00'
unit_of_measurement: kWh
friendly_name: Opgewekt Actief Vermogen
device_class: energy
icon: mdi:home-export-outline
state_class: total_increasing
2

total_increasing Isn’t released yet - will be included in 2021.9. Then Knx sensor state_class can also be directly configured in yaml.

Beta starts tomorrow. Try it and let us know if you run into problems.

3

Any news here?
This sensor (from a Shelly) shows up as an individual device for Energy Dashboard

grafik
grafik1632×164 44.2 KB

looking identical, but this two (from KNX integration) do not:

grafik
grafik1632×348 62 KB

the ‘missing’ sensors:

grafik
grafik724×640 86.8 KB

This is on 2022.10.5 with xknx-1.1.0.

The only difference I could find in the registry is that the knx entry has no device_id set:

{
  "area_id": null,
  "capabilities": {
    "state_class": "total_increasing"
  },
  "config_entry_id": "a1ad6cbe4a7a0a10f966c35793968e5f",
  "device_class": null,
  "device_id": null,
  "disabled_by": null,
  "entity_category": null,
  "entity_id": "sensor.w_kaffeemaschine",
  "hidden_by": null,
  "icon": null,
  "id": "31e0e398b037d09def9285a3983d3ce2",
  "has_entity_name": false,
  "name": "Zähler Kaffeemaschine",
  "options": {},
  "original_device_class": "energy",
  "original_icon": null,
  "original_name": "w_kaffeemaschine",
  "platform": "knx",
  "supported_features": 0,
  "unique_id": "6/0/9",
  "unit_of_measurement": "kWh"
},

{
  "area_id": null,
  "capabilities": {
    "state_class": "total_increasing"
  },
  "config_entry_id": "8f1e8aeb7f016454859bf928db707329",
  "device_class": null,
  "device_id": "2baa4c245d1d290a36663ed8e0077ae8",
  "disabled_by": null,
  "entity_category": null,
  "entity_id": "sensor.k_hifi_main_energy",
  "hidden_by": null,
  "icon": null,
  "id": "ee8301509887e29aa7c0ec9cee064d7e",
  "has_entity_name": false,
  "name": null,
  "options": {},
  "original_device_class": "energy",
  "original_icon": null,
  "original_name": "K_HIFI_MAIN Energy",
  "platform": "shelly",
  "supported_features": 0,
  "unique_id": "C45BBE626EC6-relay_0-energy",
  "unit_of_measurement": "kWh"
},
4

This works fine on my system (with type: active_energy as my sensors report Wh, not kWh).

5

OK, DPT: 13.010?, could you please show a config entry?
I think I would prefer 13.010 anyway for it’s better resolution.

6

It looks exactly like yours (except I didn’t set a name and have “Wh” as unit.).

7

Yep, finally solved it now: the change to 13.010 (Wh) did not help.

The entities started to show up immediately after I removed the ‘name’ attribute I have overwritten in the GUI, perhaps caused by the german umlaut in the word “Zähler”, which is useless anyway.

I’ll check that out later, first I have to deal with the change of the unit in the long term database, Home Assistant currently considers that I have used up 1.2 MWh today :slight_smile:

8

That’s very unfortunate. If you can reproduce that the energy dashboard doesn’t accept entities with name attribute (with or without umlaut) I would consider this a bug - then it would be best to open an issue at GitHub.

9

OK, will investigate this further, still have ~56 more meters to add, took the bigger consumers first. Now I have a working meter template to copy.