New behaviour of shelly integration is confusing!

[GeorgeZ83]

The problem

New behaviour of shelly integration regarding smart switches with two channels/relays (like 2PMGen3) creates subdevices for each channel. this makes managing and understanding the device harder and confusing.

I think it makes much more sense to see all related entities belonging to a device in one page (same as every other integrations)

What version of Home Assistant Core has the issue?

2025.6.0

What was the last working version of Home Assistant Core?

2025.5.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Shelly

Link to integration documentation on our website

https://www.home-assistant.io/integrations/shelly

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @balloob, @bieniu, @thecode, @chemelli74, @bdraco, mind taking a look at this issue as it has been labeled with an integration (shelly) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of shelly can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign shelly Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

shelly documentation
shelly source
_{^{(message by IssueLinks)}}

[bieniu]

The use of sub-devices was the only way to adapt Shelly integration to the Integration Quality Scale requirements without entity and device names change.

In addition, sub-devices allow you to better assign individual relays/channels to their actual roles and rooms/areas.

Initially, this change may cause some confusion, but in the long run it helps keep devices organized.

[GeorgeZ83]

It may be a good ideea to add links to the sub-devices pages in the main device page ( in the device info area below the MAC adress); this would at least save a step when switching between one sub-device page to another.

It seems that each sub-device page already has links to the main device (where it says connected via...) but not the other way around.

Thanks for taking the time to reply!

[Theo16]

I understand this change, but couldn't you have done it in a way that the area assigned to a device in the previous version would be assigned to all sub-devices in the new version? A large part of my automation stopped working, and I really had to spend some time figuring out why, because it's not mentioned anywhere that this attribute doesn't carry over.

[bieniu]

A large part of my automation stopped working

Can you show an example of automation that stopped working?

[bieniu]

It may be a good ideea to add links to the sub-devices pages in the main device page