legacy group: entity not found error in inspector

[Mariusthvdb]

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.

Describe the issue you are experiencing

Describe the behavior you expected

no error

Steps to reproduce the issue

1. simply click on the more-info of a group in dev tools state with inspector open

3. ...

What version of Home Assistant Core has the issue?

2023.12.3

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Safari Mac

Which operating system are you using to run this browser?

Sonoma 14.1.2

State of relevant entities

No response

Problem-relevant frontend configuration

no particular Frontend config, just this yaml for the group

group:
  hub_device_trackers:
    name: Hub device trackers
    all: true
    entities:
      - device_tracker.ha_main
      - device_tracker.synology_diskstation
      - device_tracker.iungo
      - device_tracker.solaredge
      - device_tracker.ikea_tradfri
      - device_tracker.philips_hue_1
      - device_tracker.philips_hue_2
      - device_tracker.philips_hue_3
      - device_tracker.plugwise_smile
      - device_tracker.somfy_tahoma

all trackers are available. I have 7 legacy groups, and clicking any of these throws the error, and, as far as I have tested now, no where else.

Javascript errors shown in your browser console/inspector

error itself does not show a lot of info

Additional information

error seems to only show when debug tools is turned on in dev tools. still, it would be nice trace why, and fix

[karwosts]

I don't think this is related to groups, I think it happens for any entity that is not in the entity registry (e.g. does not have a unique_id).

Frontend requests the entity registry info when you open the popup, and if it does not exist, the WS call returns an error. The frontend correctly and quietly handles this error (assuming you don't have this debug flag enabled), so I don't think there's really anything different that should be done here.

[Mariusthvdb]

yes, I can confirm that is the case! I only have a few of those left and indeed groups are among those ofc. I just tested the core integrations for Alarm control panel (.) and Meteoalarm.

same issue.

should anything change? well, it could print this fact: no 'unique_id on entity' so to make this error be more meaningful

or: 'entityid not found in entity registry'

seems obvious once you know, but it would have helped debugging this 'issue'

[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.