What is wrong with entities customization

Configuration
1

I wanted to showrten very long names given by Netatmo integration to entities so I wen to customize.yaml and addes several entires like these (here is the example for humidity sensors, but case applies to many more):

    sensor.netatmo_pogodynka_ogrod_humidity:
      friendly_name: Garden Humidity
    sensor.netatmo_pogodynka_parter_humidity:
      friendly_name: Living Room Humidity
    sensor.netatmo_pogodynka_sypialnia_humidity:
      friendly_name: Bedroom Humidity
    sensor.netatmo_pogodynka_tv_room_humidity:
      friendly_name: TV Room Humidity

Customization seems to work, sort of… When I go to Developers Tolools -> State I can see new friendly names assigned:

Screenshot 2020-06-16 at 9.38.42
Screenshot 2020-06-16 at 9.38.42836×467 54.6 KB

Now, the tricky part is that not all of these new names are reflected in history graph:

Screenshot 2020-06-16 at 9.40.13
Screenshot 2020-06-16 at 9.40.131030×210 15 KB

As you can see only the very first one (Garden Humidity) is using a new name, all others are using system assigned, original names. Same case for other entities from Netatmo integration… ~50% of them are using customized friendly names, while the others the original one. How to get tthis fixed?

EDIT: Interestingly, when I tried to see how these customizations looks like from Configuration->Customizations in UI and selected one of these I see error message popping up:
Screenshot 2020-06-16 at 10.05.38

which is very strange, since I made all customizations directly inside configuration.yaml, not including these in customize.yaml… which I actually planned as a next step… So at the moment my full configuration.yaml looks like that:

homeassistant:
  customize:
    sensor.netatmo_pogodynka_ogrod_humidity:
      friendly_name: Garden Humidity
    sensor.netatmo_pogodynka_parter_humidity:
      friendly_name: Living Room Humidity
    sensor.netatmo_pogodynka_sypialnia_humidity:
      friendly_name: Bedroom Humidity
    sensor.netatmo_pogodynka_tv_room_humidity:
      friendly_name: TV Room Humidity
2

You have to include a customize.yaml file. Like the error says to.

3

OK, I’m not sure how this would change the situation… Configuration I made is perfectly in line with official customization documentation…
Now, I moved all customizations to customize file and update configuration accordingly:
configuration.yaml:

homeassistant:
  customize: !include customize.yaml

customize.yaml:

. . .
sensor.netatmo_pogodynka_parter_co2:
  friendly_name: Living Room CO2
sensor.netatmo_pogodynka_parter_humidity:
  friendly_name: Living Room Humidity
sensor.netatmo_pogodynka_parter_max_temp:
  friendly_name: Living Room Max Temp
sensor.netatmo_pogodynka_parter_min_temp:
  friendly_name: Living Room Min Temp
sensor.netatmo_pogodynka_parter_noise:
  friendly_name: Living Room Noise
sensor.netatmo_pogodynka_parter_pressure:
  friendly_name: Pressure
sensor.netatmo_pogodynka_parter_temperature:
  friendly_name: Living Room Temperature
. . .

It actually works… I now see the the changed names for customized entities.
However, when I try to use UI to customize something I see new entry created in customize.yaml, but still receive the same error stating that customize.yaml is not properly included…
BTW, config check is not reporting any issues, obviously.