Integration page not showing correct number of entities for subentries

[hanwg]

Checklist

• [x] I have updated to the latest available Home Assistant version.
• [x] I have cleared the cache of my browser.
• [x] I have tried a different browser to see if it is related to my browser.
• [ ] I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

The Telegram bot integration creates a service for each config entry. For each subentry, the integration also creates 1 entity associated with the service.

The screenshot below shows 1 config entry with 5 subentries hence there is 1 service with 5 entities (highlighted in red). The frontend shows 5 entities for each subentry (highlighted in blue) which is misleading and users might mistaken that there are a total of 25 distinct entities.

Describe the behavior you expected

The entity count for each subentry should only count entities related to that subentry. In this case, it should show only 1 entity for each of the subentry.

Steps to reproduce the issue

1. Add the Telegram bot integration.
2. Add 2 or more subentries (chat IDs).
3. The integration page shows the incorrect no. of entities for each subentry.

What version of Home Assistant Core has the issue?

core-2025.9.1

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue?

Brave

Which operating system are you using to run this browser?

Windows 11

State of relevant entities

Problem-relevant frontend configuration

JavaScript errors shown in your browser console/inspector

Additional information

No response

[karwosts]

Kitchen sink doesn't seem to have a problem with counting here:

It seems like it should be filtering to the subentry id.

Can you check the details about the subentries and entities in .storage?

E.g. core.config_entries

{
  "created_at": "2025-09-06T14:11:56.341384+00:00",
  "data": {},
  "disabled_by": null,
  "discovery_keys": {},
  "domain": "kitchen_sink",
  "entry_id": "01K4FNX59NQA2K356M1NNS5VE5",
  "minor_version": 1,
  "modified_at": "2025-09-09T23:02:56.519007+00:00",
  "options": {},
  "pref_disable_new_entities": false,
  "pref_disable_polling": false,
  "source": "import",
  "subentries": [
    {
      "data": {
        "state": 1
      },
      "subentry_id": "01K4RBD60A917CECDD8MKG2J66",
      "subentry_type": "entity",
      "title": "Subsensor",
      "unique_id": null
    },
    {
      "data": {
        "state": 2
      },
      "subentry_id": "01K4RBFKR6PD3316HWQF5H171S",
      "subentry_type": "entity",
      "title": "Subsensor2",
      "unique_id": null
    }
  ],
  "title": "Kitchen Sink",
  "unique_id": null,
  "version": 1
}

Entities from core.entity_registry:

[
  {
    "aliases": [],
    "area_id": null,
    "categories": {},
    "capabilities": null,
    "config_entry_id": "01K4FNX59NQA2K356M1NNS5VE5",
    "config_subentry_id": "01K4RBD60A917CECDD8MKG2J66",
    "created_at": "2025-09-09T23:02:03.332662+00:00",
    "device_class": null,
    "device_id": "6db586d239f8786ea90167f3494e811f",
    "disabled_by": null,
    "entity_category": null,
    "entity_id": "sensor.subsensor",
    "hidden_by": null,
    "icon": null,
    "id": "8544cf49a97cd3fa605c89e318d1204f",
    "has_entity_name": true,
    "labels": [],
    "modified_at": "2025-09-09T23:02:03.340050+00:00",
    "name": null,
    "options": {
      "conversation": {
        "should_expose": false
      }
    },
    "original_device_class": null,
    "original_icon": null,
    "original_name": null,
    "platform": "kitchen_sink",
    "suggested_object_id": null,
    "supported_features": 0,
    "translation_key": null,
    "unique_id": "01K4RBD60A917CECDD8MKG2J66",
    "previous_unique_id": null,
    "unit_of_measurement": null
  },
  {
    "aliases": [],
    "area_id": null,
    "categories": {},
    "capabilities": null,
    "config_entry_id": "01K4FNX59NQA2K356M1NNS5VE5",
    "config_subentry_id": "01K4RBFKR6PD3316HWQF5H171S",
    "created_at": "2025-09-09T23:03:31.163182+00:00",
    "device_class": null,
    "device_id": "1edd33130171d79d68ef65f8cc40395f",
    "disabled_by": null,
    "entity_category": null,
    "entity_id": "sensor.subsensor2",
    "hidden_by": null,
    "icon": null,
    "id": "9382731d99ff89bd87e75a1087e176e9",
    "has_entity_name": true,
    "labels": [],
    "modified_at": "2025-09-09T23:03:31.166641+00:00",
    "name": null,
    "options": {
      "conversation": {
        "should_expose": false
      }
    },
    "original_device_class": null,
    "original_icon": null,
    "original_name": null,
    "platform": "kitchen_sink",
    "suggested_object_id": null,
    "supported_features": 0,
    "translation_key": null,
    "unique_id": "01K4RBFKR6PD3316HWQF5H171S",
    "previous_unique_id": null,
    "unit_of_measurement": null
  }
]

[karwosts]

I guess probably what you're showing here is:

5 sub entries, each subentry is linked to the same service, and that service has 5 entities. As that row you're highlighting is the device row component, and it just counts how many entities that device has.

If each subentry had a different device with 1 entity, it would show 1 there.

[hanwg]

Yes, you understood it correctly.

Shouldn't the display show only 1? i.e. count only entities whose config_subentry_id matches the row's subentry.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[tomlut]

Not stale.