Why its not possible to define a friendly name for plant sensors?
The documentation says that it’s not possible to define one in YAML and also it’s not possible to change the friendly name through the UI - “This entity does not have a unique ID, therefore its settings cannot be managed from the UI.”
Which plant sensor?
The miflora?
It has a name you can define https://www.home-assistant.io/integrations/miflora/#name
Have you tried adding a friendly_name using customize?
I am currently working on an updated Plant Component.
It will take advantage of the Open Plant Book API that is currently under development.
In this version I have added “name” as one of the config parameters for a plant.
Hope to get at PR ready as soon as the openplantbook is slightly more mature, but it works fine here (I use it in my production setup) so you can install it as a custom_component already.
1 Like
It’s been a lot of back and forth, and the latest progress was that we first needed to have an architectural discussion about how to access configuration variables from inside HA:
When that has been decided, the plant component needs to be updated to publish its config in the proper way.
And then we can start adding plantbook attributes to the plant object, and update the cards to read and use these attributes.
All the bulding blocks are in place, but the process of getting it into core was a bit harder that initially thought.
But if anyone has any input to the architectural discussion, please participate in the mentioned issue.