Customization Not Working for Some Entities

For some reason, I am unable to customize some entities in Home Assistant, including the icon, friendly name, and ‘hidden’ attribute. There are no errors or warnings in the homeassistant log file.

For example, I want to hide both Trip A and Trip B sensors from the UI entirely:

Selection_030

Here is how I include the customizations:

homeassistant:
    [...]
    customize: !include_dir_merge_named customize

And in the file customize/sensors.yaml:

sensor.c71e5d401fbf11e795090050568f5b13_trip_a:
  hidden: true

sensor.c71e5d401fbf11e795090050568f5b13_trip_b:
  hidden: true

Both of these entities are found in the states list:

And using the ‘built in’ customization UI at https://localhost/config/customize it is able to correctly parse the config and show that ‘Hide from UI’ is checked - so why isn’t it applied to the dashboard?
Selection_032

Also weird is that I have multiple other customizations in that file, changing both ‘hidden’ and the friendly name, and those changes are applied correctly. And this is just one example - I have about six or seven other sensors/switches having the same issues, even after multiple reboots.

customize: !include_dir_merge_named customize/sensors.yaml <===

Isn’t include_dir_merge_named supposed to be used with a directory argument, not a file argument? This is what the customize directory looks like:

customize/
├── binary_sensors.yaml
├── locks.yaml
├── sensors.yaml
└── switches.yaml

Advanced Usage

We offer four advanced options to include whole directories at once.

!include_dir_list will return the content of a directory as a list with each file content being an entry in the list.
!include_dir_named will return the content of a directory as a dictionary which maps filename => content of file.
!include_dir_merge_list will return the content of a directory as a list by merging all files (which should contain a list) into 1 big list.
!include_dir_merge_named will return the content of a directory as a dictionary by loading each file and merging it into 1 big dictionary.

I appreciate the response but I am already using include_dir_merge_named and, as far as I know, using it correctly.

I tried your suggestion of customize: !include_dir_merge_named customize/sensors.yaml and it did not work.

you can just put
!include customize/sensors.yaml <== this point specific to sensors.yaml in customize folder

That did not work either. I get the exact same behavior as before. Below is the full contents of my sensors.yaml file. Only the sensors beginning with sensor.c71e5d401fbf11e795090050568f5b13* are missing the customizations. Every other sensor in the configuration file is being applied properly.

sensor.aeotec_zw096_smart_switch_6_current:
  friendly_name: 'Bedroom Fan Current'
  hidden: true

sensor.aeotec_zw096_smart_switch_6_energy:
  friendly_name: 'Bedroom Fan Energy'

sensor.aeotec_zw096_smart_switch_6_power:
  friendly_name: 'Bedroom Fan Power'
  hidden: true

sensor.aeotec_zw096_smart_switch_6_voltage:
  friendly_name: 'Bedroom Fan Voltage'
  hidden: true

sensor.aeotec_zw096_smart_switch_6_previous_reading:
  hidden: true


sensor.yr_symbol:
  friendly_name: 'Weather'

sensor.yr_temperature:
  friendly_name: 'Temp'


sensor.ecolink_door_access_control:
  hidden: true

sensor.ecolink_door_alarm_level:
  hidden: true

sensor.ecolink_door_alarm_type:
  hidden: true

sensor.ecolink_door_burglar:
  hidden: true

sensor.ecolink_door_power_management:
  hidden: true

sensor.ecolink_door_sourcenodeid:
  hidden: true


sensor.kitchen_multisensor_relative_humidity:
  friendly_name: 'Kitchen Humidity'

sensor.kitchen_multisensor_temperature:
  friendly_name: 'Kitchen Temp'

sensor.kitchen_multisensor_ultraviolet:
  hidden: true

sensor.kitchen_multisensor_sourcenodeid:
  hidden: true

sensor.kitchen_multisensor_luminance:
  hidden: true

sensor.kitchen_multisensor_alarm_level:
  hidden: true

sensor.kitchen_multisensor_alarm_type:
  hidden: true

sensor.kitchen_multisensor_burglar:
  hidden: true


sensor.fibaro_system_fgrgbwm441_rgbw_controller_exporting_10_32:
  hidden: true

sensor.fibaro_system_fgrgbwm441_rgbw_controller_power_10_4:
  friendly_name: 'Kitchen LED Power'

sensor.fibaro_system_fgrgbwm441_rgbw_controller_power_10_8:
  hidden: true

# Car
sensor.c71e5d401fbf11e795090050568f5b13_fuel:
  friendly_name: 'Fuel Level'
  icon: mdi:fuel

sensor.c71e5d401fbf11e795090050568f5b13_odometer:
  friendly_name: 'Odometer'
  icon: mdi:gauge

sensor.c71e5d401fbf11e795090050568f5b13_range:
  friendly_name: 'Driving Range'
  icon: mdi:road-variant

sensor.c71e5d401fbf11e795090050568f5b13_trip_a:
  hidden: true

sensor.c71e5d401fbf11e795090050568f5b13_trip_b:
  hidden: true

So actually you want to customize the entity_id that already exists, Sorry for my misunderstood, I thought you are using in sensor platform.

customize: !include_dir_list customize/

in sensors.yaml file, you need 2 space before like I past below

  sensor.aeotec_zw096_smart_switch_6_current:
    friendly_name: 'Bedroom Fan Current'
    hidden: true

  sensor.aeotec_zw096_smart_switch_6_energy:
    friendly_name: 'Bedroom Fan Energy'

when you put directly under customize:

customize:
  sensor.aeotec_zw096_smart_switch_6_current:
    friendly_name: 'Bedroom Fan Current'
    hidden: true

  sensor.aeotec_zw096_smart_switch_6_energy:
    friendly_name: 'Bedroom Fan Energy'

Thanks, I tried that suggestion and it gives me a configuration error:

2018-01-24 00:55:09 ERROR (MainThread) [homeassistant.config] Invalid config
for [homeassistant]: expected a dictionary for dictionary value @ data['customize']. Got
[OrderedDict([('sensor.aeotec_zw096_smart_switch_6_current', OrderedDict([(
'friendly_name', 'Bedroom Fan Current'), ('hidden', True)])), ('sensor.aeotec_zw096_smart_switch_6_energy', 
OrderedDict([('friendly_name', 'Bedroom Fan Energy')])), 
('sensor.aeotec_zw096_smart_switch_6_power', 
OrderedDict([('friendly_name', 'Bedroom Fan Power'), ('hidden', True)])), 
('sensor.aeotec_zw096_smart_switch_6_voltage', OrderedDict([('friendly_name', 
'Bedroom Fan Voltage'), ('hidden', True)])), ('sensor.aeotec.... 
(See /home/homeassistant/.homeassistant/configuration.yaml, line 1)

Maybe it will help if I upload my config to github.
Here is my sensors file: https://github.com/nemec/home-assistant-config/blob/master/customize/sensors.yaml
And my main configuration: https://github.com/nemec/home-assistant-config/blob/master/configuration.yaml#L9

have you try !include_dir_merge_list
customzie: !include_dir_merge_list customize/

This mean every yaml file in customize folder has to be be under customize platform

What would that look like? The customize entry in the documentation doesn’t include any list at all: Customizing entities - Home Assistant

And the docs also mention:

It is important to note that when using !include_dir_merge_list, you must include a list in each file