customize_glob is described in the docs here (only in the example, it’s not actually described in the proper documentation), but I’ve never seen it used or heard of it before.
Looks to customize based on pattern matching. If it’s not working for OP, we would probably need to see what his customize_glob.yaml looks like too, if that’s what’s failing. The example seems to show that the customize_glob: will still work when customize: is used, so that part looks ok.
I generally have had the need to use it for custom UI customizations. And you use it where (as the name suggests) that you want to globally customize entities without having to modify each one individually in the customize: section.
Here is how I use it in my config:
customize_glob:
## see https://github.com/andrey-git/home-assistant-custom-ui for full instructions
"*.*":
custom_ui_state_card: state-card-custom-ui
automation.*:
emulated_hue_hidden: true
haaska_hidden: true
group.*:
emulated_hue_hidden: true
haaska_hidden: true
switch.*:
assumed_state: false
fan.*:
custom_ui_state_card: state-card-custom-fanspeed
## had to add the next lines due to an undocumented breaking change in v0.81.x ##
## https://github.com/home-assistant/home-assistant-polymer/issues/1991 ##
#weather.*:
# custom_ui_state_card: null
camera.*:
custom_ui_state_card: null
history_graph.*:
custom_ui_state_card: null
media_player.*:
custom_ui_state_card: null
Old post but this did it for me thanks. I had manually created the file and editing the entities were not working. Well they were adding the amendments into the file but not updating anything on lovelace.