I have this entry on my configuration.yaml:
customize: !include customize.yaml
and a customize.yaml file in config dir, but when i go to check the entire configuration i get the error “component customize not found”.
Where am i wrong?
I have this entry on my configuration.yaml:
customize: !include customize.yaml
and a customize.yaml file in config dir, but when i go to check the entire configuration i get the error “component customize not found”.
Where am i wrong?
Without more context, it’s hard to know.
You did include it as part of the homeassistant
: block and not starting a line?
To be more precise here it is the part of config file i did:
homeassistant:
customize: !include customize.yaml
Is this correct ?
Assuming two spaces before customize:
then yes. This is mine
homeassistant:
customize: !include customize.yaml
Your customize.yaml
file doesn’t start customize:
?
You need to post your customise file. If the first line is this:
Customise:
Then that is your problem.
Also, everything in customise will be shifted to the left so it’s different to if you had it in configuration.yaml
These are the first lines in customize.yaml:
sensor.living_room_link:
hidden: false
sensor.living_room_overlay:
hidden: false
device_tracker.chromecaststation_2:
hidden: false
device_tracker.tv_living_room:
hidden: true
binary_sensor.door_window_sensor_158d000201b557:
hidden: true
icon: mdi:door
binary_sensor.motion_sensor_158d0001a98a62:
hidden: true
friendly_name: Sensore Movimento Salotto
binary_sensor.motion_sensor_158d0001ddac9e:
hidden: true
friendly_name: Sensore Movimento Studio
binary_sensor.motion_sensor_158d0001a92ca1:
hidden: true
friendly_name: Sensore Movimento Letto
binary_sensor.switch_158d00019cd3cd:
hidden: true
friendly_name: Pulsante 1
binary_sensor.switch_158d0001bd1a4b:
hidden: true
friendly_name: Pulsante 2
No, customize.yaml doesn’t have customize:
See my last post…
Simple fix, all your entries need four spaces inserted in front of them…
sensor.living_room_link:
hidden: false
sensor.living_room_overlay:
hidden: false
You need to duplicate how they would be spaced in configuration. yaml minus two leading spaces.
Thanks… solved !