Plant monitor: manually set friendly_name or unique_id

Feature Requests
1

Hi everybody,

please upvote this if you would like a solution as well; this has bothering me for quite some time, so I thought I’d ask for a change :slight_smile:

Suggestion

Please allow to either have an attribute friendly_name or unique_id for the plant entity via yaml.

Why (tl;dr)

This way, users can have a nicer name for their plant entities (compared to the automatically generated ones); see screenshot from bottom of this post.

Why (long)

I have multiple plant monitors set up via ESPHome and Xiaomi BLE sensor.

Here is an example of one of these plant entities:

plant:
  unten_arbeitszimmer_pachira_aquatica_links:
    sensors:
      moisture: sensor.plant_sensor_5fff_moisture
      temperature: sensor.plant_sensor_5fff_temperature
      battery: sensor.plant_sensor_5fff_battery
      conductivity: sensor.plant_sensor_5fff_conductivity
      brightness: sensor.plant_sensor_5fff_illuminance
    min_moisture: 20
    max_moisture: 85

This plant will show up like this

grafik
grafik1018×404 22.6 KB

I’d like the arbeitszimmer_pachira_aquatica_links to be something like Arbeitszimmer/Pachira Aquatica/Links or simply Pachira Aquatica; however, this name is directly related to this line

grafik
grafik912×209 20.9 KB

There is no friendly_name attribute that I can set for this plant via yaml; when I try to assign a friendly name via UI, I get this, which loosely translates to This entity ("plant.arbeitszimmer_pachira_aquatica_links") does not have an unique ID, therefore it cannot be configured through the UI. Have a look at the documentation for further details..

grafik
grafik1229×500 46 KB

I would like it to look like this mock-up

grafik
grafik1035×383 20.1 KB

This is not just for having a nicer name in the UI, but especially for notifiications; mine currently look like this, because they use the entity_id - since there is no friendly_name

grafik
grafik751×137 9.13 KB

arbeitszimmer_baeumchen comes from plant.arbeitszimmer_baeumchen, which is the entity_id; I’d like to use the (currently non-existent) friendly_name, which would -in this case- by Arbeitszimmer Baeumchen instead.

2

It definitely should support name/friendly_name.

Until it is implemented you can use customize to add a friendly name:

1 Like
3

Take a look at this custom component in the mean time. Heavily featured, works great.

1 Like