You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
I'd like to see the name of the config parameter of the device when it has been set to be discovered through MQTT in HA. The entity ID must be the same as it is, holding the actual config parameter number.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
By looking at this again I just remember that actually you can already do this by setting a custom entity name template from MQTT discovery settings :) If you want label to be included you can use %l in the template. Under the input there is a helper to help you doing this. The default template is %ln_%o that means the node name + object id
Thing is that I’m already using “ _%o” as the template to not break previous functionality of using for example “relay_switch_3” as entityID in automations. With setting this “ _%o”, I’m getting the exact same behaviour as before, so I don’t have to revisit all of my automations. At some point HA discovery have been changed, and since then, only “_switch_3” was discovered as the entityID as HA omits the “%ln” part of the default discovery template.
All names are generated by this function so what could be the solution here? I mean I cannot make it work differently only for configuration CC values otherwise that would be a breaking change
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
I'd like to see the name of the config parameter of the device when it has been set to be discovered through MQTT in HA. The entity ID must be the same as it is, holding the actual config parameter number.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: