Core: New Customization in 0.53 throws erroneous warning

[JSCSJSCS]

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version): This doesn't work in Hass.io. This should be updated, but I am using 0.53

Python release (python3 --version):This doesn't work for Hass.io either. It should be updated. I have no idea what python version it is using.

Component/platform:Home Assistant. I filed a report in Hass.io and was told it is a HA problem and my issue was closed there.

Description of problem:Just tried out the new Customization feature of Hass.io 0.53 and it threw a warning, while actually doing what was expected. After clicking SAVE to change the default name of a camera.usps.mail entity, the change was made to the customize.yaml file and it worked as expected.

Expected:I expected no warning, as it all appeared to work as expected.

Problem-relevant configuration.yaml entries and steps to reproduce:

1. Clicked the UPGRADE link in version 0.52.1 and upgraded to 0.53
2. After upgrade, tried out the new Customization feature
3. Changed the friendly name of the camera.usps.mail entity
4. All seemed to work, except I got a Warning saying it would not work. See Additional info below.

Traceback (if applicable):

Additional info:

I have the following in my configuration.yaml file:

homeassistant:
  name: Home
  latitude: !secret latitude
  longitude: !secret longitude
  elevation: 701
  unit_system: imperial
  time_zone: America/Los_Angeles
  customize: !include customize.yaml

And after making the edit with the Customize function, the customize.yaml file was updated as expected:

camera.usps_mail:
  friendly_name: USPS Mail Images

So it appears that my configuration.yaml file DOES properly include customize.yaml and my changes did take effect despite the warning to the contrary.

Love this feature by the way. Hope the issue can be rectified easily.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[Cnordbo]

I still get this issue on 59.2

[Munsio]

Problem is still available on version: 0.60.0
Using an Raspberry 3 and the docker image for it.

[abeeson]

I have confirmed this as well as still present on 0.60 on two separate RHEL installs.
One using Python 3.4 and the other using 3.6, both with the same results.

[goldiiii]

I also have the issue. Complete fresh install with 0.6

[VDRainer]

+1
Latest release 0.61.1
Started with a fresh customize.yaml.
Customizing the views (order) worked as expected.
On customizing the first group, the warning is shown.

[theetron]

I had this error line also in 0.62.1 Hassio. But I edited the customize.yaml by hand.
I started with 4 spaces in the file and it was picked up properly. I also had quotes around my friendly name.

    switch.neo_coolcam_power_plug_12a_switch:
      friendly_name: 'Lamp boven bank'
      icon: mdi:spotlight-beam

After saving this customization in the GUI, the spaces and quotes are gone in the file.

switch.neo_coolcam_power_plug_12a_switch:
  friendly_name: Lamp boven bank
  icon: mdi:spotlight-beam

Now I don't have the error anymore.

[ghvader]

seeing this issue in .63 install. oddly i edited the name of about 5 or 6 devices and then this warning started showing up and won't go away. i see the entries get added to the customize.yaml file though and the changes do reflect in the front end

[drogfild]

I can confirm this with Hass.io on Raspberry 3, version 0.64.0. Customization from UI works fine and values are saved to customize.yaml, but it always gives me that same error after save. Haven't found why it does that.

My configuration.yaml homeassistant-tag:

homeassistant:
  name: Home
  latitude: !secret latitude
  longitude: !secret longitude
  elevation: !secret elevation
  unit_system: metric
  time_zone: !secret timezone
  customize: !include customize.yaml

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[ABeumer525]

Still an issue! How the hack do you change entity names around the customize.yaml file.

[david81]

This still appears to be an issue on 0.80. Clean install on Ubuntu 18.04

[ab-it]

Clean install of hass.io + configurator + lovelace migration.

The first time a change was accepted without the error, next changes this error occurred but changes are incorporated.

I am not 100% sure but I believe

  # Customization file
  customize: !include customize.yaml

is the problem. Those are lines 13 and 14 of my configuration.yaml and when I remove the indentation, no more complaints.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[WoLpH]

Still an issue on the latests dev commit (https://github.com/home-assistant/home-assistant/commit/b697bb7a26146cf9365b43c5cca89807676f2435)

[tawera]

I have the same issue on version 0.93.1 on HassOS 1.13. I get the warning but everything seems to work.

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.