Underscore in Names

[dMopp]

Hi all,

i really love this addon but i ahve a Question and MAYBE a bug, i dont know.

The Autodiscover Feature always changes the name of the discovered the device from

"Uppercase Name"

to

"lowercase_name"

This causes some tourbles with Formating for me, because it should use the actual Name.

Example:
The Device iam using is a tuya power switch with measurement and namend "Steckdose Trockner" inside HomeAssistant (Provided by Zigbee2MQTT)

AutoDiscover naming it "steckdose_trockner".

And for another device, it was using the correct name without underscore... Is there a way to reset the autodisvocer DB so its re-generating the names ?

[bramstroker]

The procedure to get the name from the source entity (in your case "Steckdose Trockner") is done in following fallback mechanism:

1. name (this is the name if you changed the name manually with the GUI)
2. original_name (name provided by the integration)
3. object_id (part after the dot from the entity_id).

So in your case it seems both 1 and 2 did not apply. Could you check file config/.storage/core.entity_registry and search for the switch switch.steckdose_trockner?

Anyway you can just rename the entities from the GUI by clicking the cog wheel.

[dMopp]

Thanks for trying to help out :)

{ "aliases": [], "area_id": null, "capabilities": null, "config_entry_id": "04de18b4dd03b51adf17e2b96ba9b031", "device_class": null, "device_id": "e1c284e90e18bb9aaa5bd57db689e3b9", "disabled_by": null, "entity_category": null, "entity_id": "switch.steckdose_trockner", "hidden_by": null, "icon": null, "id": "680ccd813f67aea95a4fbe9ebfe1a4b2", "has_entity_name": true, "name": null, "options": { "conversation": { "should_expose": true } },

Iam wondering a bit, because another tuya works fine (but just one of them) which si called switch.steckdose_poolpumpe

see:

{ "aliases": [], "area_id": null, "capabilities": null, "config_entry_id": "04de18b4dd03b51adf17e2b96ba9b031", "device_class": null, "device_id": "b574066230ac1be46a89c352f92a28e0", "disabled_by": null, "entity_category": null, "entity_id": "switch.steckdose_poolpumpe", "hidden_by": null, "icon": null, "id": "76b3253cbf732faa9d2720055858bb9d", "has_entity_name": true, "name": null, "options": { "conversation": { "should_expose": true } },

PS: Even if i rename the pwoercalc Device later, the entity names staying the same (lowercase and underscore)

I renamed it here:

but the names are still with underscore etc, see:

[bramstroker]

Both you JSON dumps above are for the same entity. Could you also add the one from switch.steckdose_poolpumpe?

To rename the entities, you have to rename the 5 entities. Click one one of them and than the cog wheel, there you have the option to give it a custom name, or even change the entity id's.
Currently you are renaming the configuration entry, which does nothing really to the entity names. It's only for presentation purposes in the listing of powercalc configurations.

[dMopp]

Sorry, ive updated / fixed the copy/paste issue.

And renaming all 5 Entities for actual 12 devices is a lot of work i would like to avoid, becasue for one of the devices (all using the same pattern and addon) it was working like expected :|

Anyway, if that its the way, i will do it :D

PS: The Tuya Device offers a Power Sensor already, why Powercalc is adding another Power Sensor based on the given one ?

[bramstroker]

I might have an idea what causes this. There is some property has_entity_name in HA which indicates the entity itself does not provide a name, but it should get that from the device. I will adopt my code to also look at that.
Will let you know if a fix is out.

PS: The Tuya Device offers a Power Sensor already, why Powercalc is adding another Power Sensor based on the given one ?

Powercalc provides profiles for some smart plugs which don't provide their self usage. Even though their consumption is very small, they will add up to your total consumption in your house. So you'll get a power sensor so you'll know how much the smart plug itself uses. Hence the naming _device_power and _device_energy.
When you don't want these in your installation you can simply ignore the provided discoveries.

[bramstroker]

Should be fixed with #1811. Just released new version 1.9.1.
After updating you'll need to remove the config entry, that's from the list at the integration page.
That should also remove the related 5 entities.
After that restart HA and it should hopefully discover again. Now add again and it should set the correct names for both the config entry and the 5 entities.
Try that first for one. After that your can do the other 11 in one go.