-
-
Notifications
You must be signed in to change notification settings - Fork 32.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Renault entity naming #57371
Comments
renault documentation |
Hey there @epenet, mind taking a look at this issue as it has been labeled with an integration ( |
Hi @sagitt, This was discussed with @frenck on the original PR: #39605 (comment) |
Of course the user can change entities name, but i think is a better choice (like most integrations) change the integration naming scheme. Personally, i not change any entity name on my installation working on real device name or integration name, and all integrations are ok, except Renault. I think that the better solution is the ability to give a name to the integration during configuration and associate the given name as prefix to the entities. Please think about this solution! Thanks |
The VIN is good for core/homeassistant/components/tplink/sensor.py Lines 164 to 170 in 748d915
|
Car model, VIN, integration name or car plate are all ok But i think is a bad choice (as now) a generic entity name without prefix like "sensor.battery_level". |
The problem
With new Renault integration in 2021.10.X, all entity have a bad naming scheme (respect old custom component)
for example, "sensor.battery_level".
I think is better an entity like sensor.XXXXXX_battery_level, where XXXXXX is for example the integration name, the plate or the VIN number.
What is version of Home Assistant Core has the issue?
core-2021.10.2
What was the last working version of Home Assistant Core?
n/a
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Renault
Link to integration documentation on our website
https://www.home-assistant.io/integrations/renault/
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: