This link:
contains an example code only supported by the Custom UI plugin:
And there are no any remarks that this is only supported by this custom plugin.
Examples for “customize_glob” & “customize_domain” were added as a part of
this PR on 26 Feb 2017.
Either Custom UI becomes a part of HA or the docs are edited correspondingly.
petro
October 27, 2022, 12:00am
2
Those were added into core along time ago
Line 125 shows them in core
"""Constants used by Home Assistant components."""
from __future__ import annotations
from typing import Final
from .backports.enum import StrEnum
APPLICATION_NAME: Final = "HomeAssistant"
MAJOR_VERSION: Final = 2022
MINOR_VERSION: Final = 12
PATCH_VERSION: Final = "0.dev0"
__short_version__: Final = f"{MAJOR_VERSION}.{MINOR_VERSION}"
__version__: Final = f"{__short_version__}.{PATCH_VERSION}"
REQUIRED_PYTHON_VER: Final[tuple[int, int, int]] = (3, 9, 0)
REQUIRED_NEXT_PYTHON_VER: Final[tuple[int, int, int]] = (3, 9, 0)
# Truthy date string triggers showing related deprecation warning messages.
REQUIRED_NEXT_PYTHON_HA_RELEASE: Final = ""
# Format for platform files
PLATFORM_FORMAT: Final = "{platform}.{domain}"
show original
Does that mean that a functionality of Custom UI is a core functionality - at least in part of this code?
customize_domain:
light:
icon: mdi:home
...
customize_glob:
"light.kitchen_*":
icon: mdi:description
petro
October 27, 2022, 12:27am
4
Everything you see in the docs is part of core.
petro
October 27, 2022, 12:28am
5
I think you’re getting tripped up because custom ui can also do the same actions. Just wipe custom ui from your memory and try what’s in the docs
1 Like
Now I got the point. Correct me if I am wrong:
You may use customize, customize_glob & customize_domain as a part of a core - w/o templates.
You may also use them with templates written on JS code - only with Custom UI.
