Skip to content

feat: always separate loadpoint/vehicle entities into own devices - #339

Merged
marq24 merged 3 commits into
marq24:mainfrom
mschmiedel:main
Sep 30, 2026
Merged

marq24 merged 3 commits into
marq24:mainfrom
mschmiedel:main

Conversation

@mschmiedel

Copy link
Copy Markdown
Contributor
  • Remove multi_loadpoint_config/multi_vehicle_config conditionals so name_addon is always set, ensuring proper device separation even with a single loadpoint or vehicle
  • Fix chargetotalimport translation: 'Netzbezug'/'Grid imported' → 'Geladen (Gesamt)'/'Charged (Total)' — this is the wallbox meter, not grid import

Affected platforms: sensor, binary_sensor, button, switch, select, number

BREAKING: Loadpoint and vehicle entities will move from the main site device into their own dedicated devices after restart.

- Remove multi_loadpoint_config/multi_vehicle_config conditionals
  so name_addon is always set, ensuring proper device separation
  even with a single loadpoint or vehicle
- Fix chargetotalimport translation: 'Netzbezug'/'Grid imported'
  → 'Geladen (Gesamt)'/'Charged (Total)' — this is the wallbox
  meter, not grid import

Affected platforms: sensor, binary_sensor, button, switch, select, number

BREAKING: Loadpoint and vehicle entities will move from the main
site device into their own dedicated devices after restart.
@mschmiedel

Copy link
Copy Markdown
Contributor Author

Hi, please check carefully for the breaking change part.

If this is not wanted it is OK.

But the correct Name for the entity is important, the actual version shows "Wallbox energy meter" as "Grid consumption".

@marq24

marq24 commented Sep 30, 2026

Copy link
Copy Markdown
Owner

Hi Martin

  1. I would kindly ask to start a discussion/issue before a PR is generated - this might save us some time - since as you already anticipated, it might be the case that the change is not wanted (or this is designed by purpose)

  2. Please do not mix/combine changes... since I don't want to start cherry-picking [so the adjusted translation]

  3. Right now I don't see the breaking part - it's just in the HA UI, where certain entities will be shown/displayed (the connection to a device is IMHO quite loose... So "yes" users might get confused - but at the end all existing dashboards and automations will still continue to work as they are.

@marq24

marq24 commented Sep 30, 2026 •

Copy link
Copy Markdown
Owner

... but since the PR is already made - Why do you believe, that the split of entities should be forced (without any option for the user to choose)? I have the philosophy to give the users a choice what they prefer (when this is possible) ? I am honest interested in your opinion, why you believe forcing the split is the right thing to do.

@mschmiedel

Copy link
Copy Markdown
Contributor Author

I will retest the part of the separation. I first assumed it was not possible to get the Wallbox as separate Entity, but then I saw the controls. I assumed it only separated if you had more than one.

But the naming of the Entities is a real issue. I will retest it with only the Entity Name change and give feedback... ;)

@mschmiedel

Copy link
Copy Markdown
Contributor Author

I retested, and you are right, the forcing of the separate entities is not wanted, you have a checkbox for that (I am not sure if that was added after I configured first or if I oversaw it), but I could reconfigure everything as it should be.

However, the naming of the entity is a real bug, this should be merged as "Netzbezug" is technically incorrect, it is the complete energy meter of the wallbox no matter where the energy came from...

@marq24
marq24 merged commit 8480c53 into marq24:main Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants