I have noticed recently that reloading my customisations (say I add an icon or friendly name) either in a package or in customisation.yaml doesn’t reload anymore. This is for entities that I can’t edit in the GUI so I edit the customize file or package but then reloading core does nothing.
Anyone else see this?
As soon as I restart HA everything loads u correctly. Also all other reload options (themes etc) work perfectly…
@bdraco
Nick - you did the reload for everything else in What the Heck… can you confirm this is a bug before I raise an issue on Github?
Reload location and customizations is actually a special case and isn’t a reload service. It actually calls homeassistant.reload_core_config
The code in homeassistant/config.py related to customize hasn’t changed in a long time so I’m not sure what is going on.
yes I am calling that service via a script. It definitely used to work but isn’t anymore.
If you change an icon or a friendly_name in customize.yaml and call the service you can see it doesn’t load the ned icon/name.
I just gave it a shot and change the name of my A/C, and its working as expected for me.
I can’t understand why it’s not working for me then.
What logging level should I set to debug to see what is happening?
logger:
default: debug
?
Also did you try an entity you CAN’T manage via the GUI like a template sensor?
Just tried it on a barebones install on a sensor that I can’t manage (change name/icon in the GUI as no unique ID) and it doesn’t work there either.
MAYBE I need to wait a few minutes. An entity I changed in a package just updated now…
SCRATCH THAT - I must have done something else because it’s def not changing now…
Yes and the behavior is, as the saying goes, “norbal”.
The explanation for its quirky behavior can be found at the very bottom of the documentation page for Customizing Entities:
Warning
New customize information will be applied the next time the state of the entity gets updated
I customized a sensor entity by adding some information to customize.yaml. I executed Reload Location and Customizations and didn’t see, in the States view, the custom attribute I had created. However, if I wait long enough for the sensor to change state, the custom attribute appears.
Not exactly how you would expect it to behave after executing a Reload service but that’s it’s “norbal” behavior. 
Well that sucks!