2022.12.0 (zigbee2mqtt) entities are not grouped by type anymore

[bartplessers]

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

Lovelace autogenerated dashboard: since 2022.12.0 my zigbee2mqtt entities are not placed in the correcsponding domain card, i.e. "lights":

• individual Z2M lightbulb (1) (mqtt integration)
• automatic created group of lightbulbs (2) (shows here lightbulbs from other integrations)

• 

This results in a cluttered dashboard

Describe the behavior you expected

lightbulbs/switches/sensors/... will go to corresponding domain-group

Steps to reproduce the issue

1. add light to Z2M
2. install MQTT integration
3. observe autogenerated lovelace dashboard

What version of Home Assistant Core has the issue?

2022.12.0

What was the last working version of Home Assistant Core?

2022.11.x

In which browser are you experiencing the issue with?

all

Which operating system are you using to run this browser?

dietpi

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

[spacegaier]

Sounds like https://github.com/home-assistant/frontend/issues/14556 introduced probably by https://github.com/home-assistant/frontend/pull/14577 and https://github.com/home-assistant/frontend/pull/14577

[codyc1515]

Please close this ticket as completed in #14707

[bartplessers]

Please re-open, because this is NOT solved https://github.com/home-assistant/frontend/pull/14707 as about sortorder.

As mentioned in initial post: zigbee2mqtt entities are not placed in the correcsponding domain card, i.e. "lights", but generate an own card per device, i.e.:

[spacegaier]

@bramkragten Is that behavior correct? If those are not in an area or a group, then one card per device is the new logic you had added?

[suawek2]

@bramkragten @spacegaier any progress on this?

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

[suawek2]

bump so the issue isn't closed

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

[codyc1515]

I think this might still be an issue. Can anyone confirm?

[suawek2]

yes, it is still an issue

[bartplessers]

Unfortunatly, yes. Still an 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.

[codyc1515]

I don’t think I’m facing any issue anymore.

[suawek2]

The issue still persists on 2023.11.2

[bartplessers]

Confirmed

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

[suawek2]

not working in 2024.2.2

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

[suawek2]

not working in 2024.5.4

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

[suawek2]

ot working in 2024.8.2