-
Notifications
You must be signed in to change notification settings - Fork 7
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: Can we have a friendlier friendly_name? #41
Comments
Thx for the feedback! |
I was looking into this.
|
I do not know how other HA users use your integration. To me the sensors for a chosen location, the prediction sensors and official price sensors appear being more "static" when it comes to displaying their values on a dashboard; e.g. the entity name of a chosen gas-station is a fixed choice and can easily be changed using a YAML "name" tag on the dashboard. The neighborhood price sensors have names and addresses varying as prices change throughout the week. My vote would be to direct your efforts just to the "neighborhood price sensors". |
I've found some way to achieve this, see update readme for info. |
Installed your Custom Component after the provider for Skons "dutch_gas_prices" apparently blocked access to their API.
Living literally on the border between Belgium and the Netherlands, I appreciate very much your components allows to query both sides of the border.
What I really liked about Skons' solution was that it allowed to create a "friendly_name" using any attribute returned in the sensor.
See Skons' DOCS.md for more information.
Thanks for the great work
Edit: I may have been shooting faster than my shadow .... blame it on being a newbie around here. Found this article in HA Configuration .... Would this be the way to provide a friendly name?
The text was updated successfully, but these errors were encountered: