-
Notifications
You must be signed in to change notification settings - Fork 24
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
Feature request: Allow customization of entity id's #36
Comments
This is indeed a good request. We could configure it in such a way that the entity ids contain the country name in it. Then also change the integration friendly name to a country. That would allow you to add multiple instances of the integration. Would that solve it? |
There was also a request to add different instances of the integration with different templates. Thus, I think I am gonna ask the user for a name in the config flow and add this name to the entity name. Similar to how Forecast.Solar handles this. |
My issues also resulted from the frankenergy and entsoe integrations using the same name. |
I got multiple instances working in my PR #42 |
Thanks to @sfstar this issue is resolved. The user is asked for a name when configuring the integration. This name is added to the end of the entity id in this format: |
@JaccoR Thank you for merging. |
I made some small changes. The prefix has been called name and the format is |
Ah yes, should've taken a bit more time for this. I quickly fixed it by deleting the _ when no name is given. Next to that I put the name in front now. So sensor._current_electricity_market_price. I deemed the _ necessary for a clarity. Hope i thought of everything now and this didn't cause too much of a disturbance. Thanks! |
Currently some of the entity id's given by this component conflict with another integration I've configured to provide me with all-in hour prices from an energy provider.
Next to that I have the need to monitor 2 different country's hour prices.
Therefore, it would be nice if this component has an prepend option during configuration.
So that users might customize their entity id's (and possibly in the future create multiple instances of this integration).
The text was updated successfully, but these errors were encountered: