From 9cfb0867f44890b5f0b2d0435db2607b4b15a286 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Sat, 11 Dec 2021 11:43:35 +0100 Subject: [PATCH] 2021.12: Clarify breaking change --- .../_posts/2021-12-11-release-202112.markdown | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/source/_posts/2021-12-11-release-202112.markdown b/source/_posts/2021-12-11-release-202112.markdown index 86c47c8c662..c293a699c81 100644 --- a/source/_posts/2021-12-11-release-202112.markdown +++ b/source/_posts/2021-12-11-release-202112.markdown @@ -356,6 +356,28 @@ for this is recommended and remains available. In case you used this to change how, for example, a cover or door contact entity is shown, you can now change that by editing the entity in the UI. +For these cases, customizing the `device_class` is no longer needed. + +A small explanation why it has been removed: + +With customize, one is changing the state machine directly, without any checks. +This comes at a risk. Additionally, for many use cases (like: name, icon, +device class) one should edit the entity via the UI instead, which is +possible for the greater part of the entities nowadays. + +The old customize UI is confusing in many ways and has a level of power that, +if wielded incorrectly, it can have unforeseen consequences. +Someone found the customize first, and then things +are out of sync throughout the UI, as the internal entity registry would show +the old values. + +The customize UI also relied on setting up an include and YAML configuration to +begin with; which already made it an advanced feature. + +Therefore, the customize UI was removed and remains available as an advanced +YAML feature, additionally we have added the capability, to adjust +the common `device_class` changes using the "Show as" feature while +editing the entity from UI. {% enddetails %}