Adding the inverter adds the area as sensor prefix without option to remove.

[panmari]

Describe the bug

I recently got a replacement for my solaredge inverter. I wanted to add it again under exactly the same name so that my custom dashboards and automations will flawlessly carry over.

When re-adding the invert, the entities all got a prefix from the area, e.g. garage_solaredge_modbus_i1_ac_current.

Where ist that prefix coming from? Could we disable that behavior, or at least make it configurable?

Expected behavior

Entities are added as solaredge_modbus_i1_ac_current, only using the user-specified prefix "Solaredge Modbus" snake-casified.

Screenshots

N/A

Diagnostic File

config_entry-solaredge_modbus_multi-01KTTSJ9RPQWPRF522HX6BTKMP.json

Debug logs

Home Assistant Version

2026.6.2

solaredge-modbus-multi Version

Version 3.3.0-pre.1

Installation Type

HAOS

Read the Instructions

• My configuration follows https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Configuration
• I have read the Known Issues https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Known-Issues
• This issue is not about a template error (do not report template errors, read https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Template-Design-Notes)

Additional Context

No response

[WillCodeForCats]

That doesn't sound like something I did.

Maybe don't set an area?

[panmari]

It auto-populates when adding the entities:

Even when removing the area here, it already created the entities (see background), so they get the garage prefix. The battery, which is created afterwards by clicking a checkbox to scan for batteries, doesn't get that treatment.

Is there a difference in how the adding of these entities is handled?

[WillCodeForCats]

I'm not (and never have been) doing anything with area names in my code, so it would have to be HA generating that based on the area.

[WillCodeForCats]

Try deleting the hub and re-adding it new (without selecting an area) to see if HA will clear the entity registry of the area-prefixed names.

[WillCodeForCats]

I found it, HA is doing this now as a core change:

Prefix area to entity ID:
home-assistant/core#170560

Include area in entity ID during first-time generation:
home-assistant/core#168899

This is new for HA 2026.6 release.
https://www.home-assistant.io/changelogs/core-2026.6

[panmari]

Thanks for finding the reference!

I tried extending the configuration flow to add the area id field already in the initial onboarding flow, overriding whatever default is inherited from the "deleted devices" registery, where the setting apparently comes from: panmari@7dcdac0

So far no luck. The area selector shows up, but leaving it empty doesn't have the desired effect of leaving the area unassigned for the newly created devices. Do you spot an immediate issue with my code? I'm afraid I'm out of my expertise, I just followed antigravity suggestions for extending the flow.

[WillCodeForCats]

I think HA stores it as JSON data in the .storage directory, file core.entity_registry or core.device_registry

Since this is a new "feature" for HA 2026.6 it would probably need to be a bug report or feature request to HA to clear the area slug from entity names.

[panmari]

So whatever I tried in my fork, I couldn't manage to make it work. @WillCodeForCats do you have some pointers on how the onboarding flow could be updated so that an area setting from this screen will be used for creating the entities? Thanks!

[WillCodeForCats]

I'm not sure that the integration can alter area like that since HA is adding the area name after the integration config step is done, not during it.