Renaming custom entities using customize.yaml

Configuration
1

Hey Everyone :wave:

I am currently trying to rename 20 entities using the customize.yaml being imported into my configuration.yaml but I keep getting the following error.

image

Been a bit stuck on this for the last day or so, I have checked out a few threads but I am sure I am missing something silly :sweat_smile:

Customize.yaml

customize:
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_1:
    friendly_name: CPU 1 Core 1
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_2:
    friendly_name: CPU 1 Core 2
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_3:
    friendly_name: CPU 1 Core 3
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_4:
    friendly_name: CPU 1 Core 4
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_5:
    friendly_name: CPU 1 Core 5
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_6:
    friendly_name: CPU 1 Core 6
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_7:
    friendly_name: CPU 1 Core 7
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_8:
    friendly_name: CPU 1 Core 8
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_9:
    friendly_name: CPU 1 Core 9
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_10:
    friendly_name: CPU 1 Core 10
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_1_2:
    friendly_name: CPU 2 Core 1
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_2_2:
    friendly_name: CPU 2 Core 2
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_3_2:
    friendly_name: CPU 2 Core 3
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_4_2:
    friendly_name: CPU 2 Core 4
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_5_2:
    friendly_name: CPU 2 Core 5
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_6_2:
    friendly_name: CPU 2 Core 6
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_7_2:
    friendly_name: CPU 2 Core 7
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_8_2:
    friendly_name: CPU 2 Core 8
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_9_2:
    friendly_name: CPU 2 Core 9
  sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_10_2:
    friendly_name: CPU 2 Core 10

Configuration.yaml

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Text to speech
tts:
  - platform: google_translate

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

frontend:
  themes: !include_dir_merge_named themes
  
binary_sensor:
  - platform: hikvision
    host: 192.168.1.94
    username: admin
    password: SECRET
    
homeassistant:
  customize: !include customize.yaml
2

Hello and welcome to the forum.

Please go to Developer Tools → YAML and perform a config check before attempting to restart if you are using/changing YAML config. Even if it says the config is valid check your persistent notifications and logs for config errors after performing the check (known bug). Only restart when the check passes.

Your problem is that you have this at the top of your include file:

customize:

Remove it.

Then shift everything left two spaces.

At the moment your customize section resolves to this after the include! is parsed:

homeassistant:
  customize: 
    customize: # this is the double entry you have included in the file
      sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_1:
        friendly_name: etc...

When what you need it to resolve to is this:

homeassistant:
  customize: 
    sensor.emery_server_intel_xeon_e5_2670_v2_load_cpu_core_1:
      friendly_name: etc...
1 Like
3

That did the trick perfectly, Thank you for the warm welcome and the guidance/solution :slight_smile:

2 Likes