Correct use of customize_glob

I’m in the process of figuring out how to split up the configuration and trying to get it as clean and logical as possible. Now I’m a bit in doubt about the difference between customize.yaml and customize_glob.yaml. I guess no real hard rules apply but perhaps there is a preferred way?

I have 6 Mi Flower sensors and added them to my sensors.yaml. They work fine but I noticed when creating an entities card on the mainpage the description of the entities shows as: sensor.flower_4_moisture with a percentage. All correct but ugly. Now I could use friendly names in customize.yaml but that would be a lot of code for 6 sensors with 4 readings. So I created the next code and put it in customize_glob. It works just fine but I wonder if this is the correct way.

#customize_glob
# Flower care 
"sensor.flower_*_battery":
  friendly_name: Battery
"sensor.flower_*_light_intensity":
  friendly_name: Light intensity
"sensor.flower_*_temperature":
  friendly_name: Temperature
"sensor.flower_*_conductivity":
  friendly_name: Fertility
  icon: mdi:pot
"sensor.flower_*_moisture":
  friendly_name: Water

This work really well, the names in the cards for all 6 sensors show up as wanted and on entity level its still easy to identify the different senors. I just wonder if in this case the use of customize_glob is the correct way or that I should put this code in a different (customize.yaml) yaml file?

Regards

1 Like

Not sure if it is correct - but it works and seems really cool as a way to deal with repetitive names!