HomeMatic device names / HA entity names

[noxhirsch]

I'm a little confused about the device/entity names:
In HomeMatic this device, for example, is called "ws_charger". The device in HA is also named like this - as well as the diagnostic sensors. For normal sensors and controls, however, the name is not adopted.
Is this not yet implemented or a bug? Or must there be something wrong in my installation? I have already deleted the integration and removed all remaining entries from the entity registry, but at least that doesn't seem to be the problem.

[SukramJ]

Did you set the name of channels in your CCU?

[noxhirsch]

I'd vote for Opt2, too.

How do you work with ccu programs and direct connections without naming the channels?

I only have a few heating groups - direct connections I have never touched myself and programs only very rarely. Since I have a pretty wild mix of devices (HM,Zigbee,ESPHome,...) at the moment, I automate everything in HomeAssistant.

[SukramJ]

Please test the latest release

[Lemocin]

Please test the latest release

Seems to work. I don't really know why it only shows the 4 in some views.

Even if i rename the entity, It stay's on 4 on the autogenerated lovelace card. If i re-add the card then it changes.
On the device view it discards always the Device name in the entity name but i think that is intended from HA(so it justs says e.g. Level and not Roomname Levelin the device view).

[SukramJ]

If you rename Gästezimmer 4 to Gästezimmer it should be displayed on all cards.
if you change it in the CCU you have to click on reload integration (integrations page) to clear the caches. A restart of HA doesn't clear the caches.

[Lemocin]

If you rename Gästezimmer 4 to Gästezimmer it should be displayed on all cards.

Yes, it's not a problem. Just the autogenerated card doesn't change it's name. But that's an issue from HA or Lovelace, not of this integration i think.

[emufan]

Can we perhaps discuss the entity namings again?

Old integration:
Main Entity name is set a device name in HM
Additional Entity names are set a device name in HM plus Suffix.
=> So the user is used to get the name from HM as main entity name. The entity name is used in the UIs.

Current state of new integration
Device name is set a device name in HM.
Every Entitiy name is set as device name in HM but with suffix of the channel

Proposal:
Device name is set as device name in HM.
Main entitiy name is set as device name in HM as well
Additional channels are set as device name in HM but with suffix of the channel
=> The user has still the name from HM as entity name. The entity name is used in the UIs. This is common for other integrations as well. Device name = Main entity name.
=> This is then more or less the same as in old integration (no breaking) and most usefull.

[SukramJ]

Feel free to create a PR. That might give you an insight of the complexity of naming things.
All i could do is to cut off the channel number for the primary channel.
[Edit]: it's not a real option and will break multi channel devices.

I've never thought that is so hard to fulfill some prerequisites like naming some channels for custom entities.

[SukramJ]

There is one option with limited effort:
If device is not a multi device (multiple physical channels) and virtual channels are disabled:
Cut the channel number from the entity name

If device is a multi device (multiple physical channels) or virtual channels are enabled:
All channels will habe a channel suffix, unless the channel name is customized in CCU

[emufan]

Sounds great at least for me.

But think about Sunday lunch and Sunday relaxing. 😂

[danielperna84]

@SukramJ
Regarding the option with limited effort: which effect will this have if a user decides to enable the virtual channels, but then decides to go back to disabled channels? Would this create inconsistent / broken entities that could cause problems if not properly cleaned up? Just mentioning this as a possible problem that could be introduced.

[SukramJ]

I don‘t think so. The entity id will not change after initial setup, due to the unique id. Only the displayed entity name will change, if not customized in ha.
This is only relevant for hmip devices with one physical and virtal channels. So basically switches and light.
Climate has no virtual channels., and Cover displays no virtual channels as described in another discussion.