For various reasons I am having to rebuild my Hassio system from scratch, It was 18 months or so since I first built it, and renaming Zwave Nodes and entities seems even more obscure then it used to be, but I “thought” I was starting to work out how it works.
Changing the name of the Node in Customize gives me this notice on the screen
“It seems that your configuration.yaml doesn’t properly include customize.yaml
Changes made here won’t affect your configuration.”
Fair enough, so I added customize: !include customize.yaml to the Config file to give this config
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
# base_url: example.duckdns.org:8123
# Sensors
sensor:
# Weather prediction
- platform: yr
# Text to speech
tts:
- platform: google_translate
customize: !include customize.yaml
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
(This is actually the config from another fresh build that I made to try and work out what was going on, in this case I added a customisation to the User)
When I check the config file I get the following error
" Configuration invalid
Integration not found: customize"
I have checked the release notes and i cannot find anything related to this so at the moment I am a bit lost. I am sure the answer is blindingly obvious but …
Thanks for any help
No. Why do people keep thinking it needs to be replaced? Honestly I haven’t seen a single article suggesting that it ever needs to be removed or replaced, yet repeatedly people keep asking the same question. I’m not being funny, just curious what made you think that it needs to be replaced with anything?
Just add the text @VDRainer posted to your configuration.yaml, do not remove anything unless you want to remove that functionality.
Not sure if it’s a formatting issue here on the forum…but if your configuration.yaml looks just like what you posted in that code window, your indentation is off. It should look like this:
yes, the formatting int he forum is off. my indentation is exactly as you mentioned. Infact, yesterday, I had HomeAssistant crash on me and boot up in safe mode. It only went back to normal when i deleted the code from the config.yaml file.
Great ! Thank you it is work now.
One more question. How to understand file structure in my home assistant server.
i use Ubuntu and my configuration.yaml and customize.yaml files are located in :
/usr/share/hassio/homeassistant
So when i point /local/www/pics/tosho.jpg in some config file , actually it is located in
I have some trouble with HA not seeming to be able to write to customize.yaml file anymore.
I had somehow managed to put data in there through the UI. But I had not enabled the integration. Now that I try to do so. It throws warning that my integration is not setup. But I can not see any problem. And nothing is ever written to the file in the first place.
I have checked that all r/w permissions are in order. It is driving me bonkers. Help please. I did go into the file to delete the previous entry.
See attatched screen prints:!
But the file is completely empty.
It is not loading the integration. Am I just too tired that I am missing something?
Seems like you could help me (NEWBIE) as well. I can not figure out what I am doing wrong on my configuration and customize.
In my configuration I have added:
homeassistant:
customize: !include customize.yaml
Customize is 2 spaces indent
In my customize.yaml (stored un der config dir) i have tried:
1:
homeassistant:
name: Home
unit_system: metric
# etc
customize: # Add an entry for each entity that you want to overwrite.
sensor.solaredge_current_power:
friendly_name: Zonepanelen huidig vermogen
I keep getting:
extra keys not allowed @ data[‘customize’][‘homeassistant’]
PS this is all because I am lookingto get a solution for my Solar edge entities which all show:
This entity (“sensor.solaredge_current_power”) does not have a unique ID, therefore its settings cannot be managed from the UI. See the documentation for more detail.
