-
Notifications
You must be signed in to change notification settings - Fork 5k
Open
Description
Feature Request: Option to use device.name instead of friendly_name for Entity IDs in Tasmota MQTT Discovery
Description:
Currently, the Tasmota MQTT Discovery integration in Home Assistant primarily uses the device’s friendly_name
for naming entity IDs (e.g., switch.friendly_name
). This causes entity IDs to change whenever the friendly name on the device is modified. For users who want stable and consistent entity IDs, this behavior is problematic.
I would like to request an option (or alternative default) to use the device’s device.name
instead for entity ID generation, as this is generally more stable and rarely changed. This would improve consistency and avoid breaking automations, scripts, or dashboards when friendly names are updated.
Why is this important?
- The
friendly_name
is user-editable and can change frequently, which leads to unexpected entity ID changes. - The
device.name
is usually set once during setup and remains stable. - Users should have flexibility to choose which naming scheme suits their needs best.
Current situation:
- The integration currently defaults to using
friendly_name
for entity IDs. - Changing the friendly name results in changing entity IDs.
- Users need to manually adjust entity IDs or automations when names change.
Proposed solution:
- Add a configuration option in the Tasmota integration to select whether
friendly_name
ordevice.name
is used for entity ID generation. - The default behavior can remain using
friendly_name
for backward compatibility, or set the default to the new proposed scheme for future clarity. (I would prefer the second option) - Possibly offer a migration path for existing setups to switch naming schemes.
Additional notes:
- This would improve long-term stability and maintainability of Tasmota entities in Home Assistant.
- It gives users control over naming conventions to better fit their workflows.
Metadata
Metadata
Assignees
Labels
No labels